From: Luca Ceresoli <luca.ceresoli@bootlin.com>
To: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Cc: "Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>,
"Bartosz Golaszewski" <brgl@bgdev.pl>,
"Doug Anderson" <dianders@chromium.org>,
"Chen-Yu Tsai" <wenst@chromium.org>,
"Matt Coster" <Matt.Coster@imgtec.com>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
"Alexandre Belloni" <alexandre.belloni@bootlin.com>,
"Maxime Chevallier" <maxime.chevallier@bootlin.com>,
"Hervé Codina" <herve.codina@bootlin.com>,
"Rob Herring" <robh@kernel.org>,
"Conor Dooley" <conor@kernel.org>,
"Saravana Kannan" <saravanak@google.com>,
linux-kernel@vger.kernel.org
Subject: Re: Hotplug hardware with (un)loadable DT overlays - unconference meeting notes
Date: Fri, 10 May 2024 09:31:56 +0200 [thread overview]
Message-ID: <20240510093156.13bfcd34@booty> (raw)
In-Reply-To: <20240426115141.201f257a@booty>
Hello,
On Fri, 26 Apr 2024 11:51:41 +0200
Luca Ceresoli <luca.ceresoli@bootlin.com> wrote:
[...]
> We described 2 use cases we are working on at Bootlin.
>
> One use case is for the LAN966x, a classic SoC that can be however be
> started in "endpoint mode", i.e. with the CPU cores deactivated and a
> PCI endpoint that allows an external CPU to access all the peripherals
> over PCIe. In practice the whole SoC would be used as a peripheral chip
> providing lots of devices for another SoC where the OS runs. This use
> case has been described by Rob Herring and Lizhi Hou at LPC 2023 [4][5].
>
> The other use case, which was discussed in more detail, is for an
> industrial product under development by a Bootlin customer, which is a
> regular, self-standing embedded Linux system with a connector allowing
> to connect an add-on with additional peripherals. The add-on
> peripherals are on I2C, MIPI DSI and potentially other non-discoverable
> busses (there are also peripherals on natively hot-pluggable busses
> such as USB and Ethernet, but by their nature they don't need special
> work).
>
> For both use cases (and perhaps others we are unaware of) runtime
> loading/unloading DT overlays appears as the most fitting technique.
> Except it is not yet ready for real usage.
>
> For it to work, we highlighted 3 main areas in need of work in the
> Linux kernel:
>
> 1. how to describe the connector and the add-ons in device tree
> (bindings etc) -- only relevant for the 2nd use case
> 2. implementation of DT overlays for adding/removing the add-on
> peripherals
> 3. fixing issues with various subsystems and drivers that don't react
> well on device removal
Quick update: I just sent a series with a proposal covering items 1 and
2:
https://lore.kernel.org/all/20240510-hotplug-drm-bridge-v2-0-ec32f2c66d56@bootlin.com/
Luca
--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2024-05-10 7:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-26 9:51 Hotplug hardware with (un)loadable DT overlays - unconference meeting notes Luca Ceresoli
2024-04-30 8:51 ` Herve Codina
2024-05-10 7:31 ` Luca Ceresoli [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=20240510093156.13bfcd34@booty \
--to=luca.ceresoli@bootlin.com \
--cc=Matt.Coster@imgtec.com \
--cc=alexandre.belloni@bootlin.com \
--cc=brgl@bgdev.pl \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=herve.codina@bootlin.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.chevallier@bootlin.com \
--cc=robh@kernel.org \
--cc=saravanak@google.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=wenst@chromium.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;
as well as URLs for NNTP newsgroup(s).