From: Lukasz Majewski <l.majewski@samsung.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] usb: gadget: composite: Correct recovery path for register
Date: Tue, 01 Mar 2016 13:42:21 +0100 [thread overview]
Message-ID: <20160301134221.6777bdeb@amdc2363> (raw)
In-Reply-To: <56D42E2E.4030600@denx.de>
Hi Marek,
> On 02/29/2016 11:11 AM, Lukasz Majewski wrote:
> > Hi Marek,
> >
> >> On 02/26/2016 08:43 PM, Sam Protsenko wrote:
> >>> On Fri, Feb 19, 2016 at 9:34 PM, Sam Protsenko
> >>> <semen.protsenko@linaro.org> wrote:
> >>>> + Praneeth Bajjuri
> >>>> + Tom Rini
> >>>> + Rob Herring
> >>>>
> >>>> On Tue, Feb 16, 2016 at 7:59 PM, Semen Protsenko
> >>>> <semen.protsenko@linaro.org> wrote:
> >>>>> From: Sam Protsenko <semen.protsenko@linaro.org>
> >>>>>
> >>>>> In case when usb_composite_register() failed once (for whatever
> >>>>> reason), it will fail further even if all conditions are
> >>>>> correct. Example:
> >>>>>
> >>>>> => fastboot 2
> >>>>> Invalid Controller Index
> >>>>> couldn't find an available UDC
> >>>>> g_dnl_register: failed!, error: -19
> >>>>> exit not allowed from main input shell.
> >>>>>
> >>>>> => fastboot 0
> >>>>> g_dnl_register: failed!, error: -22
> >>>>> exit not allowed from main input shell.
> >>>>>
> >>>>> Despite that 0 is correct index for USB controller, "fastboot 0"
> >>>>> command will fail, because "composite" structure wasn't cleared
> >>>>> properly on previous fail (on "fastboot 2" command).
> >>>>>
> >>>>> This patch fixes that erroneous behavior, allowing us to use
> >>>>> composite even after previous failure.
> >>>>>
> >>>>> Signed-off-by: Sam Protsenko <semen.protsenko@linaro.org>
> >>>>> ---
> >>>>> drivers/usb/gadget/composite.c | 8 +++++++-
> >>>>> 1 file changed, 7 insertions(+), 1 deletion(-)
> >>>>>
> >>>>> diff --git a/drivers/usb/gadget/composite.c
> >>>>> b/drivers/usb/gadget/composite.c index 60f9272..d0ee784 100644
> >>>>> --- a/drivers/usb/gadget/composite.c
> >>>>> +++ b/drivers/usb/gadget/composite.c
> >>>>> @@ -1077,6 +1077,8 @@ static struct usb_gadget_driver
> >>>>> composite_driver = { */
> >>>>> int usb_composite_register(struct usb_composite_driver *driver)
> >>>>> {
> >>>>> + int res;
> >>>>> +
> >>>>> if (!driver || !driver->dev || !driver->bind ||
> >>>>> composite) return -EINVAL;
> >>>>>
> >>>>> @@ -1084,7 +1086,11 @@ int usb_composite_register(struct
> >>>>> usb_composite_driver *driver) driver->name = "composite";
> >>>>> composite = driver;
> >>>>>
> >>>>> - return usb_gadget_register_driver(&composite_driver);
> >>>>> + res = usb_gadget_register_driver(&composite_driver);
> >>>>> + if (res != 0)
> >>>>> + composite = NULL;
> >>>>> +
> >>>>> + return res;
> >>>>> }
> >>>>>
> >>>>> /**
> >>>>> --
> >>>>> 2.7.0
> >>>>>
> >>>
> >>> bump
> >>>
> >>
> >> Looks fine. Lukasz, shall I pick this myself ?
> >>
> >> btw if this isn't applied in a week, please ping me and I will
> >> pick it nonetheless.
> >>
> >
> > I will add this to my tree. And test it afterwards.
This patch seems correct - no regression found.
Tested-by: Lukasz Majewski "<l.majewski@samsung.com>"
Acked-by: Lukasz Majewski "<l.majewski@samsung.com>"
> >
> > I will send new PR with some other patches.
Patches which I thought that you didn't pull are already in u-boot-usb
tree, so there is no point to prepare PR for this single patch.
Hence, Marek, please apply it directly to -usb tree.
> >
>
> Roger, thanks!
>
--
Best regards,
Lukasz Majewski
Samsung R&D Institute Poland (SRPOL) | Linux Platform Group
next prev parent reply other threads:[~2016-03-01 12:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 17:59 [U-Boot] [PATCH] usb: gadget: composite: Correct recovery path for register Semen Protsenko
2016-02-19 19:34 ` Sam Protsenko
2016-02-26 19:43 ` Sam Protsenko
2016-02-26 19:52 ` Marek Vasut
2016-02-29 10:11 ` Lukasz Majewski
2016-02-29 11:40 ` Marek Vasut
2016-03-01 12:42 ` Lukasz Majewski [this message]
2016-03-01 13:47 ` 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=20160301134221.6777bdeb@amdc2363 \
--to=l.majewski@samsung.com \
--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