RFC Representing interrupt affinity in devicetree
Get series with b4
b4 am 20130413213322.7C6193E2249@localhostVersions newest first · linked by author and title
- v2 RFC Latest posting 2/20 of 2 patches 0 repliesNew
- v2 RFC posting 1/20 of 2 patches 0 repliesSuperseded
Patches in v2 posting 2/2 No applies recorded yet
None of the 2 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v2 yet.
Cover letter [RFCv2 0/2] Representing interrupt affinity in devicetree
Quoted 22 lines · Mark Rutland
Quoted 5 lines · Grant Likely
I could use some more context for how this will be used. Do device drivers need to be aware of which CPU can handle an interrupt for a device, or is it the sort of thing that can be done in the background when an irq is requested? What are some examples of device drivers using this interface.
The main users I can think of for this would be PMUs in multi-cluster systems, where we may have differing PMUs in each cluster. The driver for each needs to know the set of CPUs it's handling, and which CPU each interrupt is affine to.
With the above binding scheme, we'd describe the A15x2 A7x3 CoreTile's PMUs something like:
pmu_a15s { compatible = "arm,cortex-a15-pmu"; interrupts = <0 68 4>, <0 69 4>; interrupts-affinity = <0 0x0>, <0 0x1>; };
Quoted 9 lines
pmu_a7s {
compatible = arm,cortex-a7-pmu";
interrupts = <0 128 4>,
<0 129 4>,
<0 130 4>;
interrupts-affinity = <0 0x100>,
<0 0x101>,
<0 0x102>;
};That does sound an awful lot like what Lorenzo has been trying to solve. I really do think that you need to coordinate with him.
g.