linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: f.fainelli@gmail.com (Florian Fainelli)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 2/4] ARM: bcm2835: add rpi power domain driver
Date: Tue, 15 Dec 2015 14:27:25 -0800	[thread overview]
Message-ID: <567093CD.1020208@gmail.com> (raw)
In-Reply-To: <1450215622-27394-3-git-send-email-eric@anholt.net>

On 15/12/15 13:40, Eric Anholt wrote:
> From: Alexander Aring <alex.aring@gmail.com>
> 
> This patch adds support for several power domains on Raspberry Pi,
> including USB (so it can be enabled even if the bootloader didn't do
> it), and graphics.
> 
> This patch is the combined work of Eric Anholt (who wrote USB support
> inside of the Raspberry Pi firmware driver, and wrote the non-USB
> domain support) and Alexander Aring (who separated the original USB
> work out from the firmware driver).
> 
> Signed-off-by: Alexander Aring <alex.aring@gmail.com>
> Signed-off-by: Eric Anholt <eric@anholt.net>
> ---
> 
> v2: Add support for power domains other than USB, using the new
>     firmware interface, reword commit message (changes by Eric)
> 
> v3: Restructure as a builtin driver, and drop
>     of_genpd_add_provider_onecell error handling to avoid
>     pm_genpd_exit() dependency until that API can be settled.  Clean
>     up copyright header, add missing ISP initialization, and fix typo
>     in transposer's name.
> 
>  arch/arm/mach-bcm/Kconfig                   |  10 ++
>  arch/arm/mach-bcm/Makefile                  |   1 +
>  arch/arm/mach-bcm/raspberrypi-power.c       | 247 ++++++++++++++++++++++++++++
>  include/dt-bindings/arm/raspberrypi-power.h |  41 +++++
>  4 files changed, 299 insertions(+)
>  create mode 100644 arch/arm/mach-bcm/raspberrypi-power.c

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?
-- 
Florian

  reply	other threads:[~2015-12-15 22:27 UTC|newest]

Thread overview: 17+ 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 ` [PATCH v3 1/4] ARM: bcm2835: Define two new packets from the latest firmware Eric Anholt
2015-12-15 21:40 ` [PATCH v3 2/4] ARM: bcm2835: add rpi power domain driver Eric Anholt
2015-12-15 22:27   ` Florian Fainelli [this message]
2015-12-15 23:55     ` Eric Anholt
2015-12-16  0:05       ` Florian Fainelli
2015-12-16  0:53         ` Eric Anholt
2015-12-16  1:11           ` Sebastian Reichel
2015-12-16  1:27             ` Krzysztof Kozlowski
2015-12-16 10:06               ` Ulf Hansson
2015-12-17  0:39                 ` Eric Anholt
2015-12-15 21:40 ` [PATCH v3 3/4] dt-bindings: add rpi power domain driver bindings 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-17 16:33 ` [PATCH v3 0/4] Raspberry Pi power domains Ulf Hansson
2015-12-17 19:03   ` Eric Anholt
2015-12-17 20:11     ` Arnd Bergmann
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=567093CD.1020208@gmail.com \
    --to=f.fainelli@gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).