From: Saravana Kannan <firstname.lastname@example.org>
To: Marek Szyprowski <email@example.com>,
Greg Kroah-Hartman <firstname.lastname@example.org>
Cc: Russell King <email@example.com>,
Philipp Zabel <firstname.lastname@example.org>,
Rob Herring <email@example.com>,
Ulf Hansson <firstname.lastname@example.org>,
John Stultz <email@example.com>,
Linus Walleij <firstname.lastname@example.org>,
Sudeep Holla <email@example.com>,
Nicolas Saenz Julienne <firstname.lastname@example.org>,
Geert Uytterhoeven <email@example.com>,
Android Kernel Team <firstname.lastname@example.org>,
Subject: Re: [PATCH v3] amba: Remove deferred device addition
Date: Tue, 24 Aug 2021 12:26:16 -0700 [thread overview]
Message-ID: <CAGETcx8b228nDUho3cX9AAQ-pXOfZTMv8cj2vhdx9yc_pk8q+A@mail.gmail.com> (raw)
On Mon, Mar 8, 2021 at 11:15 AM Saravana Kannan <email@example.com> wrote:
> On Sun, Mar 7, 2021 at 11:28 PM Marek Szyprowski
> <firstname.lastname@example.org> wrote:
> > Hi Saravana,
> > On 05.03.2021 19:02, Saravana Kannan wrote:
> > > On Fri, Mar 5, 2021 at 3:45 AM Marek Szyprowski
> > > <email@example.com> wrote:
> > >> On 04.03.2021 20:51, Saravana Kannan wrote:
> > >>> The uevents generated for an amba device need PID and CID information
> > >>> that's available only when the amba device is powered on, clocked and
> > >>> out of reset. So, if those resources aren't available, the information
> > >>> can't be read to generate the uevents. To workaround this requirement,
> > >>> if the resources weren't available, the device addition was deferred and
> > >>> retried periodically.
> > >>>
> > >>> However, this deferred addition retry isn't based on resources becoming
> > >>> available. Instead, it's retried every 5 seconds and causes arbitrary
> > >>> probe delays for amba devices and their consumers.
> > >>>
> > >>> Also, maintaining a separate deferred-probe like mechanism is
> > >>> maintenance headache.
> > >>>
> > >>> With this commit, instead of deferring the device addition, we simply
> > >>> defer the generation of uevents for the device and probing of the device
> > >>> (because drivers needs PID and CID to match) until the PID and CID
> > >>> information can be read. This allows us to delete all the amba specific
> > >>> deferring code and also avoid the arbitrary probing delays.
> > >>>
> > >>> Cc: Rob Herring <firstname.lastname@example.org>
> > >>> Cc: Ulf Hansson <email@example.com>
> > >>> Cc: John Stultz <firstname.lastname@example.org>
> > >>> Cc: Saravana Kannan <email@example.com>
> > >>> Cc: Linus Walleij <firstname.lastname@example.org>
> > >>> Cc: Sudeep Holla <email@example.com>
> > >>> Cc: Nicolas Saenz Julienne <firstname.lastname@example.org>
> > >>> Cc: Geert Uytterhoeven <email@example.com>
> > >>> Cc: Marek Szyprowski <firstname.lastname@example.org>
> > >>> Cc: Russell King <email@example.com>
> > >>> Signed-off-by: Saravana Kannan <firstname.lastname@example.org>
> > >>> ---
> > >>>
> > >>> v1 -> v2:
> > >>> - Dropped RFC tag
> > >>> - Complete rewrite to not use stub devices.
> > >>> v2 -> v3:
> > >>> - Flipped the if() condition for hard-coded periphids.
> > >>> - Added a stub driver to handle the case where all amba drivers are
> > >>> modules loaded by uevents.
> > >>> - Cc Marek after I realized I forgot to add him.
> > >>>
> > >>> Marek,
> > >>>
> > >>> Would you mind testing this? It looks okay with my limited testing.
> > >> It looks it works fine on my test systems. I've checked current
> > >> linux-next and this patch. You can add:
> > >>
> > >> Tested-by: Marek Szyprowski <email@example.com>
> > > Hi Marek,
> > >
> > > Thanks! Does your test set up have amda drivers that are loaded based
> > > on uevents? That's the one I couldn't test.
> > I've checked both, the built-in and all amba drivers compiled as
> > modules, loaded by udev. Both works fine here.
> > >> I've briefly scanned the code and I'm curious how does it work. Does it
> > >> depend on the recently introduced "fw_devlink=on" feature? I don't see
> > >> other mechanism, which would trigger matching amba device if pm domains,
> > >> clocks or resets were not available on time to read pid/cid while adding
> > >> a device...
> > > No, it does not depend on fw_devlink or device links in any way.
> > >
> > > When a device is attempted to be probed (when it's added or during
> > > deferred probe), it's matched with all the drivers on the bus.
> > > When a new driver is registered to a bus, all devices in that bus are
> > > matched with the driver to see if they'll work together.
> > > That's how match is called. And match() can return -EPROBE_DEFER and
> > > that'll cause the device to be put in the deferred probe list by
> > > driver core.
> > >
> > > The tricky part in this patch was the uevent handling and the
> > > chicken-and-egg issue I talk about in the comments.
> > Thanks for the explanation. This EPROBE_DEFER support in match()
> > callback must be something added after I crafted that periodic retry
> > based workaround.
> I think it got in just a few months before your patches, but your
> patches worked :) I actually don't like match returning -EPROBE_DEFER,
> but I can work around it for some of my fw_devlink optimization plans.
> More context here:
I just noticed that this still hasn't been picked up.
Russell/Greg, can we please pick this up. This finally cleans up
deferred probing of AMBA devices so that they don't have any special
next prev parent reply other threads:[~2021-08-24 19:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20210304195109eucas1p1779060378305d0f9a1eb0c7ddefd1db3@eucas1p1.samsung.com>
2021-03-04 19:51 ` [PATCH v3] amba: Remove deferred device addition Saravana Kannan
2021-03-05 11:45 ` Marek Szyprowski
2021-03-05 18:02 ` Saravana Kannan
2021-03-08 7:28 ` Marek Szyprowski
2021-03-08 19:15 ` Saravana Kannan
2021-08-24 19:26 ` Saravana Kannan [this message]
2021-08-27 8:54 ` Greg Kroah-Hartman
2021-08-27 19:15 ` Saravana Kannan
2021-08-27 19:36 ` Greg Kroah-Hartman
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).