[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <176780144202.1197510.11558178510570306104.robh@kernel.org>
Date: Wed, 7 Jan 2026 09:57:22 -0600
From: "Rob Herring (Arm)" <robh@...nel.org>
To: David Lechner <dlechner@...libre.com>
Cc: linux-kernel@...r.kernel.org, Mark Brown <broonie@...nel.org>,
linux-spi@...r.kernel.org,
Nuno Sá <nuno.sa@...log.com>,
Andy Shevchenko <andy@...nel.org>, linux-iio@...r.kernel.org,
Marcelo Schmitt <marcelo.schmitt@...log.com>,
Conor Dooley <conor+dt@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Jonathan Cameron <jic23@...nel.org>, devicetree@...r.kernel.org,
Sean Anderson <sean.anderson@...ux.dev>,
Michael Hennerich <michael.hennerich@...log.com>
Subject: Re: [PATCH v4 2/9] spi: dt-bindings: add spi-{tx,rx}-lane-map
properties
On Fri, 19 Dec 2025 15:32:10 -0600, David Lechner wrote:
> Add spi-tx-lane-map and spi-rx-lane-map properties to the SPI peripheral
> device tree binding. These properties allow specifying the mapping of
> peripheral data lanes to controller data lanes. This is needed e.g. when
> some lanes are skipped on the controller side so that the controller
> can correctly route data to/from the peripheral.
>
> Signed-off-by: David Lechner <dlechner@...libre.com>
> ---
>
> v4 changes:
> - This replaces the data-lanes property from the previous revision. Now
> there are separate properties for tx and rx lane maps. And instead of
> being the primary property for determining the number of lanes, this
> is only needed in special cases where the mapping is non-trivial.
> ---
> .../devicetree/bindings/spi/spi-peripheral-props.yaml | 14 ++++++++++++++
> 1 file changed, 14 insertions(+)
>
Reviewed-by: Rob Herring (Arm) <robh@...nel.org>
Powered by blists - more mailing lists