[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87frdp119x.fsf@bootlin.com>
Date: Mon, 18 Aug 2025 10:28:58 +0200
From: Miquel Raynal <miquel.raynal@...tlin.com>
To: David Lechner <dlechner@...libre.com>
Cc: Sean Anderson <sean.anderson@...ux.dev>, Mark Brown
<broonie@...nel.org>, Michal Simek <michal.simek@....com>,
linux-spi@...r.kernel.org, Jinjie Ruan <ruanjinjie@...wei.com>,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
Amit Kumar Mahapatra <amit.kumar-mahapatra@....com>
Subject: Re: [PATCH v2 1/9] dt-bindings: spi: Add spi-buses property
Hello,
>> + spi-buses:
>> + description:
>> + Array of bus numbers that describes which SPI buses of the controller are
>> + connected to the peripheral. This only applies to peripherals connected
>> + to specialized SPI controllers that have multiple SPI buses on a single
>> + controller.
>> + $ref: /schemas/types.yaml#/definitions/uint32-array
>> + minItems: 1
>
> Finally have some hardware to test this series with using 2 or 4 buses.
Out of curiosity, what is the practical use case and intended benefit?
Maybe an example of such device and an explanation of how useful this is
would be welcome, as it does not seem to fit the initial spi idea
(which has been greatly "improved", not saying it is bad, just unusual).
Thanks,
Miquèl
Powered by blists - more mailing lists