From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH] drivers: bus: add ARM CCI support
Date: Thu, 18 Apr 2013 11:11:53 -0700 [thread overview]
Message-ID: <51703769.10908@codeaurora.org> (raw)
In-Reply-To: <alpine.LFD.2.03.1304181341020.17375@syhkavp.arg>
On 04/18/13 10:54, Nicolas Pitre wrote:
> On Thu, 18 Apr 2013, Stephen Boyd wrote:
>
>> On 04/11/13 07:47, Lorenzo Pieralisi wrote:
>>> diff --git a/drivers/bus/arm-cci.c b/drivers/bus/arm-cci.c
>>> new file mode 100644
>>> index 0000000..81953de
>>> --- /dev/null
>>> +++ b/drivers/bus/arm-cci.c
>> [...]
>>> +static void notrace cci_port_control(unsigned int port, bool enable)
>>> +{
>>> + void __iomem *base = ports[port].base;
>>> +
>>> + if (!base)
>>> + return;
>>> +
>>> + writel_relaxed(enable, base + CCI_PORT_CTRL);
>>> + while (readl_relaxed(cci_ctrl_base + CCI_CTRL_STATUS) & 0x1)
>>> + ;
>> cpu_relax()?
> In some cases there is no more cache coherence when this is called and
> the hardware might not be in a good state to cope with whatever action
> people might be tempted to insert into cpu_relax(). After the CCI is
> disabled it is important to keep a low profile and not touch anything
> global. With some early hardware revision, even a DMB here was harmful.
Fair enough. Perhaps the code could use a comment to that effect.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
next prev parent reply other threads:[~2013-04-18 18:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-11 14:47 [RFC PATCH] ARM CCI support Lorenzo Pieralisi
2013-04-11 14:47 ` [RFC PATCH] drivers: bus: add " Lorenzo Pieralisi
2013-04-18 17:20 ` Stephen Boyd
2013-04-18 17:54 ` Nicolas Pitre
2013-04-18 18:11 ` Stephen Boyd [this message]
2013-04-22 14:24 ` Russell King - ARM Linux
2013-04-22 15:18 ` Nicolas Pitre
2013-04-19 11:21 ` Lorenzo Pieralisi
2013-04-23 13:52 ` Jon Medhurst (Tixy)
2013-04-23 14:27 ` Lorenzo Pieralisi
2013-04-23 16:28 ` Dave Martin
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=51703769.10908@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).