From: Timur Tabi <timur@codeaurora.org>
To: Christopher Covington <cov@codeaurora.org>,
Neil Leeder <nleeder@codeaurora.org>,
Mark Rutland <mark.rutland@arm.com>
Cc: David Brown <david.brown@linaro.org>,
Andy Gross <andy.gross@linaro.org>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Mark Langsdorf <mlangsdo@redhat.com>,
Mark Salter <msalter@redhat.com>, Jon Masters <jcm@redhat.com>,
ashwin.chaugule@linaro.org, sboyd@codeaurora.org
Subject: Re: [PATCH] soc: qcom: provide mechanism for drivers to access L2 registers
Date: Mon, 23 May 2016 18:04:44 -0500 [thread overview]
Message-ID: <57438C8C.7050109@codeaurora.org> (raw)
In-Reply-To: <57438391.7090405@codeaurora.org>
Christopher Covington wrote:
> 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
To be fair, none of the other drivers in drivers/soc/ specify any
specific SOCs. They all have generic file names.
--
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora
Forum, a Linux Foundation collaborative project.
WARNING: multiple messages have this Message-ID (diff)
From: timur@codeaurora.org (Timur Tabi)
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:04:44 -0500 [thread overview]
Message-ID: <57438C8C.7050109@codeaurora.org> (raw)
In-Reply-To: <57438391.7090405@codeaurora.org>
Christopher Covington wrote:
> 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
To be fair, none of the other drivers in drivers/soc/ specify any
specific SOCs. They all have generic file names.
--
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora
Forum, a Linux Foundation collaborative project.
next prev parent reply other threads:[~2016-05-23 23:04 UTC|newest]
Thread overview: 26+ 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 19:13 ` Neil Leeder
2016-05-20 21:19 ` Stephen Boyd
2016-05-20 21:19 ` Stephen Boyd
2016-05-23 15:43 ` Neil Leeder
2016-05-23 15:43 ` Neil Leeder
2016-05-23 17:04 ` Stephen Boyd
2016-05-23 17:04 ` Stephen Boyd
2016-05-23 18:12 ` Neil Leeder
2016-05-23 18:12 ` Neil Leeder
2016-05-23 17:25 ` Mark Rutland
2016-05-23 17:25 ` Mark Rutland
2016-05-23 18:22 ` Neil Leeder
2016-05-23 18:22 ` Neil Leeder
2016-05-23 22:26 ` Christopher Covington
2016-05-23 22:26 ` Christopher Covington
2016-05-23 23:04 ` Timur Tabi [this message]
2016-05-23 23:04 ` Timur Tabi
2016-05-24 11:23 ` Mark Rutland
2016-05-24 11:23 ` Mark Rutland
2016-05-24 19:54 ` Neil Leeder
2016-05-24 19:54 ` Neil Leeder
2016-05-26 4:48 ` Bjorn Andersson
2016-05-26 4:48 ` Bjorn Andersson
2016-05-26 20:38 ` Neil Leeder
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=57438C8C.7050109@codeaurora.org \
--to=timur@codeaurora.org \
--cc=andy.gross@linaro.org \
--cc=ashwin.chaugule@linaro.org \
--cc=cov@codeaurora.org \
--cc=david.brown@linaro.org \
--cc=jcm@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mlangsdo@redhat.com \
--cc=msalter@redhat.com \
--cc=nleeder@codeaurora.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.