From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Sudeep Holla <sudeep.holla@arm.com>,
Saravana Kannan <saravanak@google.com>
Cc: Philipp Zabel <p.zabel@pengutronix.de>,
Rob Herring <robh@kernel.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
Linus Walleij <linus.walleij@linaro.org>,
Nicolas Saenz Julienne <nsaenzjulienne@suse.de>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Kefeng Wang <wangkefeng.wang@huawei.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
kernel-team@android.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5] amba: Remove deferred device addition
Date: Thu, 21 Jul 2022 09:49:47 +0100 [thread overview]
Message-ID: <YtkTK3QS0PQ2LRpM@shell.armlinux.org.uk> (raw)
In-Reply-To: <20220720131221.azqfidkry3cwiarw@bogus>
On Wed, Jul 20, 2022 at 02:12:21PM +0100, Sudeep Holla wrote:
> On Tue, Jul 19, 2022 at 11:20:10AM -0700, 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 <robh@kernel.org>
> > Cc: Ulf Hansson <ulf.hansson@linaro.org>
> > Cc: Saravana Kannan <saravanak@google.com>
> > Cc: Linus Walleij <linus.walleij@linaro.org>
> > Cc: Sudeep Holla <sudeep.holla@arm.com>
>
> Tested-by: Sudeep Holla <sudeep.holla@arm.com>
>
> on Juno with linux-next(which had the reported issue [1]) + this patch(which
> fixes the issue)
Ok, but this patch needs to end up in the patch system for me to apply
it. Can someone please add "KernelVersion: 5.19-rc7" or whatever version
the patch was generated against (just the tagged version is sufficient)
somewhere in the email, and send it to patches@armlinu.org.uk.
Thanks.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2022-07-21 8:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-19 18:20 [PATCH v5] amba: Remove deferred device addition Saravana Kannan
2022-07-20 13:12 ` Sudeep Holla
2022-07-21 8:49 ` Russell King (Oracle) [this message]
2022-07-21 11:30 ` Lee Jones
2022-07-21 21:58 ` Saravana Kannan
2022-07-27 7:43 ` Greg Kroah-Hartman
2022-07-27 7:53 ` Russell King (Oracle)
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=YtkTK3QS0PQ2LRpM@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=geert+renesas@glider.be \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-team@android.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=nsaenzjulienne@suse.de \
--cc=p.zabel@pengutronix.de \
--cc=robh@kernel.org \
--cc=saravanak@google.com \
--cc=sudeep.holla@arm.com \
--cc=ulf.hansson@linaro.org \
--cc=wangkefeng.wang@huawei.com \
/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