Hi Marc,
On 2021/4/15 下午4:11, Marc Zyngier wrote:
Hi Kever,
On Thu, 15 Apr 2021 08:24:33 +0100,
Kever Yang <[email protected]> wrote:
Hi Marc, Peter,
RK356x GIC has two issues:
1. GIC only support 32bit address while rk356x supports 8GB DDR SDRAM,
so we use ZONE_DMA32 to fix this issue;
What transactions does this affect exactly?
The GIC on rk356x is a 32bit master, which means all the space its logic
need to access should be in the 4GB range.
Only some ITS tables? Or
all of them, including the command queue? What about the configuration
and pending tables associated with the redistributors?
2. GIC version is r1p6-00rel0, RK356x interconnect does not support
GIC and CPU snoop to each other, hence the GIC does not support the
shareability feature. The read of register value for shareability
feature does not return as expect in GICR and GITS, so we have to
workaround for it.
How about the cacheability attribute? Can you please provide the exact
set of attributes that this system actually supports for each of the
ITS and redistributor base registers?
The shareability attributes in GICR_PENDBASEER, GICR_PROPBASER,
GITS_BASERn, GITS_CBASER default value is 0b00, when we set 0b01 then
read returns 0b01.
Since there is no ACE coherency interface for this GIC controller, all
the cacheability in the GIC is not support in hardware.
Also, please provide errata numbers for these two issues so that we
can properly document them and track the workarounds.
What kind of errata do you need, could you please share any kind of
example close to this case?
We consider this as a SoC implement design instead of a bug, so we will
add document in RK356X TRM to describe the GIC design, but no idea how
to provide the errata.
Here is the shareabily attribute from ARM GIC architecture specification:
Shareability, bits [11:10] (from GITS_CBASER)
Indicates the Shareability attributes of accesses to the command queue.
The possible values of this field are:
0b00 Non-shareable.
0b01 Inner Shareable.
0b10 Outer Shareable.
0b11 Reserved. Treated as 0b00.
It is IMPLEMENTATION DEFINED whether this field has a fixed value or can
be programmed by software. Implementing this field with a fixed value is
deprecated.
On a Warm reset, this field resets to an architecturally UNKNOWN value
As you can see, "Implementing this field with a fixed value is
deprecated", so software should program this field to '0b00
Non-shareable' if the SoC design does not support the cache shareability.
Thanks,
- Kever
Thanks,
M.
