[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20251021142129.GA34073-robh@kernel.org>
Date: Tue, 21 Oct 2025 09:21:29 -0500
From: Rob Herring <robh@...nel.org>
To: David Lechner <dlechner@...libre.com>
Cc: Mark Brown <broonie@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>,
Marcelo Schmitt <marcelo.schmitt@...log.com>,
Michael Hennerich <michael.hennerich@...log.com>,
Nuno Sá <nuno.sa@...log.com>,
Jonathan Cameron <jic23@...nel.org>,
Andy Shevchenko <andy@...nel.org>,
Sean Anderson <sean.anderson@...ux.dev>, linux-spi@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-iio@...r.kernel.org
Subject: Re: [PATCH 1/6] dt-bindings: spi: Add spi-buses property
On Tue, Oct 14, 2025 at 05:02:11PM -0500, David Lechner wrote:
> Add a spi-buses property to the spi-peripheral-props binding to allow
> specifying the SPI data bus or buses that a peripheral is connected to
> in cases where the SPI controller has more than one physical SPI data
> bus.
Is there a reason why spi-rx-bus-width property doesn't work for you?
The only thing I see would be you need to define the order of the pins
like "data-lanes" property.
Rob
Powered by blists - more mailing lists