Hi Shanker,Yes, but GICD_CTLR.DS is reversed bit not defined when accessing from non-secure.
On 06/02/17 02:17, Shanker Donthineni wrote:
On systems where it supports two security states, both the registerI'm afraid we don't have the same definition of GICD_CTLR.DS. In my copy
GICR_WAKE and GICD_IGROUPR accesses are RAZ/WI from non-secure.
The function gic_enable_redist() to wake/sleep redistributor is not
harmful at all, but it is confusing looking at the code. The current
code checks the single security state based on bit GICD_CTLR.DS which
is absolutely incorrect. The disable security bit GICD_CTLR.DS is RAZ
to non-secure.
of the architecture spec, it says:
"When this field is set to 1, all accesses to GICD_CTLR access the
single Security state view, and all bits are accessible".
^^^^^^^^^^^^^^^^^^^^^^^
This would tend to support my interpretation that once DS has been setI've verified three releases of GIC specs, all of them have the same definition of GICD_CTLR.
from the secure side, it becomes visible to all type of accesses.
The GICD_TYPE.SecurityExtn indicates whether the GICYes, and that's orthogonal to having set DS or not.
implementation supports two security states or only one security
state.
So clearly, we have a difference of interpretation. What part of the
spec is supporting yours?