From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] usb: Early failure when the first descriptor read fails, one way or another
Date: Fri, 3 Apr 2015 04:01:35 +0200 [thread overview]
Message-ID: <201504030401.35150.marex@denx.de> (raw)
In-Reply-To: <1427722503.2521.9.camel@collins>
On Monday, March 30, 2015 at 03:35:03 PM, Paul Kocialkowski wrote:
> Le lundi 30 mars 2015 ? 01:47 +0200, Marek Vasut a ?crit :
[...]
> > > > Hi,
> > > >
> > > > since this is an error, this should probably be a printf(). Also,
> > > > to make the error message useful, it should state the invalid value
> > > > due to which it failed.
> > >
> > > Well, it is not unexpected behaviour in my use case (but I reckon it
> > > may be generally speaking).
> >
> > Why is this not unexpected in your case please ?
>
> Because using an USB low speed device with an EHCI controller should
> normally fail (that is, the first descriptor read returns 0 bytes), or
> at least it does on the sunxi platforms. I thought there was no need to
> report that as an error, but I changed my mind.
Indeed.
> Since the end result is that the USB device won't work, I think it makes
> sense to print an error.
Yes, I agree.
> > > If you're not convinced by this, I can still make a v2 with printf, I
> > > just don't think it's a necessity.
> >
> > Let me just understand what you're seeing a bit better first please .
>
> At this point, v2 of this patch was sent as: usb: Early failure when the
> first descriptor read fails or is invalid
>
> Let me know if you need some more context on this.
This is OK, thank you for clarifying !
Best regards,
Marek Vasut
prev parent reply other threads:[~2015-04-03 2:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-28 17:23 [U-Boot] [PATCH] usb: Early failure when the first descriptor read fails, one way or another Paul Kocialkowski
2015-03-28 17:26 ` Marek Vasut
2015-03-28 17:31 ` Paul Kocialkowski
2015-03-29 10:30 ` Paul Kocialkowski
2015-03-29 23:47 ` Marek Vasut
2015-03-30 13:35 ` Paul Kocialkowski
2015-04-03 2:01 ` 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=201504030401.35150.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