[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YV00JD31EPD6WqlB@atomide.com>
Date: Wed, 6 Oct 2021 08:29:08 +0300
From: Tony Lindgren <tony@...mide.com>
To: Saravana Kannan <saravanak@...gle.com>
Cc: Russell King <linux@...linux.org.uk>,
Neil Armstrong <narmstrong@...libre.com>,
Geert Uytterhoeven <geert+renesas@...der.be>,
Magnus Damm <magnus.damm@...il.com>,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will@...nel.org>,
Damien Le Moal <damien.lemoal@....com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Ulf Hansson <ulf.hansson@...aro.org>,
Rob Herring <robh+dt@...nel.org>, kernel-team@...roid.com,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-oxnas@...ups.io, linux-renesas-soc@...r.kernel.org,
linux-omap@...r.kernel.org, linux-riscv@...ts.infradead.org
Subject: Re: [PATCH v4 0/2] Fix simple-bus issues with fw_devlink
* Saravana Kannan <saravanak@...gle.com> [210929 03:08]:
> Ulf reported an issue[1] with fw_devlink. This series tries to fix that
> issue.
>
> I replicated a similar set up on my end and I confirmed:
> - A simple-bus only device is probed.
> - Another device listing simple-bus as a 2nd compatible string isn't
> probed.
>
> v1->v2:
> - Switched to probing the simple-bus device instead of marking it as
> NEVER_PROBES.
>
> v2->v3:
> - Moved all the code into the simple-pm-bus driver
> - Addressed Ulf's comment about the remove() code missing a check.
>
> v3->v4:
> - Added support for driver_override to accommodate the case where new
> transparent bus compatible strings are added to DT, but the kernel hasn't
> been updated yet.
> - Added/updated comments to give more details.
> - Adding Ulf's Tested-by that he have for v3 (v4 didn't change by much).
Works for me:
Tested-by: Tony Lindgren <tony@...mide.com>
Powered by blists - more mailing lists