[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YvO5UKACe2FMa5K4@sirena.org.uk>
Date: Wed, 10 Aug 2022 14:57:36 +0100
From: Mark Brown <broonie@...nel.org>
To: Patrice CHOTARD <patrice.chotard@...s.st.com>
Cc: Alexandre Torgue <alexandre.torgue@...s.st.com>,
linux-spi@...r.kernel.org,
linux-stm32@...md-mailman.stormreply.com,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
christophe.kerello@...s.st.com
Subject: Re: [PATCH v2 1/2] spi: stm32_qspi: Add transfer_one_message() spi
callback
On Wed, Aug 10, 2022 at 03:52:39PM +0200, Patrice CHOTARD wrote:
> On 8/10/22 15:40, Mark Brown wrote:
> > Can't the controller figure this out by looking at the properties of the
> > connected devices? You'd need to just return an error if we ever
> > triggered transfer_one_message() on a device that can't support the
> > operation.
> It should be a solution.
> I just noticed another point, property parallel-memories is an array of uint64 which represent device's size.
> In case a FPGA is connected to the qspi 8 line bus, parallel-memories property will be set with what ?
> simply random value to make dtbs_check happy ?
> IMHO, adding a new proprietary property would be cleaner.
I tend to agree that this is all rather unclear for things that aren't
actually storage.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists