From: Herve Codina <herve.codina@bootlin.com>
To: Luca Ceresoli <luca.ceresoli@bootlin.com>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
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>,
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: Tue, 30 Apr 2024 10:51:30 +0200 [thread overview]
Message-ID: <20240430105130.11725e1e@bootlin.com> (raw)
In-Reply-To: <20240426115141.201f257a@booty>
Hi,
On Fri, 26 Apr 2024 11:51:41 +0200
Luca Ceresoli <luca.ceresoli@bootlin.com> wrote:
...
> 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].
>
FYI, I sent upstream the first iteration of the series adding minimal
support the LAN966x PCI device driver.
https://lore.kernel.org/lkml/20240430083730.134918-1-herve.codina@bootlin.com/
This driver binds on the LAN996x PCI VID/PID, and when probed, loads a DT
overlay to instantiates all internal devices re-using all existing drivers
with no change.
Best regards,
Hervé
next prev parent reply other threads:[~2024-04-30 8:51 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 [this message]
2024-05-10 7:31 ` Luca Ceresoli
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=20240430105130.11725e1e@bootlin.com \
--to=herve.codina@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=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.ceresoli@bootlin.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.