public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Question about DWC3 USB controller driver
Date: Tue, 28 Jul 2015 17:55:40 +0200	[thread overview]
Message-ID: <201507281755.40647.marex@denx.de> (raw)
In-Reply-To: <CAK7LNATygqvaLaQxAhdbUGXtrFjZRRSF4HQy86kSnqRdYTvn8A@mail.gmail.com>

On Tuesday, July 28, 2015 at 05:48:49 PM, Masahiro Yamada wrote:
> Hi Marek,

Hi!

> 2015-07-28 2:03 GMT+09:00 Marek Vasut <marex@denx.de>:
> > On Monday, July 27, 2015 at 05:37:52 PM, Masahiro Yamada wrote:
> >> Hi Marek, other USB guys,
> > 
> > Hi!
> > 
> >> I noticed commit dc9cdf859e11de (usb: dwc3: Add DWC3 controller driver
> >> support) was pulled into the mainline a few days ago.
> >> 
> >> 
> >> Now we have two drivers with similar names.
> >> 
> >> 
> >> - drivers/usb/dwc3/
> >> - drivers/usb/host/xhci-dwc3.c
> >> 
> >> 
> >> Are they the same hardware, or completely different ones?
> > 
> > dwc3 is the USB gadget, drivers/usb/host/xhci-dwc3 is the USB host.
> > I believe the host part should be merged into drivers/usb/xhci-dwc3
> > eventually.
> 
> In my understanding, Synopsys' DWC3 is dual role core.
> 
> 
> In Linux, both host and gadget are supported,
> but drivers/usb/dwc3/host.c is missing from U-Boot.
> 
> I think merging into a single directory drivers/usb/dwc3
> is the right thing.

Correct. Someone would have to backport the host part of drivers/usb/dwc3
from mainline for that purpose though .

Best regards,
Marek Vasut

      reply	other threads:[~2015-07-28 15:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-27 15:37 [U-Boot] Question about DWC3 USB controller driver Masahiro Yamada
2015-07-27 17:03 ` Marek Vasut
2015-07-28 15:48   ` Masahiro Yamada
2015-07-28 15:55     ` Marek Vasut [this message]

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=201507281755.40647.marex@denx.de \
    --to=marex@denx.de \
    --cc=u-boot@lists.denx.de \
    /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