All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Matthijs van Duin <matthijsvanduin@gmail.com>
Cc: Bin Liu <binmlist@gmail.com>, Felipe Balbi <balbi@ti.com>,
	Kishon Vijay Abraham I <kishon@ti.com>,
	linux-kernel@vger.kernel.org,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	linux-usb <linux-usb@vger.kernel.org>,
	Brian Hutchinson <b.hutchman@gmail.com>
Subject: Re: [PATCH] phy: Add a driver for dm816x USB PHY
Date: Mon, 16 Mar 2015 09:49:51 -0700	[thread overview]
Message-ID: <20150316164951.GR5264@atomide.com> (raw)
In-Reply-To: <CAALWOA_FM71OsvCfPuz4DHwGDEpfxcSB4L+YdoCsJuZkukK2iw@mail.gmail.com>

* Matthijs van Duin <matthijsvanduin@gmail.com> [150314 14:04]:
> On 13 March 2015 at 20:30, Tony Lindgren <tony@atomide.com> wrote:
> > 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.
> 
> Hmm? While I see plenty of usb errata (mostly DMA bugs), I don't see
> anything about registers being different.

Sorry it seems to be the partially updated TRM instead, it's the
sprs614e.pdf instead. That has the USBPHY_CTRL registers right.
No mention of Synopsys in sprs614e.pdf though so who knows. It
seems something got swapped compared to the TRM as the USB_CTRL
registers totally changed.

I'll just add a comments you mentioned earlier about it probably
being Synopsys phy.
 
> I do see something curious: advisory 70, the only PHY-related erratum
> I see, is also present in the DM814x errata and even in AM335x r1.0.
> This strongly suggests the PHYs must at least be closely related...

Hmm interesting. But dm814x has again different USB_CTRL registers,
seems to be wired up like am335x. Also there's no USBPHY_CTRL
registers on dm814x or am335x. Chances are that dm814x is wired up
the same way as am335x.

> The dm816x TRM makes three separate mentions of the synopsys usb phy
> though, while I found no other TRMs that mention it, so if it's a
> copy-paste error (which certainly would not be exceptional) I don't
> know where from.

Yes I checked am3517 trm, and that too mentions Synopsys once, but
has different registers. And also checked the l-138/da850 TRM, and
that does not have USB_CTRL and USBPHY_CTRL registers either.. Looks
like the copy paste errors come from tms320dm6446.pdf that has
the USB_CTRL and USBPHY_CTRL registers, but then no mention of
Synopsys.

> I suppose it's still possible TI acquired a sufficiently permissive
> license for the synopsys phy to fork it and call it a "TI PHY" as they
> do in the AM335x docs. (No mention of its origin is made in the DM814x
> docs.)
> 
> BTW, da850? Is that yet another instance of Primus? (i.e.
> omap-L1xx/c674x/am1xxx with odd final digit, also da830/da828)

Yes it's the arm926 based series, l-138 is da850 I believe.

Regards,

Tony

  reply	other threads:[~2015-03-16 16:49 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-09 20:51 [PATCH] phy: Add a driver for dm816x USB PHY Tony Lindgren
     [not found] ` <20150309205157.GE5140-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2015-03-09 21:11   ` Bin Liu
2015-03-09 21:11     ` Bin Liu
2015-03-09 21:13     ` Felipe Balbi
2015-03-09 21:13       ` Felipe Balbi
2015-03-09 21:17       ` Bin Liu
2015-03-09 21:20         ` Felipe Balbi
2015-03-09 21:20           ` Felipe Balbi
2015-03-09 21:26           ` Tony Lindgren
2015-03-09 21:35             ` Bin Liu
     [not found]               ` <CADYTM3ZW5e5dCQbbaE02o7wxOC26+jo5Ddo+2B4Q6UCAT2pTdQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-03-09 21:41                 ` Tony Lindgren
2015-03-09 21:41                   ` Tony Lindgren
2015-03-10 14:35                   ` Bin Liu
     [not found]                   ` <20150309214129.GK5264-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2015-03-13 18:38                     ` Matthijs van Duin
2015-03-13 18:38                       ` Matthijs van Duin
2015-03-13 19:30                       ` Tony Lindgren
     [not found]                         ` <20150313193058.GN5264-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2015-03-14 21:04                           ` Matthijs van Duin
2015-03-14 21:04                             ` Matthijs van Duin
2015-03-16 16:49                             ` Tony Lindgren [this message]
2015-03-16 21:16                               ` Matthijs van Duin
2015-03-17  2:19                                 ` Tony Lindgren
2015-03-19 11:19                                   ` Matthijs van Duin
2015-03-19 15:57                                     ` Tony Lindgren
2015-03-09 21:20         ` Tony Lindgren
2015-03-09 21:31           ` Bin Liu
2015-03-11  9:58 ` Kishon Vijay Abraham I
2015-03-11  9:58   ` Kishon Vijay Abraham I
2015-03-11 15:19   ` Tony Lindgren
2015-03-11 11:16 ` Paul Bolle
2015-03-11 15:20   ` Tony Lindgren
2015-03-12  0:56     ` Rusty Russell
2015-03-12 20:42       ` Tony Lindgren

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=20150316164951.GR5264@atomide.com \
    --to=tony@atomide.com \
    --cc=b.hutchman@gmail.com \
    --cc=balbi@ti.com \
    --cc=binmlist@gmail.com \
    --cc=kishon@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=matthijsvanduin@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.