Re: [PATCH v3 7/7] dt-bindings: iio: adc: adi,ad4030: add data-lanes property
From: David Lechner
Date: Fri Dec 05 2025 - 16:33:52 EST
On 12/5/25 3:12 PM, Marcelo Schmitt wrote:
> On 12/04, Rob Herring wrote:
>> On Mon, Dec 01, 2025 at 08:20:45PM -0600, David Lechner wrote:
>>> Add data-lanes property to specify the number of data lanes used on the
>>> ad463x chips that support reading two samples at the same time using
>>> two data lanes with a capable SPI controller.
>>>
>>> Signed-off-by: David Lechner <dlechner@xxxxxxxxxxxx>
>>> ---
>>> v3 changes: new patch
>>>
>>> I added this one to give a real-world use case where spi-rx-bus-width
>>> was not sufficient to fully describe the hardware configuration.
>>>
>>> spi-rx-bus-width = <4>; alone could be be interpreted as either:
>>>
>>> +--------------+ +----------+
>>> | SPI | | AD4630 |
>>> | Controller | | ADC |
>>> | | | |
>>> | SDIA0 |<---| SDOA0 |
>>> | SDIA1 |<---| SDOA1 |
>>> | SDIA2 |<---| SDOA2 |
>>> | SDIA3 |<---| SDOA3 |
>>> | | | |
>>> | SDIB0 |x | SDOB0 |
>>> | SDIB1 |x | SDOB1 |
>>> | SDIB2 |x | SDOB2 |
>>> | SDIB3 |x | SDOB3 |
>>> | | | |
>>> +--------------+ +---------+
>>>
>>> or
>>>
>>> +--------------+ +----------+
>>> | SPI | | AD4630 |
>>> | Controller | | ADC |
>>> | | | |
>>> | SDIA0 |<---| SDOA0 |
>>> | SDIA1 |<---| SDOA1 |
>>> | SDIA2 |x | SDOA2 |
>>> | SDIA3 |x | SDOA3 |
>>> | | | |
>>> | SDIB0 |<---| SDOB0 |
>>> | SDIB1 |<---| SDOB1 |
>>> | SDIB2 |x | SDOB2 |
>>> | SDIB3 |x | SDOB3 |
>>> | | | |
>>> +--------------+ +---------+
>>>
>>> Now, with data-lanes having a default value of [0] (inherited from
>>> spi-peripheral-props.yaml), specifying:
>>>
>>> spi-rx-bus-width = <4>;
>>>
>>> is unambiguously the first case and the example given in the binding
>>> documentation is the second case:
>>>
>>> spi-rx-bus-width = <2>;
>>> data-lanes = <0>, <1>;
>>
>> I just reviewed this and all, but what if you just did:
>>
>> spi-rx-bus-width = <2>, <2>;
>>
>> So *-bus-width becomes equal to the number of serializers/channels.
>
> Unless I'm missing something, I think that would also describe the currently
> possible use cases as well. To me, it actually seems even more accurate than
> data-lanes. The data-lanes property only describes the SPI controller input
> lines/lanes, no info is given about the output lanes.
It describes both directions.
> Well yeah, that would only> be a problem for a device with multiple input serializers and multiple output
> serializers. Still, the *-bus-width = <N>, <N>, ... <N>; notation looks clearer,
> IMHO.
>
>>
>> Rob
>>
It think it complicates Sean's use case though where such
a controller is being used as basically two separate SPI
buses.
For that case, we want to be able to do:
spi {
...
thing@0 {
compatible = ...;
reg = <0>;
/* (implicit) data-lanes = <0>; */
};
thing@1 {
compatible = ...;
reg = <1>;
data-lanes = <1>;
};
};
Meaning:
+--------------+ +----------+
| SPI | | Thing 1 |
| Controller | | |
| | | |
| CS0 |--->| CS |
| SDI0 |<---| SDO |
| SDO0 |--->| SDI |
| SCLK0 |--->| SCLK |
| | | |
| | +----------+
| |
| | +----------+
| | | Thing 2 |
| | | |
| CS1 |--->| CS |
| SDI1 |<---| SDO |
| SDO1 |--->| SDI |
| SCLK1 |--->| SCLK |
| | | |
+--------------+ +----------+
(I don't remember if SCLKs are shared or separate, but I don't
think that is relevant anyway).
I guess we could write it like this?
spi {
...
thing@0 {
compatible = ...;
reg = <0>;
};
thing@1 {
compatible = ...;
reg = <1>;
spi-tx-bus-width = <0>, <1>;
spi-rx-bus-width = <0>, <1>;
};
};