From: Lukasz Majewski <lukma@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] dm: usb: gadget: Fix boot breakage on sunxi platforms
Date: Wed, 2 Jan 2019 13:15:06 +0100 [thread overview]
Message-ID: <20190102131506.03a70616@jawa> (raw)
In-Reply-To: <1334d28c-5b96-1359-811c-e1491c8aba7d@ti.com>
On Wed, 2 Jan 2019 11:38:47 +0100
Jean-Jacques Hiblot <jjhiblot@ti.com> wrote:
> On 29/12/2018 19:49, Jagan Teki wrote:
> > On Mon, Dec 24, 2018 at 3:44 AM Jagan Teki
> > <jagan@amarulasolutions.com> wrote:
> >> On Fri, Dec 21, 2018 at 2:20 PM Jean-Jacques Hiblot
> >> <jjhiblot@ti.com> wrote: Better to have proper commit head that
> >> tells the real issue.
>
> I found it hard to come up with a short description of the real issue.
>
> At least this title makes it clear that it is a regression fix, not a
> new feature.
>
> The details of the failures are in the commit log (or so I thought)
>
> >>
> >>> Fixes commit 013116243950 ("dm: usb: create a new UCLASS ID for
> >>> USB gadget devices")
> >>>
> >>> The UCLASS_DRIVER for id UCLASS_USB_GADGET_GENERIC needs to be
> >>> declared even for platforms that do not enable DM_USB_GADGET.
> >>> Otherwise the driver for their usb peripheral controller fails to
> >>> bind.
> >> Sorry this is unclear, you are trying to skip DM_USB_GADGET code
> >> even though UCLASS_USB_GADGET_GENERIC id used. does it make
> >> sense?
>
> Sorry for the delay. This was indeed a vacation time.
>
> This patch does not skip DM_USB_GADGET. What it does is declare the
> UCLASS_DRIVER for USB peripheral devices even if DM_USB_GADGET is not
> set.
>
> DM_USB_GADGET is a new option and not (yet) widely used and some
> drivers have their own version of the DM support for gadget drivers
> (ie they implement their own version of usb_gadget_initialize(),
> usb_gadget_release() and usb_gadget_handle_interrupts()). However all
> those drivers use the UCLASS_USB_GADGET_GENERIC uclass ID and thus
> the UCLASS_DRIVER for UCLASS_USB_GADGET_GENERIC must be declared. In
> the past they used UCLASS_USB_DEV_GENERIC, but this option is
> intended for the host side.
>
Thanks for a detailed explanation. Would you prepare v2 soon?
>
> JJ
>
> > Any response on this?
> >
> > We need the fix asap since the release is about a week.
> >
Best regards,
Lukasz Majewski
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma at denx.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190102/46bc6c88/attachment.sig>
next prev parent reply other threads:[~2019-01-02 12:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-21 8:50 [U-Boot] [PATCH] dm: usb: gadget: Fix boot breakage on sunxi platforms Jean-Jacques Hiblot
2018-12-23 22:14 ` Jagan Teki
2018-12-29 18:49 ` Jagan Teki
2018-12-30 15:55 ` Marek Vasut
2019-01-02 10:38 ` Jean-Jacques Hiblot
2019-01-02 12:15 ` Lukasz Majewski [this message]
2019-01-02 15:20 ` Jean-Jacques Hiblot
2019-01-02 18:25 ` Jagan Teki
2019-01-03 6:59 ` Lukasz Majewski
2019-01-03 13:44 ` Marek Vasut
2019-01-03 19:53 ` Jagan Teki
2019-01-03 19:54 ` Marek Vasut
2019-01-03 21:47 ` Lukasz Majewski
2019-01-04 0:04 ` Marek Vasut
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=20190102131506.03a70616@jawa \
--to=lukma@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