[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJZ5v0j52eotamMABZpu3-L3mmW=MwJEtTHCu3j8tAA0dZJzzA@mail.gmail.com>
Date: Thu, 31 Aug 2023 14:58:47 +0200
From: "Rafael J. Wysocki" <rafael@...nel.org>
To: Ulf Hansson <ulf.hansson@...aro.org>
Cc: "Rafael J. Wysocki" <rafael@...nel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Arnd Bergmann <arnd@...db.de>, linux-pm@...r.kernel.org,
linux-kernel@...r.kernel.org, Olof Johansson <olof@...om.net>,
soc@...nel.org, linux-arm-kernel@...ts.infradead.org,
Sebastian Reichel <sebastian.reichel@...labora.com>
Subject: Re: [GIT PULL] ARM: SoC/genpd driver updates for v6.6
On Thu, Aug 31, 2023 at 1:37 PM Ulf Hansson <ulf.hansson@...aro.org> wrote:
>
> On Thu, 31 Aug 2023 at 11:33, Rafael J. Wysocki <rafael@...nel.org> wrote:
> >
> > On Wed, Aug 30, 2023 at 10:34 AM Ulf Hansson <ulf.hansson@...aro.org> wrote:
[cut]
> > > Please advise me on how to move forward.
> >
> > If I may suggest something, I would call this "pmdomain" instead of
> > "genpd". I don't think that /drivers/power/ is a particularly
> > suitable location for it, because it doesn't really have much to do
> > with power supplies and more to do with device PM.
>
> "pmdomain" is probably giving a reasonable good hint of what goes on
> in this subsystem. This works fine for me, thanks!
>
> >
> > Also, I would move drivers/base/power/domain.c to drivers/pmdomain/
> > (and rename it to something like core.c), because it would be a better
> > location for that fiile IMO.
>
> We could certainly do that, let's discuss it a bit more.
>
> Although, at this point I want to focus on the genpd providers, as to
> release some of the burden from arm-soc maintainers.
That's fine, it's just a suggestion.
The rationale is that the "core" code is used by the providers, so
putting it next to them would be more convenient in case it needs to
be modified along with the providers, for example.
> >
> > I can also handle future pull requests for this if that's fine with everyone.
>
> Thanks a lot for your offer! However, if a re-route is preferred (I
> think not?), this is probably better suited via arm-soc, as most
> changes are going to be arm platform specific.
Whichever works for you better.
Powered by blists - more mailing lists