From: Sebastian Reichel <sre@ring0.de>
To: Eric Anholt <eric@anholt.net>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, Ulf Hansson <ulf.hansson@linaro.org>,
Florian Fainelli <f.fainelli@gmail.com>,
Alexander Aring <alex.aring@gmail.com>,
Pawel Moll <pawel.moll@arm.com>,
Stephen Warren <swarren@wwwdotorg.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-pm@vger.kernel.org, Lee Jones <lee@kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
linux-kernel@vger.kernel.org, Kevin Hilman <khilman@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
linux-rpi-kernel@lists.infradead.org,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 2/4] ARM: bcm2835: add rpi power domain driver
Date: Wed, 16 Dec 2015 02:11:11 +0100 [thread overview]
Message-ID: <20151216011110.GA13147@earth> (raw)
In-Reply-To: <87mvtbkyd0.fsf@eliezer.anholt.net>
[-- Attachment #1.1: Type: text/plain, Size: 1745 bytes --]
Hi,
On Tue, Dec 15, 2015 at 04:53:31PM -0800, Eric Anholt wrote:
> >>> What motivated the location of this power domain driver in
> >>> arch/arm/mach-bcm? Should not we have this in drivers/power/ or
> >>> somewhere in drivers/ at the very least?
> >>
> >> ls stronly suggests that power contains drivers for power supplies and
> >> batteries, not power domains.
Indeed it's used for fuel gauges and chargers, but also for
reboot/powerdown and adaptive voltage scaling, so another
subdirectory for power-domains wouldn't be that odd.
> >> There are 6 power domain drivers in
> >> arch/arm, 3 in drivers/clk, and 3 in drivers/soc.
> >
> > If we ever have to support a different architecture which happens to use
> > a similar power domain, then we want it to be in a location which makes
> > it easy for sharing it in the first place. As it stands today, it does
> > not seem useful to me to have this code in arch/arm/mach-bcm/ at all.
> >
> > Maybe there is room from a drivers/power/domains/ of some kind?
I like the idea, but let's include generic power domain maintainers
in this discussion, as I suggested here (I got a power domain driver
patch for drivers/power just a few days ago):
https://lkml.org/lkml/2015/12/15/815
Also somebody would have to step up to maintain that directory.
> The great thing about git is that moving code is easy, even after it's
> first committed.
>
> The subsystem maintainer didn't comment on the code's location in v1 or
> v2, and I think they probably have the final say on that. Whatever they
> want, where there is currently a genpd driver, is fine with me.
sounds reasonable.
P.S.: Thanks for taking bringing RPI support upstream :)
-- Sebastian
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: sre@ring0.de (Sebastian Reichel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 2/4] ARM: bcm2835: add rpi power domain driver
Date: Wed, 16 Dec 2015 02:11:11 +0100 [thread overview]
Message-ID: <20151216011110.GA13147@earth> (raw)
In-Reply-To: <87mvtbkyd0.fsf@eliezer.anholt.net>
Hi,
On Tue, Dec 15, 2015 at 04:53:31PM -0800, Eric Anholt wrote:
> >>> What motivated the location of this power domain driver in
> >>> arch/arm/mach-bcm? Should not we have this in drivers/power/ or
> >>> somewhere in drivers/ at the very least?
> >>
> >> ls stronly suggests that power contains drivers for power supplies and
> >> batteries, not power domains.
Indeed it's used for fuel gauges and chargers, but also for
reboot/powerdown and adaptive voltage scaling, so another
subdirectory for power-domains wouldn't be that odd.
> >> There are 6 power domain drivers in
> >> arch/arm, 3 in drivers/clk, and 3 in drivers/soc.
> >
> > If we ever have to support a different architecture which happens to use
> > a similar power domain, then we want it to be in a location which makes
> > it easy for sharing it in the first place. As it stands today, it does
> > not seem useful to me to have this code in arch/arm/mach-bcm/ at all.
> >
> > Maybe there is room from a drivers/power/domains/ of some kind?
I like the idea, but let's include generic power domain maintainers
in this discussion, as I suggested here (I got a power domain driver
patch for drivers/power just a few days ago):
https://lkml.org/lkml/2015/12/15/815
Also somebody would have to step up to maintain that directory.
> The great thing about git is that moving code is easy, even after it's
> first committed.
>
> The subsystem maintainer didn't comment on the code's location in v1 or
> v2, and I think they probably have the final say on that. Whatever they
> want, where there is currently a genpd driver, is fine with me.
sounds reasonable.
P.S.: Thanks for taking bringing RPI support upstream :)
-- Sebastian
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20151216/987f00f3/attachment.sig>
WARNING: multiple messages have this Message-ID (diff)
From: Sebastian Reichel <sre@ring0.de>
To: Eric Anholt <eric@anholt.net>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
linux-arm-kernel@lists.infradead.org,
linux-rpi-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Stephen Warren <swarren@wwwdotorg.org>,
Lee Jones <lee@kernel.org>, Kevin Hilman <khilman@kernel.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Alexander Aring <alex.aring@gmail.com>,
devicetree@vger.kernel.org, linux-pm@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>
Subject: Re: [PATCH v3 2/4] ARM: bcm2835: add rpi power domain driver
Date: Wed, 16 Dec 2015 02:11:11 +0100 [thread overview]
Message-ID: <20151216011110.GA13147@earth> (raw)
In-Reply-To: <87mvtbkyd0.fsf@eliezer.anholt.net>
[-- Attachment #1: Type: text/plain, Size: 1745 bytes --]
Hi,
On Tue, Dec 15, 2015 at 04:53:31PM -0800, Eric Anholt wrote:
> >>> What motivated the location of this power domain driver in
> >>> arch/arm/mach-bcm? Should not we have this in drivers/power/ or
> >>> somewhere in drivers/ at the very least?
> >>
> >> ls stronly suggests that power contains drivers for power supplies and
> >> batteries, not power domains.
Indeed it's used for fuel gauges and chargers, but also for
reboot/powerdown and adaptive voltage scaling, so another
subdirectory for power-domains wouldn't be that odd.
> >> There are 6 power domain drivers in
> >> arch/arm, 3 in drivers/clk, and 3 in drivers/soc.
> >
> > If we ever have to support a different architecture which happens to use
> > a similar power domain, then we want it to be in a location which makes
> > it easy for sharing it in the first place. As it stands today, it does
> > not seem useful to me to have this code in arch/arm/mach-bcm/ at all.
> >
> > Maybe there is room from a drivers/power/domains/ of some kind?
I like the idea, but let's include generic power domain maintainers
in this discussion, as I suggested here (I got a power domain driver
patch for drivers/power just a few days ago):
https://lkml.org/lkml/2015/12/15/815
Also somebody would have to step up to maintain that directory.
> The great thing about git is that moving code is easy, even after it's
> first committed.
>
> The subsystem maintainer didn't comment on the code's location in v1 or
> v2, and I think they probably have the final say on that. Whatever they
> want, where there is currently a genpd driver, is fine with me.
sounds reasonable.
P.S.: Thanks for taking bringing RPI support upstream :)
-- Sebastian
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-12-16 1:11 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-15 21:40 [PATCH v3 0/4] Raspberry Pi power domains Eric Anholt
2015-12-15 21:40 ` Eric Anholt
2015-12-15 21:40 ` [PATCH v3 1/4] ARM: bcm2835: Define two new packets from the latest firmware Eric Anholt
2015-12-15 21:40 ` Eric Anholt
2015-12-15 21:40 ` [PATCH v3 2/4] ARM: bcm2835: add rpi power domain driver Eric Anholt
2015-12-15 21:40 ` Eric Anholt
2015-12-15 22:27 ` Florian Fainelli
2015-12-15 22:27 ` Florian Fainelli
[not found] ` <567093CD.1020208-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-12-15 23:55 ` Eric Anholt
2015-12-15 23:55 ` Eric Anholt
2015-12-15 23:55 ` Eric Anholt
[not found] ` <87oadrmfmi.fsf-omZaPlIz5HhaEpDpdNBo/KxOck334EZe@public.gmane.org>
2015-12-16 0:05 ` Florian Fainelli
2015-12-16 0:05 ` Florian Fainelli
2015-12-16 0:05 ` Florian Fainelli
2015-12-16 0:53 ` Eric Anholt
2015-12-16 0:53 ` Eric Anholt
2015-12-16 1:11 ` Sebastian Reichel [this message]
2015-12-16 1:11 ` Sebastian Reichel
2015-12-16 1:11 ` Sebastian Reichel
2015-12-16 1:27 ` Krzysztof Kozlowski
2015-12-16 1:27 ` Krzysztof Kozlowski
2015-12-16 1:27 ` Krzysztof Kozlowski
2015-12-16 10:06 ` Ulf Hansson
2015-12-16 10:06 ` Ulf Hansson
2015-12-17 0:39 ` Eric Anholt
2015-12-17 0:39 ` Eric Anholt
2015-12-17 0:39 ` Eric Anholt
[not found] ` <1450215622-27394-1-git-send-email-eric-WhKQ6XTQaPysTnJN9+BGXg@public.gmane.org>
2015-12-15 21:40 ` [PATCH v3 3/4] dt-bindings: add rpi power domain driver bindings Eric Anholt
2015-12-15 21:40 ` Eric Anholt
2015-12-15 21:40 ` Eric Anholt
2015-12-15 21:40 ` [PATCH v3 4/4] ARM: bcm2835: Add the Raspberry Pi power domain driver to the DT Eric Anholt
2015-12-15 21:40 ` Eric Anholt
2015-12-17 16:33 ` [PATCH v3 0/4] Raspberry Pi power domains Ulf Hansson
2015-12-17 16:33 ` Ulf Hansson
2015-12-17 19:03 ` Eric Anholt
2015-12-17 19:03 ` Eric Anholt
2015-12-17 19:03 ` Eric Anholt
[not found] ` <878u4sx5gs.fsf-omZaPlIz5HhaEpDpdNBo/KxOck334EZe@public.gmane.org>
2015-12-17 20:11 ` Arnd Bergmann
2015-12-17 20:11 ` Arnd Bergmann
2015-12-17 20:11 ` Arnd Bergmann
2015-12-17 21:08 ` Ulf Hansson
2015-12-17 21:08 ` Ulf Hansson
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=20151216011110.GA13147@earth \
--to=sre@ring0.de \
--cc=alex.aring@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=eric@anholt.net \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=khilman@kernel.org \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=rjw@rjwysocki.net \
--cc=robh+dt@kernel.org \
--cc=swarren@wwwdotorg.org \
--cc=ulf.hansson@linaro.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.