From: Kumar Gala <galak@codeaurora.org>
To: Bjorn Andersson <bjorn@kryo.se>
Cc: Bjorn Andersson <bjorn.andersson@sonymobile.com>,
Samuel Ortiz <sameo@linux.intel.com>,
Lee Jones <lee.jones@linaro.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Josh Cartwright <joshc@codeaurora.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>
Subject: Re: [PATCH 0/3] Qualcomm Resource Power Manager driver
Date: Wed, 28 May 2014 12:06:32 -0500 [thread overview]
Message-ID: <8CA95B37-E5EE-46BE-ABFD-64AA3BBF4E96@codeaurora.org> (raw)
In-Reply-To: <CAJAp7Ojb7PvuNYJkPyKx+iehi0bF6rdYvYmfrDz21mebxMN1qg@mail.gmail.com>
On May 28, 2014, at 11:59 AM, Bjorn Andersson <bjorn@kryo.se> wrote:
> On Wed, May 28, 2014 at 9:23 AM, Kumar Gala <galak@codeaurora.org> wrote:
>>
>> On May 27, 2014, at 12:28 PM, Bjorn Andersson <bjorn.andersson@sonymobile.com> wrote:
>>
>>> This series adds a regulator driver for the Resource Power Manager found in
>>> Qualcomm 8660, 8960 and 8064 based devices.
>>>
>>> The RPM driver exposes resources to its child devices, that can be accessed to
>>> implement drivers for the regulators, clocks and bus frequency control that's
>>> owned by the RPM in these devices.
>>
>> Rather than adding yet another mfd driver, how about we put this in drivers/soc/qcom as a much better location for the low level rpm code. Some code already merged in arm-soc for creation of drivers/soc/qcom/
>
> Hi Kumar,
>
> I do see rpm as somewhat equivalent to a pmic and that was why I
> followed suite and put it in mfd, but I can of course move it if you
> prefer.
>
>
> Lately I've been working on rpm, rpm-smd, smem, smd, smsm, smp2p
> patches for mainline.
> It could be argued that smd is a bus and should go in drivers/bus, but
> for the rest I fear that we just created drivers/soc/qcom as another
> dumping ground for things; a "Qualcomm specific drivers/mfd".
>
> But maybe that is the purpose of it ;)
It is the purpose so that as we see common patterns between either drivers/soc/<VENDOR> we can refactor in the future. However, we need to all a little time for those patterns to emerge rather than shoe horning in drivers into places that don’t make sense.
>
> If I move the rpm driver, are there any conclusion to where I should
> move the dt binding documentation?
devicetree/bindings/soc/qcom
include/dt-bindings/soc
>
> Regards,
> Bjorn
- 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:[~2014-05-28 17:06 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-27 17:28 Bjorn Andersson
2014-05-27 17:28 ` [PATCH 1/3] mfd: devicetree: bindings: Add Qualcomm RPM DT binding Bjorn Andersson
2014-05-28 16:34 ` Kumar Gala
2014-05-29 18:24 ` Bjorn Andersson
2014-05-29 22:32 ` Frank Rowand
2014-05-29 16:19 ` Srinivas Kandagatla
2014-05-29 16:30 ` Kumar Gala
2014-05-29 17:09 ` Srinivas Kandagatla
2014-05-29 18:38 ` Bjorn Andersson
2014-05-29 21:25 ` Srinivas Kandagatla
2014-05-29 16:54 ` Lee Jones
2014-05-29 19:05 ` Bjorn Andersson
2014-05-27 17:28 ` [PATCH 2/3] mfd: qcom-rpm: Driver for the Qualcomm RPM Bjorn Andersson
2014-05-29 16:19 ` Srinivas Kandagatla
2014-05-29 19:45 ` Bjorn Andersson
2014-05-29 21:41 ` Srinivas Kandagatla
2014-05-29 22:11 ` Bjorn Andersson
2014-05-27 17:28 ` [PATCH 3/3] regulator: qcom-rpm: Regulator driver " Bjorn Andersson
2014-05-28 16:55 ` Mark Brown
2014-05-29 21:03 ` Bjorn Andersson
2014-05-29 21:18 ` Mark Brown
2014-05-29 21:59 ` Bjorn Andersson
2014-05-29 22:04 ` Mark Brown
2014-05-28 16:23 ` [PATCH 0/3] Qualcomm Resource Power Manager driver Kumar Gala
2014-05-28 16:59 ` Bjorn Andersson
2014-05-28 17:06 ` Kumar Gala [this message]
2014-05-29 18:14 ` Bjorn Andersson
2014-06-02 8:15 ` Stanimir Varbanov
2014-06-02 10:01 ` Mark 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=8CA95B37-E5EE-46BE-ABFD-64AA3BBF4E96@codeaurora.org \
--to=galak@codeaurora.org \
--cc=bjorn.andersson@sonymobile.com \
--cc=bjorn@kryo.se \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=joshc@codeaurora.org \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sameo@linux.intel.com \
/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