[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20251031152930.3c51a313@bootlin.com>
Date: Fri, 31 Oct 2025 15:29:30 +0100
From: Herve Codina <herve.codina@...tlin.com>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: Andrew Lunn <andrew@...n.ch>, Rob Herring <robh@...nel.org>, Krzysztof
Kozlowski <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>, Greg
Kroah-Hartman <gregkh@...uxfoundation.org>, "Rafael J. Wysocki"
<rafael@...nel.org>, Danilo Krummrich <dakr@...nel.org>, Shawn Guo
<shawnguo@...nel.org>, Sascha Hauer <s.hauer@...gutronix.de>, Pengutronix
Kernel Team <kernel@...gutronix.de>, Fabio Estevam <festevam@...il.com>,
Michael Turquette <mturquette@...libre.com>, Stephen Boyd
<sboyd@...nel.org>, Andi Shyti <andi.shyti@...nel.org>, Wolfram Sang
<wsa+renesas@...g-engineering.com>, Peter Rosin <peda@...ntia.se>, Arnd
Bergmann <arnd@...db.de>, Saravana Kannan <saravanak@...gle.com>, Bjorn
Helgaas <bhelgaas@...gle.com>, Charles Keepax
<ckeepax@...nsource.cirrus.com>, Richard Fitzgerald
<rf@...nsource.cirrus.com>, David Rhodes <david.rhodes@...rus.com>, Linus
Walleij <linus.walleij@...aro.org>, Ulf Hansson <ulf.hansson@...aro.org>,
Mark Brown <broonie@...nel.org>, Andy Shevchenko
<andriy.shevchenko@...ux.intel.com>, Daniel Scally <djrscally@...il.com>,
Heikki Krogerus <heikki.krogerus@...ux.intel.com>, Sakari Ailus
<sakari.ailus@...ux.intel.com>, Len Brown <lenb@...nel.org>, Davidlohr
Bueso <dave@...olabs.net>, Jonathan Cameron <jonathan.cameron@...wei.com>,
Dave Jiang <dave.jiang@...el.com>, Alison Schofield
<alison.schofield@...el.com>, Vishal Verma <vishal.l.verma@...el.com>, Ira
Weiny <ira.weiny@...el.com>, Dan Williams <dan.j.williams@...el.com>, Geert
Uytterhoeven <geert+renesas@...der.be>, Wolfram Sang <wsa@...nel.org>,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
imx@...ts.linux.dev, linux-arm-kernel@...ts.infradead.org,
linux-clk@...r.kernel.org, linux-i2c@...r.kernel.org,
linux-pci@...r.kernel.org, linux-sound@...r.kernel.org,
patches@...nsource.cirrus.com, linux-gpio@...r.kernel.org,
linux-pm@...r.kernel.org, linux-spi@...r.kernel.org,
linux-acpi@...r.kernel.org, linux-cxl@...r.kernel.org, Allan Nielsen
<allan.nielsen@...rochip.com>, Horatiu Vultur
<horatiu.vultur@...rochip.com>, Steen Hegelund
<steen.hegelund@...rochip.com>, Luca Ceresoli <luca.ceresoli@...tlin.com>,
Thomas Petazzoni <thomas.petazzoni@...tlin.com>
Subject: Re: [PATCH v4 05/29] dt-bindings: bus: Add simple-platform-bus
On Fri, 31 Oct 2025 09:52:16 +0100
Geert Uytterhoeven <geert@...ux-m68k.org> wrote:
> Hi Hervé,
>
> On Wed, 15 Oct 2025 at 09:17, Herve Codina <herve.codina@...tlin.com> wrote:
> > A Simple Platform Bus is a transparent bus that doesn't need a specific
> > driver to perform operations at bus level.
> >
> > Similar to simple-bus, a Simple Platform Bus allows to automatically
> > instantiate devices connected to this bus.
> >
> > Those devices are instantiated only by the Simple Platform Bus probe
> > function itself.
> >
> > Signed-off-by: Herve Codina <herve.codina@...tlin.com>
>
> Thanks for your patch!
>
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/bus/simple-platform-bus.yaml
> > @@ -0,0 +1,50 @@
> > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> > +%YAML 1.2
> > +---
> > +$id: http://devicetree.org/schemas/bus/simple-platform-bus.yaml#
> > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > +
> > +title: Simple Platform Bus
> > +
> > +maintainers:
> > + - Herve Codina <herve.codina@...tlin.com>
> > +
> > +description: |
> > + A Simple Platform Bus is a transparent bus that doesn't need a specific
> > + driver to perform operations at bus level.
> > +
> > + Similar to simple-bus, a Simple Platform Bus allows to automatically
> > + instantiate devices connected to this bus. Those devices are instantiated
> > + only by the Simple Platform Bus probe function itself.
>
> So what are the differences with simple-bus? That its children are
> instantiated "only by the Simple Platform Bus probe function itself"?
> If that is the case, in which other places are simple-bus children
> instantiated?
In of_platform_populate(). It call of_platform_bus_create() which is
recursive:
https://elixir.bootlin.com/linux/v6.14/source/drivers/of/platform.c#L374
So children are instantiated out of the bus probe().
>
> Do we need properties related to power-management (clocks, power-domains),
> or will we need a "simple-pm-platform-bus" later? ;-)
>
> FTR, I still think we wouldn't have needed the distinction between
> "simple-bus" and "simple-pm-bus"...
I would like that. Using simple-pm-bus solves my issue but I don't have any
clocks or power-domains to set. The simple-pm-bus bus requires at least
one of them. Even if the driver itself solved my issue, I cannot be
compliant with its binding.
Best regards,
Hervé
Powered by blists - more mailing lists