public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Lukasz Majewski <l.majewski@samsung.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] fastboot: OUT transaction length must be aligned to wMaxPacketSize
Date: Wed, 06 Apr 2016 09:09:40 +0200	[thread overview]
Message-ID: <20160406090940.27b86500@amdc2363> (raw)
In-Reply-To: <CAM7GXomAdcVwhZwv-U2zZUUAum9=xeyj06vL+iKODqp2SpQVGQ@mail.gmail.com>

Hi Steve, Marek, Sam

> On Apr 5, 2016 3:07 PM, "Marek Vasut" <marex@denx.de> wrote:
> >
> > On 04/05/2016 08:31 PM, Steve Rae wrote:
> > > commit 9e4b510 fastboot: OUT transaction length must be aligned to
> wMaxPacketSize
> > > breaks some boards...
> > >
> > > Therefore add a conditional Kconfig to optionally enable this
> > > feature.
> >
> > Did you drill into it to figure out why this is needed ?
> >
> 
> Marek,
> Let me clarify....
> All my boards work with the original code (before the commit which
> aligned the size to the wMaxPacketSize).... Since that commit, all my
> boards are broken.
> And you will notice in this patch, that none of my boards define this
> CONFIG_ ...

Guys, please correct me if I'm wrong, but the problem _is_ be caused
by supporting different fastboot protocol versions.

Unfortunately, there is no way to specify "version" in the protocol so
different versions of fastboot application handle transmission
differently.

I think that Sam and Steve were trying to test the code by using their
fastboot apps, but without any conclusion. Am I right there? Has
something changed?

I'm OK with Kconfig flag approach, if we don't have any reliable way to
distinct protocol versions.

One fastboot user my try it with this option enabled or disabled.

What I would love to see is a proper entry into ./doc READMEs to
clarify this issue (not necessarily with this patch series). It would
help other users in the future.


> 
> So I think you are asking the wrong person to drill down into this
> issue.... Sorry, Steve
> 
> > > Signed-off-by: Steve Rae <srae@broadcom.com>
> > > ---
> > >
> > > Changes in v2:
> > > - ammendment to the original patch
> > >
> > >  drivers/usb/gadget/Kconfig      | 7 +++++++
> > >  drivers/usb/gadget/f_fastboot.c | 4 +++-
> > >  2 files changed, 10 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/drivers/usb/gadget/Kconfig
> > > b/drivers/usb/gadget/Kconfig index f4698f4..ab1c605 100644
> > > --- a/drivers/usb/gadget/Kconfig
> > > +++ b/drivers/usb/gadget/Kconfig
> > > @@ -33,3 +33,10 @@ menuconfig USB_GADGET
> > >          a USB peripheral device.  Configure one hardware driver
> > > for
> your
> > >          peripheral/device side bus controller, and a "gadget
> > > driver"
> for
> > >          your peripheral protocol.
> > > +
> > > +config USB_GADGET_FASTBOOT_DOWNLOAD_ALIGNMENT_REQUIRED
> > > +     bool "fastboot download requires alignment with
> > > wMaxPacketSize"
> > > +     help
> > > +        By default, the fastboot download OUT transactions are
> > > aligned
> > > +        to "ep->maxpacket". This option causes the fastboot
> > > download
> OUT
> > > +        transactions to be aligned with "wMaxPacketSize".
> > > diff --git a/drivers/usb/gadget/f_fastboot.c
> b/drivers/usb/gadget/f_fastboot.c
> > > index 2e87fee..130b5d0 100644
> > > --- a/drivers/usb/gadget/f_fastboot.c
> > > +++ b/drivers/usb/gadget/f_fastboot.c
> > > @@ -430,17 +430,19 @@ static void cb_getvar(struct usb_ep *ep,
> > > struct
> usb_request *req)
> > >  static unsigned int rx_bytes_expected(unsigned int maxpacket)
> > >  {
> > >       int rx_remain = download_size - download_bytes;
> > > -     int rem = 0;
> > > +     int __maybe_unused rem = 0;
> > >       if (rx_remain < 0)
> > >               return 0;
> > >       if (rx_remain > EP_BUFFER_SIZE)
> > >               return EP_BUFFER_SIZE;
> > > +#ifdef CONFIG_USB_GADGET_FASTBOOT_DOWNLOAD_ALIGNMENT_REQUIRED
> > >       if (rx_remain < maxpacket) {
> > >               rx_remain = maxpacket;
> > >       } else if (rx_remain % maxpacket != 0) {
> > >               rem = rx_remain % maxpacket;
> > >               rx_remain = rx_remain + (maxpacket - rem);
> > >       }
> > > +#endif
> > >       return rx_remain;
> > >  }
> > >
> > >
> >
> >
> > --
> > Best regards,
> > Marek Vasut



-- 
Best regards,

Lukasz Majewski

Samsung R&D Institute Poland (SRPOL) | Linux Platform Group

  reply	other threads:[~2016-04-06  7:09 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-05 18:31 [U-Boot] [PATCH v2] fastboot: OUT transaction length must be aligned to wMaxPacketSize Steve Rae
2016-04-05 22:06 ` Marek Vasut
2016-04-06  5:35   ` Steve Rae
2016-04-06  7:09     ` Lukasz Majewski [this message]
2016-04-06 10:57       ` Marek Vasut
2016-04-06 11:01     ` Marek Vasut
2016-04-06 17:18       ` Steve Rae
2016-04-06 19:53         ` Marek Vasut
2016-04-06 20:45           ` Steve Rae
2016-04-06 20:57             ` Marek Vasut
2016-04-07  8:03               ` Lukasz Majewski
2016-04-07  7:36         ` Lukasz Majewski
2016-04-07 16:46           ` Sam Protsenko
2016-04-07 17:07             ` Steve Rae
2016-04-07 21:16               ` Sam Protsenko
2016-04-07 21:39                 ` Steve Rae
2016-04-07 23:11                   ` Sam Protsenko
2016-04-07 23:15                     ` Steve Rae
2016-04-08 19:44                     ` Tom Rini
2016-04-11 12:29                       ` B, Ravi
2016-04-07 18:40             ` Marek Vasut
2016-04-11 11:34               ` Mugunthan V N
2016-04-11 15:22                 ` Tom Rini
2016-04-12 11:19                   ` Lukasz Majewski
2016-04-12 12:40                     ` Roger Quadros
2016-04-12 13:37                       ` Lukasz Majewski
2016-04-12 13:50                         ` Roger Quadros
2016-04-13  1:55                           ` Steve Rae
2016-04-14 11:15                             ` Roger Quadros
2016-04-15 19:56                               ` Steve Rae

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=20160406090940.27b86500@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