[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+h21hodaPyY54fwRFNhmksg+9ugVvW7hndMCCc=cBG39D7jdQ@mail.gmail.com>
Date: Mon, 9 Mar 2020 20:31:22 +0200
From: Vladimir Oltean <olteanv@...il.com>
To: Michael Walle <michael@...le.cc>
Cc: Mark Brown <broonie@...nel.org>, linux-spi@...r.kernel.org,
lkml <linux-kernel@...r.kernel.org>,
Shawn Guo <shawnguo@...nel.org>,
Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
devicetree@...r.kernel.org, Esben Haabendal <eha@...f.com>,
angelo@...am.it, andrew.smirnov@...il.com,
"Gustavo A. R. Silva" <gustavo@...eddedor.com>,
Wei Chen <weic@...dia.com>, Mohamed Hosny <mhosny@...dia.com>,
peng.ma@....com
Subject: Re: [PATCH 2/6] spi: spi-fsl-dspi: Fix little endian access to PUSHR
CMD and TXDATA
On Mon, 9 Mar 2020 at 20:19, Michael Walle <michael@...le.cc> wrote:
>
> Eg. is it big-endian or little-endian if there is no property at all?
>
I think it is "native endianness" in that case, i.e. big endian on big
endian CPU and little endian on little endian CPU.
Thanks,
-Vladimir
Powered by blists - more mailing lists