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] [PATCH 0/7] USB: XHCI: Add xHCI host controller stack driver
Date: Mon, 8 Jul 2013 15:01:56 +0200	[thread overview]
Message-ID: <201307081501.56535.marex@denx.de> (raw)
In-Reply-To: <CAFp+6iFFzDQCfVed0jBojSgzUPhWfQW_hZq2ppexgJQxjVhyvg@mail.gmail.com>

Hi Vivek,

[...]

> Very well said. I can see Dan's stack is nicely sync'ed with Linux
> (with ifdef's ;-) which i am sure are going to vanish down the line)
> I had a initial look at Dan's patches, which have backported DWC3 and
> XHCI, but i am sure we are going to
> need some amount of code to be put in usb core framework (common/usb*.c),
> if we are going to enable complete xHCI (super speed) support.

Absolutely, you have that part though ;-)

> For DWC3, i leave it to you, as to how much code we want to pull in.
> Ofcourse my driver for exynos did some basic DWC3 initialization,
> making it hard for other vendors who are using DWC3 to resuse the code.

Exynos also uses dwc3 ?

> > What I'd like to see is Vivek's version merged into Dan's version, that
> > should be easy (by the looks of it) and then this combined version
> > merged mainline. This should hopefully retain the easy possibility to
> > update the USB3 code from Linux. It should also cut down the time it
> > will take to get Dan's code into working state (since that's done in
> > Vivek's tree already).
> 
> We can go ahead merging the two versions. But i do have few doubts
> with how Dan is
> structuring things.
> Better i comment on his patches and clear my doubts.

Thanks.

> Dear Dan,
> 
> Please suggest on how you are planning going ahead and merging the two
> versions of xHCI stack.
> 
> > Now you can flame me to death.

Best regards,
Marek Vasut

  reply	other threads:[~2013-07-08 13:01 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-02 12:59 [U-Boot] [PATCH 0/7] USB: XHCI: Add xHCI host controller stack driver Vivek Gautam
2013-07-02 12:59 ` [U-Boot] [PATCH 1/7] arm: exynos5250: Define CONFIG_SYS_CACHELINE_SIZE Vivek Gautam
2013-07-02 12:59 ` [U-Boot] [PATCH 2/7] USB: xHCI: Add stack support for xHCI Vivek Gautam
2013-07-02 12:59 ` [U-Boot] [PATCH 3/7] USB: XHCI: Add xHCI host controller support for Exynos5 Vivek Gautam
2013-07-02 12:59 ` [U-Boot] [PATCH 4/7] arm: exynos: Add methods to control power to USB 3.0 PHY Vivek Gautam
2013-07-02 12:59 ` [U-Boot] [PATCH 5/7] exynos5: dts: Add COMPAT string data for USB 3.0 PHY and XHCI Vivek Gautam
2013-07-02 12:59 ` [U-Boot] [PATCH 6/7] exynos5: dts: Add device node for XHCI Vivek Gautam
2013-07-02 12:59 ` [U-Boot] [PATCH 7/7] temp: ARM: EXYNOS5: Enable xHCI support for Exynos5 Vivek Gautam
2013-07-02 15:23 ` [U-Boot] [PATCH 0/7] USB: XHCI: Add xHCI host controller stack driver Dan Murphy
2013-07-02 21:27   ` Marek Vasut
2013-07-03 11:15     ` Vivek Gautam
2013-07-08 13:01       ` Marek Vasut [this message]
2013-07-10 16:57       ` Dan Murphy
2013-07-18 20:53         ` Julius Werner
2013-07-19 16:57           ` Dan Murphy
2013-07-31 13:01 ` Dan Murphy
2013-07-31 13:55   ` Vivek Gautam
2013-07-31 14:18     ` Dan Murphy

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=201307081501.56535.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