Thread (15 messages) flat view 15 messages, 3 authors, 2013-10-31

[PATCH v2 4/6] edac: Document Krait L1/L2 EDAC driver binding

From: Stephen Boyd <hidden>
Date: 2013-10-31 17:30:51
Also in: linux-arm-msm, linux-devicetree, lkml

On 10/30, Kumar Gala wrote:
On Oct 30, 2013, at 4:58 PM, Stephen Boyd wrote:
quoted
On 10/30/13 14:56, Kumar Gala wrote:
quoted
On Oct 30, 2013, at 4:48 PM, Stephen Boyd wrote:
quoted
On 10/30/13 14:45, Kumar Gala wrote:
quoted
On Oct 30, 2013, at 3:25 PM, Stephen Boyd wrote:
quoted
+l2-cache node containing the following properties:
Is the L1 interrupt not per core L1 cache (even if they are OR together at PIC)?
Yes it is per CPU. That is what the 0xf part of the cpus interrupts
property is showing.
Than why not have it in each cpu node?
Because that duplicates things unnecessarily? The cpus node can hold
things that are common to all CPUs to avoid duplication. If it was a
different PPI for each CPU then I would agree that we need to put it in
each cpu node.
Ok, I'll accept that as the binding is specific to Krait (and I assume all SoCs w/Krait wire this up to a common interrupt)
Can I take that as an ack? I'll resend with the s/an/a/ fix
today.

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help