public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: lee.jones@linaro.org (Lee Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/3] Qualcomm Resource Power Manager driver
Date: Wed, 18 Jun 2014 17:48:22 +0100	[thread overview]
Message-ID: <20140618164822.GC25353@lee--X1> (raw)
In-Reply-To: <842A7147-A2CC-42BD-9947-CBADF738DC92@codeaurora.org>

On Wed, 18 Jun 2014, Kumar Gala wrote:

> 
> On Jun 18, 2014, at 10:53 AM, Kevin Hilman <khilman@linaro.org> wrote:
> 
> > 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
> 
> I dont agree, I think having this in drivers/soc means that we can
> clearly go through drivers/soc in the future and look for patterns
> across SoCs that should be re-factored.

> Where MFD seems like its become the new drivers misc.

Do you have any grounds for that statement?  I only know of one driver
which doesn't fit the bounds of a true MFD.  If you know of more, I'd
like to hear about it.

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org ? Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

  parent reply	other threads:[~2014-06-18 16:48 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
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
2014-06-18 16:03       ` Kumar Gala
2014-06-18 16:44         ` Kevin Hilman
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 [this message]
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=20140618164822.GC25353@lee--X1 \
    --to=lee.jones@linaro.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