From: Kumar Gala <galak@codeaurora.org>
To: Stephen Boyd <sboyd@codeaurora.org>
Cc: linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org
Subject: Re: [PATCH v2 4/6] edac: Document Krait L1/L2 EDAC driver binding
Date: Thu, 31 Oct 2013 12:44:39 -0500 [thread overview]
Message-ID: <C796381F-AE3B-4577-BC97-DA041E5F40E8@codeaurora.org> (raw)
In-Reply-To: <20131031173047.GK21983@codeaurora.org>
On Oct 31, 2013, at 12:30 PM, Stephen Boyd wrote:
> On 10/30, Kumar Gala wrote:
>>
>> On Oct 30, 2013, at 4:58 PM, Stephen Boyd wrote:
>>
>>> On 10/30/13 14:56, Kumar Gala wrote:
>>>> On Oct 30, 2013, at 4:48 PM, Stephen Boyd wrote:
>>>>
>>>>> On 10/30/13 14:45, Kumar Gala wrote:
>>>>>> On Oct 30, 2013, at 3:25 PM, Stephen Boyd wrote:
>>>>>>> +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.
Yes, you can take that as an ack.
- k
--
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
next prev parent reply other threads:[~2013-10-31 17:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-30 20:25 [PATCH v2 0/6] Krait L1/L2 EDAC driver Stephen Boyd
2013-10-30 20:25 ` [PATCH v2 1/6] edac: Don't try to cancel workqueue when it's never setup Stephen Boyd
2013-10-30 20:25 ` [PATCH v2 2/6] genirq: export percpu irq functions for module usage Stephen Boyd
2013-10-30 20:25 ` [PATCH v2 3/6] ARM: Add Krait L2 accessor functions Stephen Boyd
2013-10-30 20:25 ` [PATCH v2 4/6] edac: Document Krait L1/L2 EDAC driver binding Stephen Boyd
2013-10-30 21:45 ` Kumar Gala
2013-10-30 21:48 ` Stephen Boyd
2013-10-30 21:56 ` Kumar Gala
2013-10-30 21:58 ` Stephen Boyd
2013-10-30 22:02 ` Kumar Gala
2013-10-31 17:30 ` Stephen Boyd
2013-10-31 17:44 ` Kumar Gala [this message]
2013-10-30 20:25 ` [PATCH v2 5/6] edac: Add support for Krait CPU cache error detection Stephen Boyd
2013-10-30 20:25 ` [PATCH v2 6/6] ARM: dts: msm: Add Krait CPU/L2 nodes Stephen Boyd
2013-10-30 20:27 ` David Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=C796381F-AE3B-4577-BC97-DA041E5F40E8@codeaurora.org \
--to=galak@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=sboyd@codeaurora.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome