Hello! > As far as I understand Figure 1 in GICv3 architecture document the interrupts > from device goes to the distributor and from it to the > re-distributors or from the deices via the ITS to the re-distributors. > So eventually ITS should be part of the GIC. That is if the ITS is a > different entity how do you see it work with the rest of the GIC?
Easy. As i said before, what ITS actually does is transforming device ID + event ID into a single LPI number. Then, an LPI goes to the redistributor. Therefore, all we need from GIC is a method like inject_lpi(int lpi). Well, may be a couple more, for moving LPIs between collections. But this is not a problem and makes up a nice interface. Even on the picture you mentioned ITS is a kind of separate thing. It can even be completely missing. Well, my reasons end here. If you still disagree... Do what you want then, it will not be a problem to remove these unused stubs. Peter, we are summoning you. :) Kind regards, Pavel Fedin Expert Engineer Samsung Electronics Research center Russia