From: cov@codeaurora.org (Christopher Covington)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] soc: qcom: provide mechanism for drivers to access L2 registers
Date: Mon, 23 May 2016 18:26:25 -0400 [thread overview]
Message-ID: <57438391.7090405@codeaurora.org> (raw)
In-Reply-To: <f49d58ed-38b4-6284-11c2-8708d8443b14@codeaurora.org>
On 05/23/2016 02:22 PM, Neil Leeder wrote:
>
> On 5/23/2016 01:25 PM, Mark Rutland wrote:
>> On Fri, May 20, 2016 at 03:13:07PM -0400, Neil Leeder wrote:
>>> L2 registers are accessed using a select register and data
>>> register pair. To prevent multiple concurrent writes to the
>>> select register by independent drivers, the write to the
>>> select register and the associated access of the data register
>>> are protected with a lock. All drivers accessing the L2
>>> registers use the set and get functions provided by
>>> l2-accessors to ensure correct reads and writes to L2 registers.
>>
>> What will this be used for? (i.e. which drivers want to touch the L2
>> registers?).
>>
>> Generally we expect FW to configure the caches and interconnect
>> appropriately.
>
> The primary use is in the L2 PMU driver, which will be posted shortly.
>
>>
>>> Signed-off-by: Neil Leeder <nleeder@codeaurora.org>
>>> ---
>>> drivers/soc/qcom/Kconfig | 9 +++++
>>> drivers/soc/qcom/Makefile | 1 +
>>> drivers/soc/qcom/l2-accessors.c | 66 +++++++++++++++++++++++++++++++++++
>>> include/linux/soc/qcom/l2-accessors.h | 27 ++++++++++++++
>>> 4 files changed, 103 insertions(+)
>>> create mode 100644 drivers/soc/qcom/l2-accessors.c
>>> create mode 100644 include/linux/soc/qcom/l2-accessors.h
>>
>> These are awfully generic file names (and function names). Which SoCs
>> does this apply to?
>>
>> It would be good to give these more specific names.
>
> It's under soc/qcom, and dependent on ARCH_QCOM and (in v2) also on ARM64. It applies to all QCOM ARM64 SoCs.
> Given that it can only be used in a QCOM driver, and the include path has qcom in it, I'd
> prefer not to add redundancy by adding another qcom in there.
They ended up calling the pinctrl file qcom/pinctrl/qdf2xxx.c.
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=8f1338cd80648adf5434798f5393ad7c55d10848
Regards,
Cov
--
Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2016-05-23 22:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-20 19:13 [PATCH] soc: qcom: provide mechanism for drivers to access L2 registers Neil Leeder
2016-05-20 21:19 ` Stephen Boyd
2016-05-23 15:43 ` Neil Leeder
2016-05-23 17:04 ` Stephen Boyd
2016-05-23 18:12 ` Neil Leeder
2016-05-23 17:25 ` Mark Rutland
2016-05-23 18:22 ` Neil Leeder
2016-05-23 22:26 ` Christopher Covington [this message]
2016-05-23 23:04 ` Timur Tabi
2016-05-24 11:23 ` Mark Rutland
2016-05-24 19:54 ` Neil Leeder
2016-05-26 4:48 ` Bjorn Andersson
2016-05-26 20:38 ` Neil Leeder
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=57438391.7090405@codeaurora.org \
--to=cov@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).