Re: [PATCH] phy: Add a driver for dm816x USB PHY

From: Tony Lindgren
Date: Fri Mar 13 2015 - 15:36:04 EST

* Matthijs van Duin <matthijsvanduin@xxxxxxxxx> [150313 11:39]:
> Given that the documentation mentions the actual phy used, it may be
> worth mentioning this also in the driver? i.e. that it's not a
> "dm816x phy" but a "SR70LX Synopsys USB 2.0 OTG nanoPHY" (in contrast
> to the dm814x and am335x which use a phy TI made themselves)

Hmm OK have to check that. It could also be that dm816x documentation
is copy-paste from da850 or am3517 and the PHY got changed in the
hardware as the registers don't match the documentation. Only the
dm816x errata has right documentation for the USB PHY.

> USB is one of the few subsystems of the DM814x I've never really
> examined in any detail, but it appears nearly identical to the AM335x.
> (e.g. the phy registers in the control module are nearly identical,
> differing only in some bits related to GPIO-mode)

OK thanks for confirming that. It's different from this one then.

> On 9 March 2015 at 22:41, Tony Lindgren <tony@xxxxxxxxxxx> wrote:
> > Note that we still are missing basic support for dm814x in mainline,
> > I'm planning to tackle that at some point but I don't know when I'm
> > going to get to it..
> Do ping me if you have questions. While I still don't have time to
> really throw myself on the task myself, and I'm still hindered by
> insufficient knowledge of the kernel, I do have quite a bit of
> experience with the processor itself.
> BTW, w.r.t. the old "official" TI kernel for dm81xx: there are
> actually two relevant forks of the unmaintained
> arago-omap3/ti81xx-master branch, namely:
> which contain various bugfixes, including for usb (though also patches
> specific to those SDKs).

Yeah it will be several days of work anyways, not currently my
priority for sure. Would be nice to get it done though.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at