Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@linaro.org>
To: Bjorn Andersson <bjorn@kryo.se>
Cc: Lee Jones <lee.jones@linaro.org>,
	Bjorn Andersson <bjorn.andersson@sonymobile.com>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>,
	Kumar Gala <galak@codeaurora.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-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	linux-arm-msm <linux-arm-msm@vger.kernel.org>,
	Paul Walmsley <paul@pwsan.com>
Subject: Re: [PATCH v3 0/3] Qualcomm Resource Power Manager driver
Date: Wed, 18 Jun 2014 08:53:40 -0700	[thread overview]
Message-ID: <7hzjha8b97.fsf@paris.lan> (raw)
In-Reply-To: <CAJAp7OhHr4Cgcp9pvQ3=MAie_zSnFJxG28Vf37qJ98BK7P1jaQ@mail.gmail.com> (Bjorn Andersson's message of "Tue, 17 Jun 2014 10:15:10 -0700")

Bjorn Andersson <bjorn@kryo.se> writes:

> On Tue, Jun 17, 2014 at 10:07 AM, Kevin Hilman <khilman@linaro.org> wrote:
>> +Paul Walmsley
>>
>> Bjorn Andersson <bjorn.andersson@sonymobile.com> writes:
>>
>>> 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.
>>>
>>> Changes since v2:
>>>   - Fix copy-paste error in dt binding
>>>   - Correct incomplete move from mfd to soc
>>>   - Correct const mistake in regulator driver
>>>
>>> Changes since v1:
>>>   - Moved rpm driver to drivers/soc
>>
>> I'm not sure I follow the motivation for having this under drivers/soc?
>>
> Hi Kevin,
>
> I've made the argument that to me this is conceptually a black box
> handling regulators, clocks and other stuff; hence similar to a PMIC,
> which would fit nicely into drivers/mfd.
>
> I still think this is the case and now that I look back I didn't get
> any pushback from Lee Jones so maybe the move was premature?

Yes, IMO, the move was premature, but hopefully the drivers/soc folks
can chime in an clarify the criteria for inclusion there.

Kevin

  reply	other threads:[~2014-06-18 15:53 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-16 18:46 [PATCH v3 0/3] Qualcomm Resource Power Manager driver Bjorn Andersson
2014-06-16 18:46 ` [PATCH v3 1/3] soc: devicetree: bindings: Add Qualcomm RPM DT binding Bjorn Andersson
2014-06-17 23:59   ` Stephen Boyd
     [not found]     ` <53A0D651.20605-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2014-06-18  5:19       ` Bjorn Andersson
2014-06-18  8:34     ` Srinivas Kandagatla
2014-06-18 19:16       ` Stephen Boyd
2014-07-04  6:05   ` Pramod Gurav
2014-06-16 18:46 ` [PATCH v3 2/3] soc: qcom-rpm: Driver for the Qualcomm RPM Bjorn Andersson
2014-07-04  6:16   ` pramod gurav
2014-06-16 18:46 ` [PATCH v3 3/3] regulator: qcom-rpm: Regulator driver " Bjorn Andersson
2014-06-17 17:07 ` [PATCH v3 0/3] Qualcomm Resource Power Manager driver Kevin Hilman
2014-06-17 17:15   ` Bjorn Andersson
2014-06-18 15:53     ` Kevin Hilman [this message]
2014-06-18 16:03       ` Kumar Gala
2014-06-18 16:44         ` Kevin Hilman
     [not found]           ` <7hegym6uca.fsf-4poPxKt068f/PtFMR13I2A@public.gmane.org>
2014-06-19  3:55             ` Jassi Brar
2014-06-19 18:22               ` Bjorn Andersson
2014-06-19 20:01                 ` Jassi Brar
2014-06-20  4:59                   ` Bjorn Andersson
2014-06-20  5:17           ` Bjorn Andersson
2014-06-20 13:18             ` Jassi Brar
2014-06-18 16:48         ` Lee Jones
2014-06-17 21:49 ` Srinivas Kandagatla

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=7hzjha8b97.fsf@paris.lan \
    --to=khilman@linaro.org \
    --cc=bjorn.andersson@sonymobile.com \
    --cc=bjorn@kryo.se \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=joshc@codeaurora.org \
    --cc=lee.jones@linaro.org \
    --cc=lgirdwood@gmail.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=paul@pwsan.com \
    --cc=robh+dt@kernel.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