[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20200929150622.GK3950513@lunn.ch>
Date: Tue, 29 Sep 2020 17:06:22 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Andy Shevchenko <andy.shevchenko@...il.com>
Cc: Calvin Johnson <calvin.johnson@....nxp.com>,
Grant Likely <grant.likely@....com>,
"Rafael J . Wysocki" <rafael@...nel.org>,
Jeremy Linton <jeremy.linton@....com>,
Russell King - ARM Linux admin <linux@...linux.org.uk>,
Jon <jon@...id-run.com>,
Cristi Sovaiala <cristian.sovaiala@....com>,
Ioana Ciornei <ioana.ciornei@....com>,
Florian Fainelli <f.fainelli@...il.com>,
Madalin Bucur <madalin.bucur@....nxp.com>,
netdev <netdev@...r.kernel.org>, "linux.cj" <linux.cj@...il.com>,
ACPI Devel Maling List <linux-acpi@...r.kernel.org>,
nd <nd@....com>
Subject: Re: [net-next PATCH v7 1/6] Documentation: ACPI: DSD: Document MDIO
PHY
> > Does it have a standardized way of
> > saying a device is big endian, swap words around if appropriate when
> > doing IO?
>
> I guess this is not applicable to ACPI. Does Linux have a standardized way?
DT does. You add the property 'little-endian' to indicate you should
do IO to the device using little endian.
> So, what did you mean under doing I/O? I mean in which context?
NXP can synthesise the MDIO controller either big endian, or little
endian. So on some SoCs we need to tell the driver to talk to the
hardware using big endian accesses. On other SoCs we need to tell the
driver to talk to the hardware using little endian.
Is there a standard way in ACPI to describe this?
Andrew
Powered by blists - more mailing lists