From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Rob Herring <robh@kernel.org>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
Mark Brown <broonie@kernel.org>,
devicetree@vger.kernel.org,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Saravana Kannan <saravanak@google.com>,
Ivan Bornyakov <i.bornyakov@metrotek.ru>,
Fabio Estevam <festevam@gmail.com>,
linux-i2c@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Frank Rowand <frowand.list@gmail.com>,
Shawn Guo <shawnguo@kernel.org>,
linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>,
NXP Linux Team <linux-imx@nxp.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
Wolfram Sang <wsa@kernel.org>
Subject: Re: [PATCH v3] treewide: Fix probing of devices in DT overlays
Date: Thu, 6 Apr 2023 07:01:40 +0200 [thread overview]
Message-ID: <ZC5SNLY6kw_BXjM6@kroah.com> (raw)
In-Reply-To: <168072737082.449372.6122824582508382689.robh@kernel.org>
On Wed, Apr 05, 2023 at 03:42:52PM -0500, Rob Herring wrote:
>
> On Thu, 30 Mar 2023 15:26:13 +0200, Geert Uytterhoeven wrote:
> > When loading a DT overlay that creates a device, the device is not
> > probed, unless the DT overlay is unloaded and reloaded again.
> >
> > After the recent refactoring to improve fw_devlink, it no longer depends
> > on the "compatible" property to identify which device tree nodes will
> > become struct devices. fw_devlink now picks up dangling consumers
> > (consumers pointing to descendent device tree nodes of a device that
> > aren't converted to child devices) when a device is successfully bound
> > to a driver. See __fw_devlink_pickup_dangling_consumers().
> >
> > However, during DT overlay, a device's device tree node can have
> > sub-nodes added/removed without unbinding/rebinding the driver. This
> > difference in behavior between the normal device instantiation and
> > probing flow vs. the DT overlay flow has a bunch of implications that
> > are pointed out elsewhere[1]. One of them is that the fw_devlink logic
> > to pick up dangling consumers is never exercised.
> >
> > This patch solves the fw_devlink issue by marking all DT nodes added by
> > DT overlays with FWNODE_FLAG_NOT_DEVICE (fwnode that won't become
> > device), and by clearing the flag when a struct device is actually
> > created for the DT node. This way, fw_devlink knows not to have
> > consumers waiting on these newly added DT nodes, and to propagate the
> > dependency to an ancestor DT node that has the corresponding struct
> > device.
> >
> > Based on a patch by Saravana Kannan, which covered only platform and spi
> > devices.
> >
> > [1] https://lore.kernel.org/r/CAGETcx_bkuFaLCiPrAWCPQz+w79ccDp6=9e881qmK=vx3hBMyg@mail.gmail.com
> >
> > Fixes: 4a032827daa89350 ("of: property: Simplify of_link_to_phandle()")
> > Link: https://lore.kernel.org/r/CAGETcx_+rhHvaC_HJXGrr5_WAd2+k5f=rWYnkCZ6z5bGX-wj4w@mail.gmail.com
> > Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> > Acked-by: Mark Brown <broonie@kernel.org>
> > Acked-by: Wolfram Sang <wsa@kernel.org> # for I2C
> > ---
> > v3:
> > - Add Acked-by,
> > - s/instantiate/probe/,
> > - Improve commit description,
> > - Add comment before clearing FWNODE_FLAG_NOT_DEVICE,
> >
> > v2:
> > - Add Acked-by,
> > - Drop RFC.
> > ---
> > drivers/bus/imx-weim.c | 6 ++++++
> > drivers/i2c/i2c-core-of.c | 5 +++++
> > drivers/of/dynamic.c | 1 +
> > drivers/of/platform.c | 5 +++++
> > drivers/spi/spi.c | 5 +++++
> > 5 files changed, 22 insertions(+)
> >
>
> Applied, thanks!
Oops, I thought I had to take this. I'll go drop it from my tree...
thanks,
greg k-h
prev parent reply other threads:[~2023-04-06 5:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 13:26 [PATCH v3] treewide: Fix probing of devices in DT overlays Geert Uytterhoeven
2023-03-30 19:54 ` Saravana Kannan
2023-03-31 10:18 ` Ivan Bornyakov
2023-04-05 14:27 ` Shawn Guo
2023-04-05 20:42 ` Rob Herring
2023-04-06 5:01 ` Greg Kroah-Hartman [this message]
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=ZC5SNLY6kw_BXjM6@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=frowand.list@gmail.com \
--cc=geert+renesas@glider.be \
--cc=i.bornyakov@metrotek.ru \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=saravanak@google.com \
--cc=shawnguo@kernel.org \
--cc=wsa@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox