All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: Saravana Kannan <saravanak@google.com>,
	Rob Herring <robh+dt@kernel.org>,
	Frank Rowand <frowand.list@gmail.com>,
	Android Kernel Team <kernel-team@android.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	DTML <devicetree@vger.kernel.org>
Subject: Re: [PATCH v2 1/2] of: platform: Make sure bus only devices get probed
Date: Tue, 7 Sep 2021 12:52:21 +0200	[thread overview]
Message-ID: <CAMuHMdVawd1_twGnWE7GzbPKXeKr+gCCXfodiBdECLScHRTBag@mail.gmail.com> (raw)
In-Reply-To: <CAPDyKFrGyOWSxe=0DGWNQ75YQgXVa62WF8=pOHNCWUh5PLcdqQ@mail.gmail.com>

Hi Ulf,

On Tue, Sep 7, 2021 at 12:36 PM Ulf Hansson <ulf.hansson@linaro.org> wrote:
> On Fri, 3 Sept 2021 at 16:29, Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> > On Fri, Sep 3, 2021 at 11:19 AM Ulf Hansson <ulf.hansson@linaro.org> wrote:
> > > On Fri, 3 Sept 2021 at 01:04, Saravana Kannan <saravanak@google.com> wrote:
> > > > fw_devlink could end up creating device links for bus only devices.
> > > > However, bus only devices don't get probed and can block probe() or
> > > > sync_state() [1] call backs of other devices. To avoid this, set up
> > > > these devices to get probed by the simple-pm-bus.
> > > >
> > > > [1] - https://lore.kernel.org/lkml/CAPDyKFo9Bxremkb1dDrr4OcXSpE0keVze94Cm=zrkOVxHHxBmQ@mail.gmail.com/
> > > > Signed-off-by: Saravana Kannan <saravanak@google.com>
> > > > Tested-by: Saravana Kannan <saravanak@google.com>
> > >
> > > Again, this looks like a nice solution to the problem.
> > >
> > > One question though. The Kconfig SIMPLE_PM_BUS, should probably be
> > > "default y" - or something along those lines to make sure fw_devlink
> > > works as expected.
> >
> > I would love for SIMPLE_PM_BUS to go away, and all of its functionality
> > to be usurped by the standard simple-bus handling.
> >
> > In the modern world, everything uses power management and Runtime
> > PM, and the distinction between "simple-bus" and "simple-pm-bus"
> > is purely artificial.
>
> I think it's not that easy, but maybe I am wrong.
>
> Today we have an opt-in way of supporting runtime PM (and power
> management). In most cases it's up to drivers or subsystem level code
> to decide if runtime PM should be enabled for the device.
>
> Would it really be okay to enable runtime PM for all of them?

You're talking about the software policy side.

From my PoV, the issue is that this decision is leaked into DT, through
the different compatible values ("simple-pm-bus" vs. "simple-bus").

Gr{oetje,eeting}s,

                        Geert

-- 
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

  reply	other threads:[~2021-09-07 10:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-02 23:04 [PATCH v2 0/2] Fix simple-bus issues with fw_devlink Saravana Kannan
2021-09-02 23:04 ` [PATCH v2 1/2] of: platform: Make sure bus only devices get probed Saravana Kannan
2021-09-03  9:18   ` Ulf Hansson
2021-09-03 14:29     ` Geert Uytterhoeven
2021-09-03 17:09       ` Saravana Kannan
2021-09-03 19:06         ` Geert Uytterhoeven
2021-09-03 19:08           ` Saravana Kannan
2021-09-07 10:35       ` Ulf Hansson
2021-09-07 10:52         ` Geert Uytterhoeven [this message]
2021-09-07 11:02           ` Ulf Hansson
2021-09-02 23:04 ` [PATCH v2 2/2] drivers: bus: simple-pm-bus: Add support for probing simple bus only devices Saravana Kannan
2021-09-03  9:14   ` Ulf Hansson
2021-09-03 17:10     ` Saravana Kannan

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=CAMuHMdVawd1_twGnWE7GzbPKXeKr+gCCXfodiBdECLScHRTBag@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --cc=devicetree@vger.kernel.org \
    --cc=frowand.list@gmail.com \
    --cc=kernel-team@android.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=saravanak@google.com \
    --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.