Received-SPF: pass (google.com: domain of linux-kernel+bounces-175400-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) client-ip=139.178.88.99;
Date: Fri, 10 May 2024 09:31:56 +0200
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>, =?UTF-8?Q?Herv=C3=A9?= 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
Message-ID: <20240510093156.13bfcd34@booty>
In-Reply-To: <20240426115141.201f257a@booty>
References: <20240426115141.201f257a@booty>
Organization: Bootlin
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

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