[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <59651605-45fa-49d7-bb15-dae83d8ad471@jm0.eu>
Date: Tue, 18 Mar 2025 20:55:11 +0100
From: "Ing. Josua Mayer" <josua.mayer@....eu>
To: Jayesh Choudhary <j-choudhary@...com>, vigneshr@...com,
andi.shyti@...nel.org, robh@...nel.org, krzk+dt@...nel.org,
conor+dt@...nel.org, linux-kernel@...r.kernel.org
Cc: aaro.koskinen@....fi, andreas@...nade.info, khilman@...libre.com,
rogerq@...nel.org, tony@...mide.com, jmkrzyszt@...il.com,
linux-omap@...r.kernel.org, linux-i2c@...r.kernel.org,
devicetree@...r.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: i2c: omap: Add mux-states property
Hi Jayesh,
Am 18.03.25 um 11:36 schrieb Jayesh Choudhary:
> Add mux controller support for when the I2C lines are muxed after
> signals come out of SoC and before they go to any client.
>
> Signed-off-by: Jayesh Choudhary <j-choudhary@...com>
> ---
> Documentation/devicetree/bindings/i2c/ti,omap4-i2c.yaml | 6 ++++++
> 1 file changed, 6 insertions(+)
Is there any chance for this to be generic across any i2c controller
regardless of SoC in use?
Is this perhaps also generic to any device in dts,
similar to assigned-clocks?
E.g. in k3-am642-hummingboard-t-{pcie,usb3}.dts we have a mux on the
carrier board switching a serdes lane between two different connectors.
It would make sense for pcie and usb phy nodes to delay probe in a
similar fashion.
The same may hold true for other buses muxed at boot-time or based on
assembly options or extension cards.
sincerely
Josua Mayer
Powered by blists - more mailing lists