[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <23fbbf2dde387e3832b4ca23d46816c0@walle.cc>
Date: Tue, 22 Feb 2022 15:13:46 +0100
From: Michael Walle <michael@...le.cc>
To: Tudor.Ambarus@...rochip.com
Cc: p.yadav@...com, broonie@...nel.org, miquel.raynal@...tlin.com,
richard@....at, vigneshr@...com, linux-mtd@...ts.infradead.org,
linux-kernel@...r.kernel.org, linux-spi@...r.kernel.org,
Nicolas.Ferre@...rochip.com, zhengxunli@...c.com.tw,
jaimeliao@...c.com.tw
Subject: Re: [PATCH 0/4] spi-mem: Allow specifying the byte order in DTR mode
Am 2022-02-22 14:54, schrieb Tudor.Ambarus@...rochip.com:
> On 2/21/22 09:44, Michael Walle wrote:
>> EXTERNAL EMAIL: Do not click links or open attachments unless you know
>> the content is safe
>>
>> Am 2022-02-18 15:58, schrieb Tudor Ambarus:
>>> Fortunately there are controllers
>>> that can swap back the bytes at runtime, fixing the endiannesses.
>>> Provide
>>> a way for the upper layers to specify the byte order in DTR mode.
>>
>> Are there any patches for the atmel-quadspi yet? What happens if
>
> not public, but will publish them these days.
>
>> the controller doesn't support it? Will there be a software fallback?
>
> no need for a fallback, the controller can ignore op->data.dtr_bswap16
> if
> it can't swap bytes.
I don't understand. If the controller doesn't swap the 16bit values,
you will read the wrong content, no?
-michael
Powered by blists - more mailing lists