From: Bin Liu <binmlist@gmail.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Felipe Balbi <balbi@ti.com>,
Kishon Vijay Abraham I <kishon@ti.com>,
linux-kernel@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, 9 Mar 2015 16:35:28 -0500 [thread overview]
Message-ID: <CADYTM3ZW5e5dCQbbaE02o7wxOC26+jo5Ddo+2B4Q6UCAT2pTdQ@mail.gmail.com> (raw)
In-Reply-To: <20150309212622.GJ5264@atomide.com>
On Mon, Mar 9, 2015 at 4:26 PM, Tony Lindgren <tony@atomide.com> wrote:
> * Felipe Balbi <balbi@ti.com> [150309 14:21]:
>> On Mon, Mar 09, 2015 at 04:17:29PM -0500, Bin Liu wrote:
>> > On Mon, Mar 9, 2015 at 4:13 PM, Felipe Balbi <balbi@ti.com> wrote:
>> > > On Mon, Mar 09, 2015 at 04:11:28PM -0500, Bin Liu wrote:
>> > >> Hi,
>> > >>
>> > >> On Mon, Mar 9, 2015 at 3:51 PM, Tony Lindgren <tony@atomide.com> wrote:
>> > >> > Add a minimal driver for dm816x USB. Otherwise we can just use
>> > >> > the existing musb_am335x and musb_dsps on dm816x.
>> > >>
>> > >> dm816x has the almost identical usbss as that in am335x, we should be
>> > >> able to adopt musb_am335x and musb_dsps for dm816x, and dm814x too?
>> > >
>> > > Tony's using the same musb glue layers, this is just a phy driver,
>> > > right ?
>> >
>> > Can the current am335x phy driver be adopted too? I remember it is
>> > under drivers/usb/phy/.
>>
>> Tony will be best to answer, but according to our IRC discussions, it's
>> too different. Tony ?
>
> Well we should check again between dm814x and am335x documentation
> against the $subject driver as the dm816x docs were buggy and I may
> have gotten a wrong idea initially.
Will it make our life a little easier by comparing the usb drivers for
dm81xx and am335x in previous TI kernel releases? I cam dig out the
source code if that helps.
Regards,
-Bin,
>
> Regards,
>
> Tony
next prev parent reply other threads:[~2015-03-09 21:35 UTC|newest]
Thread overview: 25+ 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
2015-03-09 21:11 ` Bin Liu
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:26 ` Tony Lindgren
2015-03-09 21:35 ` Bin Liu [this message]
2015-03-09 21:41 ` Tony Lindgren
2015-03-10 14:35 ` Bin Liu
2015-03-13 18:38 ` Matthijs van Duin
2015-03-13 19:30 ` Tony Lindgren
2015-03-14 21:04 ` Matthijs van Duin
2015-03-16 16:49 ` Tony Lindgren
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 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=CADYTM3ZW5e5dCQbbaE02o7wxOC26+jo5Ddo+2B4Q6UCAT2pTdQ@mail.gmail.com \
--to=binmlist@gmail.com \
--cc=b.hutchman@gmail.com \
--cc=balbi@ti.com \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=tony@atomide.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 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).