From: Christian Lamparter <chunkeey@googlemail.com>
To: benh@au1.ibm.com
Cc: linux-usb@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org, a.seppala@gmail.com,
johnyoun@synopsys.com, gregkh@linuxfoundation.org
Subject: Re: usb: dwc2: regression on MyBook Live Duo / Canyonlands since 4.3.0-rc4
Date: Sun, 08 May 2016 13:44:18 +0200 [thread overview]
Message-ID: <1908894.Nkk1LXQkFm@debian64> (raw)
In-Reply-To: <1462704055.20290.93.camel@au1.ibm.com>
On Sunday, May 08, 2016 08:40:55 PM Benjamin Herrenschmidt wrote:
> On Sun, 2016-05-08 at 00:54 +0200, Christian Lamparter via Linuxppc-d=
ev=20
> wrote:
> > I've been looking in getting the MyBook Live Duo's USB OTG port
> > to function. The SoC is a APM82181. Which has a PowerPC 464 core
> > and related to the supported canyonlands architecture in
> > arch/powerpc/.
> >=20
> > Currently in -next the dwc2 module doesn't load:=20
>=20
> Smells like the APM implementation is little endian. You might need t=
o
> use a flag to indicate what endian to use instead and set it
> appropriately based on some DT properties.
I tried. As per common-properties[0], I added little-endian; but it has=
no
effect. I looked in dwc2_driver_probe and found no way of specifying th=
e
endian of the device. It all comes down to the dwc2_readl & dwc2_writel=
accessors. These - sadly - have been hardwired to use __raw_readl and
__raw_writel. So, it's always "native-endian". While common-properties
says little-endian should be preferred.
> > dwc2 4bff80000.usbotg: dwc2_core_reset() HANG! AHB Idle GRSTCTL=3D8=
0
> > dwc2 4bff80000.usbotg: Bad value for GSNPSID: 0x0a29544f
> >=20
> > Looking at the Bad GSNPSID value: 0x0a29544f. It is obvious that
> > this is an endian problem. git finds this patch:
> >=20
> > commit 95c8bc3609440af5e4a4f760b8680caea7424396
> > Author: Antti Sepp=E4l=E4 <a.seppala@gmail.com>
> > Date: Thu Aug 20 21:41:07 2015 +0300
> >=20
> > usb: dwc2: Use platform endianness when accessing registers
> >=20
> > This patch is necessary to access dwc2 registers correctly on
> > big-endian
> > systems such as the mips based SoCs made by Lantiq. Then dwc2 c=
an
> > be
> > used to replace ifx-hcd driver for Lantiq platforms found e.g. =
in
> > OpenWrt.
> > =20
> > The patch was autogenerated with the following commands:
> > $EDITOR core.h
> > sed -i "s/\<readl\>/dwc2_readl/g" *.c hcd.h hw.h
> > sed -i "s/\<writel\>/dwc2_writel/g" *.c hcd.h hw.h
> > =20
> > Some files were then hand-edited to fix checkpatch.pl warnings
> > about
> > too long lines.
> >=20
> > which unfortunately, broke the USB-OTG port on the MyBook Live Duo.=
> > Reverting to the readl / writel:
> >=20
> > ---=20
> > diff --git a/drivers/usb/dwc2/core.h b/drivers/usb/dwc2/core.h
> > index 3c58d63..c021c1f 100644
> > --- a/drivers/usb/dwc2/core.h
> > +++ b/drivers/usb/dwc2/core.h
> > @@ -66,7 +66,7 @@
> > =20
> > static inline u32 dwc2_readl(const void __iomem *addr)
> > {
> > -=09u32 value =3D __raw_readl(addr);
> > +=09u32 value =3D readl(addr);
> > =20
> > =09/* In order to preserve endianness __raw_* operation is
> > used. Therefore
> > =09 * a barrier is needed to ensure IO access is not re-ordered=20=
> > across
> > @@ -78,7 +78,7 @@ static inline u32 dwc2_readl(const void __iomem
> > *addr)
> > =20
> > static inline void dwc2_writel(u32 value, void __iomem *addr)
> > {
> > -=09__raw_writel(value, addr);
> > +=09writel(value, addr);
> > =20
> > =09/*
> > =09 * In order to preserve endianness __raw_* operation is
> > used. Therefore
> >=20
> > ---
> >=20
> > restores the dwc-otg port to full working order:
> > dwc2 4bff80000.usbotg: Specified GNPTXFDEP=3D1024 > 256
> > dwc2 4bff80000.usbotg: EPs: 3, shared fifos, 2042 entries in SPRAM
> > dwc2 4bff80000.usbotg: DWC OTG Controller
> > dwc2 4bff80000.usbotg: new USB bus registered, assigned bus number =
1
> > dwc2 4bff80000.usbotg: irq 33, io mem 0x00000000
> > hub 1-0:1.0: USB hub found
> > hub 1-0:1.0: 1 port detected
> > root@mbl:~# usb 1-1: new high-speed USB device number 2 using dwc2
> >=20
> > So, what to do?
^^^
Regards,
Christian
[0] <http://lxr.free-electrons.com/source/Documentation/devicetree/bind=
ings/common-properties.txt>
next prev parent reply other threads:[~2016-05-08 11:44 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-07 22:54 usb: dwc2: regression on MyBook Live Duo / Canyonlands since 4.3.0-rc4 Christian Lamparter
2016-05-08 10:40 ` Benjamin Herrenschmidt
2016-05-08 11:44 ` Christian Lamparter [this message]
2016-05-09 0:23 ` Benjamin Herrenschmidt
2016-05-09 10:36 ` Arnd Bergmann
2016-05-09 10:39 ` Felipe Balbi
2016-05-09 15:08 ` Arnd Bergmann
2016-05-09 19:06 ` Christian Lamparter
2016-05-09 20:10 ` Arnd Bergmann
2016-05-09 22:43 ` Benjamin Herrenschmidt
2016-05-09 22:37 ` Benjamin Herrenschmidt
2016-05-10 7:23 ` Arnd Bergmann
2016-05-12 9:58 ` Christian Lamparter
2016-05-12 11:55 ` Arnd Bergmann
2016-05-12 13:30 ` Christian Lamparter
2016-05-12 18:40 ` John Youn
2016-05-12 20:39 ` Christian Lamparter
2016-05-12 20:50 ` Arnd Bergmann
2016-05-12 20:55 ` John Youn
2016-05-14 13:11 ` Christian Lamparter
2016-05-14 19:45 ` Arnd Bergmann
2016-05-17 23:50 ` John Youn
2016-05-18 19:14 ` Christian Lamparter
2016-05-18 21:09 ` Arnd Bergmann
2016-05-19 0:36 ` John Youn
2016-05-12 22:17 ` Benjamin Herrenschmidt
2016-05-09 22:33 ` Benjamin Herrenschmidt
2016-05-09 14:02 ` Benjamin Herrenschmidt
2016-05-09 20:22 ` John Youn
2016-05-09 20:38 ` Arnd Bergmann
2016-05-09 21:11 ` John Youn
2016-05-09 21:30 ` Arnd Bergmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1908894.Nkk1LXQkFm@debian64 \
--to=chunkeey@googlemail.com \
--cc=a.seppala@gmail.com \
--cc=benh@au1.ibm.com \
--cc=gregkh@linuxfoundation.org \
--cc=johnyoun@synopsys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).