From: nleeder@codeaurora.org (Neil Leeder)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] soc: qcom: provide mechanism for drivers to access L2 registers
Date: Thu, 26 May 2016 16:38:48 -0400 [thread overview]
Message-ID: <3b834d0f-dc8e-86da-0bbd-f7ec72618f5d@codeaurora.org> (raw)
In-Reply-To: <20160526044810.GW1256@tuxbot>
On 5/26/2016 12:48 AM, Bjorn Andersson wrote:
> On Tue 24 May 12:54 PDT 2016, Neil Leeder wrote:
>
>>
>>
>> On 5/24/2016 07:23 AM, Mark Rutland wrote:
>>> On Mon, May 23, 2016 at 02:22:59PM -0400, 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:
>>
>>>>>> 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.
>>>
>>> Per Christopher's comment, it sounds like this applies to QDF24xx.
>>>
>>> Given that the code uses IMPLEMENTATION DEFINED system registers, I
>>> presume that this does not apply to MSM8916 which uses Cortex-A53, for
>>> example (though perhaps it does, and I am mistaken).
>>>
>>>> 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.
>>>
>>> I'm not asking for another "qcom", but simply the SoC variant or family
>>> (e.g. "qdf24xx" would be fine).
>>>
>>
>> It applies to all ARMv8 SoCs with QCOM processors in them. So QDF24xx
>> and mobile 820, but not SoCs with ARM processors in them such as
>> MSM8916. So neither msm_ nor qdf_ are accurate prefixes.
>
> What's the code name for the SoC in QDF24xx? The 820 is Kryo, is it the
> same core in QDF24xx or does that have some other name.
>
> We should try to pick something adding value, not adding another generic
> thing.
There is currently no public name for the QDF24xx core.
>
>> As Timur pointed out, the majority of source files in drivers/soc/qcom
>> don't have any prefix, which is a reason why I didn't include one.
>>
>
> There's no reason to add a generic "qcom" to the qcom folder, if
> anything we should drop the "qcom" prefix of the only one in there.
>
> Regards,
> Bjorn
>
Neil
--
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project.
prev parent reply other threads:[~2016-05-26 20:38 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
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 [this message]
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=3b834d0f-dc8e-86da-0bbd-f7ec72618f5d@codeaurora.org \
--to=nleeder@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).