From: Simon Horman <horms@verge.net.au>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 07/11] ARM: shmobile: r8a7740/armadillo legacy: Add A4MP pm domain support
Date: Mon, 27 Oct 2014 23:30:38 +0000 [thread overview]
Message-ID: <20141027233034.GA31257@verge.net.au> (raw)
In-Reply-To: <CAMuHMdWkM4jgWX7fL63e4WGwhpGt2W1R8Jx-q+dz0GmesrRsOw@mail.gmail.com>
On Mon, Oct 27, 2014 at 09:17:55AM +0100, Geert Uytterhoeven wrote:
> Hi Simon,
>
> On Mon, Oct 27, 2014 at 5:03 AM, Simon Horman <horms@verge.net.au> wrote:
> > On Thu, Oct 23, 2014 at 01:18:57PM +0200, Geert Uytterhoeven wrote:
> >> Add support for the A4MP power domain, and hook up the HDMI-Link and FSI
> >> hardware blocks.
> >> This domain also contains the SPU2, FMSI, and BBIF2 hardware blocks,
> >> but these are currently not used by any driver.
> >>
> >> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> >
> > Is it possible to split this into two patches.
> >
> > A board patch (that touches board-armadillo800eva.c)
> > and an SoC patch (the rest). Likewise for any remaining
> > patches in this series that touch both board and SoC code.
> >
> > The reason for this is that it would make the patches fit
> > the branch scheme that arm-soc people like. In particular splitting
> > patches between soc and boards branches.
>
> I kept them together as adding the PM domain without the devices will
> cause regressions (the PM domain core will power down the PM domain as
> it doesn't know about the to-be-added devices, and thus thinks it's unused).
>
> As the link from a device to a PM domain is a name string, and not a
> C reference, I could split them in two parts: first the board part
> that adds some
> devices, and then the SoC part that adds the PM domain and more devices.
> But only if you can guarantee that the SoC part will be merged first, also
> by arm-soc and Linus.
>
> Still, I prefer to keep them together. Hooking up devices to PM domains is
> SoC-specific, not board specific (for DT it lives in the .dtsi). It's
> unfortunate this code is in the board-specific C files due to board-specific
> configuration (cfr. .dts overriding/extending .dtsi).
>
> What do you think? Do you agree?
Hi Geert, thanks for the explanation. I agree that it makes sense
to keep things together. I'll see about queuing-up your series as-is.
next prev parent reply other threads:[~2014-10-27 23:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-23 11:18 [PATCH v3 00/11] ARM: shmobile: r8a7740/armadillo800eva legacy PM domain support Geert Uytterhoeven
2014-10-23 11:18 ` [PATCH v3 01/11] ARM: shmobile: r8a7740: Add missing A3SP pm domain devices Geert Uytterhoeven
2014-10-27 3:55 ` Simon Horman
2014-10-23 11:18 ` [PATCH v3 02/11] ARM: shmobile: r8a7740: Add missing A4S " Geert Uytterhoeven
2014-10-27 3:56 ` Simon Horman
2014-10-23 11:18 ` [PATCH v3 03/11] ARM: shmobile: armadillo800eva legacy: Add missing A3SP " Geert Uytterhoeven
2014-10-23 11:18 ` [PATCH v3 04/11] ARM: shmobile: armadillo800eva legacy: Add missing A4S " Geert Uytterhoeven
2014-10-27 3:56 ` Simon Horman
2014-10-27 3:59 ` Simon Horman
2014-10-23 11:18 ` [PATCH v3 05/11] ARM: shmobile: r8a7740: Add A3RV pm domain support Geert Uytterhoeven
2014-10-27 3:57 ` Simon Horman
2014-10-23 11:18 ` [PATCH v3 06/11] ARM: shmobile: r8a7740: Add A3SG " Geert Uytterhoeven
2014-10-27 4:00 ` Simon Horman
2014-10-23 11:18 ` [PATCH v3 07/11] ARM: shmobile: r8a7740/armadillo legacy: Add A4MP " Geert Uytterhoeven
2014-10-27 4:03 ` Simon Horman
2014-10-27 8:17 ` Geert Uytterhoeven
2014-10-27 23:30 ` Simon Horman [this message]
2014-10-23 11:18 ` [PATCH v3 08/11] ARM: shmobile: r8a7740: Add D4 " Geert Uytterhoeven
2014-10-23 11:18 ` [PATCH v3 09/11] ARM: shmobile: r8a7740/armadillo legacy: Add A4R " Geert Uytterhoeven
2014-10-23 11:19 ` [PATCH v3 10/11] ARM: shmobile: r8a7740: Add A4SU " Geert Uytterhoeven
2014-10-23 11:19 ` [PATCH v3 11/11] ARM: shmobile: r8a7740: Add A3SM " Geert Uytterhoeven
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=20141027233034.GA31257@verge.net.au \
--to=horms@verge.net.au \
--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).