From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC PATCH 0/7] RFC: dm: Add USB support
Date: Mon, 9 Feb 2015 22:02:08 +0100 [thread overview]
Message-ID: <201502092202.08511.marex@denx.de> (raw)
In-Reply-To: <CAPnjgZ2gtNO+UuoBDrMiNCvAenf43_0X=QB4N4mr_uGVScz86w@mail.gmail.com>
On Friday, January 30, 2015 at 11:41:33 PM, Simon Glass wrote:
> Hi Marek,
Hi!
> On 30 January 2015 at 15:16, Marek Vasut <marex@denx.de> wrote:
> > On Friday, January 30, 2015 at 08:04:50 PM, Simon Glass wrote:
> > > This series adds basic driver model support to USB. The intent is to
> > > permit the various subsystems (OHCI, EHCI, XHCI) to co-exist and allow
> > > any number of USB ports of different types. So far the absolute limit
> > > on the number of USB devices is only slightly relaxed.
> > >
> > > Only USB controllers have a real driver model device. USB devices
> > > (including the hub in the controller) are not modelled as driver model
> > > devices. This is for two reasons:
> > >
> > > - it is easier since we don't need to bind a whole lot of devices when
> > >
> > > scanning
> > >
> > > - the two main USB devices (block devices and Ethernet) don't have
> > > driver
> > >
> > > mode support yet anyway, so it would be pointless. However the
> > > recent network RFC has encouraged me to send this.
> > >
> > > The basic approach is to set up the driver model structures in parallel
> > > to what already exists rather than to replace them. This allows both
> > > driver model and legacy to be used for USB, although not with the same
> > > board.
> > >
> > > So far only XHCI is supported. As an example the Exynos XHCI driver is
> > > converted to driver model.
> > >
> > > I would appreciate comments before going further.
> > >
> > > Caveats:
> > > - sandbox code is incomplete and there are no tests
> > > - 'usb stop' does not remove existing devices (I have not yet settled
> > > on the best approach)
> > > - the usb.h changes need to be split correctly into the patches once
> > > they
> > >
> > > are final
> > >
> > > This series is available at u-boot-dm/usb-working.
> >
> > Hi!
> >
> > I'll look at this by the end of next week, I will be free by then. It's
> > not possible for me to do it earlier, sorry. Does this still work for
> > you please?
>
> Definitely, that sounds good. I was planning to leave it a week or two
> anyway, although I might fiddle more with the sandbox side in the
> meantime.
I skimmed through the series finally, it looks mostly good for but a few
minor coding style things. I would prefer if this went in for the next MW,
what do you think please ?
Best regards,
Marek Vasut
next prev parent reply other threads:[~2015-02-09 21:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-30 19:04 [U-Boot] [RFC PATCH 0/7] RFC: dm: Add USB support Simon Glass
2015-01-30 19:04 ` [U-Boot] [RFC PATCH 1/7] dm: usb: Add a uclass for USB controllers Simon Glass
2015-02-09 20:59 ` Marek Vasut
2015-03-09 6:20 ` Vivek Gautam
2015-03-09 6:32 ` Vivek Gautam
2015-01-30 19:04 ` [U-Boot] [RFC PATCH 2/7] dm: usb: Support driver model in exynos XHCI Simon Glass
2015-01-30 19:04 ` [U-Boot] [RFC PATCH 3/7] dm: usb: Adjust users of the USB stack to work with driver model Simon Glass
2015-02-25 14:09 ` Vivek Gautam
2015-01-30 19:04 ` [U-Boot] [RFC PATCH 4/7] dm: usb: WIP sandbox USB implementation Simon Glass
2015-01-30 19:04 ` [U-Boot] [RFC PATCH 5/7] dm: core: Add a function to get the uclass data for a device Simon Glass
2015-01-30 19:04 ` [U-Boot] [RFC PATCH 6/7] arm: Show relocated PC/LR in the register dump Simon Glass
2015-02-01 8:45 ` Albert ARIBAUD
2015-02-02 16:42 ` Simon Glass
2015-02-03 19:20 ` Albert ARIBAUD
2015-01-30 19:04 ` [U-Boot] [RFC PATCH 7/7] dm: exynos: Enable driver model for snow XHCI Simon Glass
2015-01-30 22:16 ` [U-Boot] [RFC PATCH 0/7] RFC: dm: Add USB support Marek Vasut
2015-01-30 22:41 ` Simon Glass
2015-02-09 21:02 ` Marek Vasut [this message]
2015-02-10 5:28 ` Simon Glass
2015-02-10 18:52 ` Marek Vasut
2015-02-25 14:07 ` Vivek Gautam
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=201502092202.08511.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