On Wed, Sep 7, 2022 at 8:44 AM Tianyi Xia via lists.riscv.org <tianshi.xty=alibaba-inc.com@...> wrote:
each "cluster" can have its own unique mmio address for mtimecmp (which may or may not be accessible to other "clusters")
I think this description is better.
Assume there are two clusters，each cluster have two cores，and each cluster have there own MTIMER device. The mmio address of mtimecmp for each hart may like this:
Cluster0
Core0: base0+0x0000_0000
Core1: base0+0x0000_0008
Cluster1
Core0: base1+0x0000_0000
Core1: base1+0x0000_0008
Base0 is the MTIER device base address of cluster0, Base1 is the MTIER device base address of cluster0. the mtimecmp of cluster0 core0 may or maynot be accessible to cluster1, depending on the implementation. If core try to access mtimecmp of other cluster, the action of the access may be write ignore read zero.
The latter sounds like it would be difficult for SW
I think in a platform with multiple MTIMER devices, the mmio address of mtimecmp should be unique to distinguish different MTIMER devices. The hardware can set regular base address to different Mtimer devices. In the above example, assuming base is 0, then base1 may be set to 0x0000_0010. If cluster0 has four cores, then base1 may be set to 0x0000_0020.Then from a software perspective, all mtimecmp registers are addressed consecutively.
This case is already handled by ACLINT device tree bindings. We just need two separate MTIMER DT nodes where the mtimecmp base address will be different in each DT node.
