From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 7/7] usb: dwc2: Do not mix data toggle for IN and OUT endpoints, check bounds
Date: Fri, 22 Jan 2016 08:24:05 +0100 [thread overview]
Message-ID: <201601220824.05111.marex@denx.de> (raw)
In-Reply-To: <1453426243-833-1-git-send-email-stefan.bruens@rwth-aachen.de>
On Friday, January 22, 2016 at 02:30:43 AM, Stefan Br?ns wrote:
> USB protocol allows for 16 IN and 16 OUT endpoints (USB 2.0 Spec,
> 8.3.2.2 Endpoint Field). A function may have an EP 1 for both IN and OUT,
> so these two should be kept separate. As EPs are either BULK or INTERRUPT
> (or ISO), it is fine to have one array per direction for all transfer
> types (also see e236519b7365ef75c5da6a5623f0b03d9c00cfae).
>
> USB device address is 7 bits, so a bus may have more than 16 devices.
> Check the device number, as the DWC2 driver only supports BULK/ISO for
> the first 16 devices.
>
> Signed-off-by: Stefan Br?ns <stefan.bruens@rwth-aachen.de>
> ---
Since this is patch 7/7, where are the remaining 6 ?
> drivers/usb/host/dwc2.c | 29 +++++++++++++++++++----------
> 1 file changed, 19 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/usb/host/dwc2.c b/drivers/usb/host/dwc2.c
> index 291e4a5..7c107bc 100644
> --- a/drivers/usb/host/dwc2.c
> +++ b/drivers/usb/host/dwc2.c
> @@ -34,7 +34,8 @@ struct dwc2_priv {
> uint8_t *aligned_buffer;
> uint8_t *status_buffer;
> #endif
> - int bulk_data_toggle[MAX_DEVICE][MAX_ENDPOINT];
> + uint8_t in_data_toggle[MAX_DEVICE][MAX_ENDPOINT];
> + uint8_t out_data_toggle[MAX_DEVICE][MAX_ENDPOINT];
Use u8/u16/u32 please. All around the place .
> struct dwc2_core_regs *regs;
> int root_hub_devnum;
> };
The rest is fine,
Acked-by: Marek Vasut <marex@denx.de>
Thanks!
Best regards,
Marek Vasut
prev parent reply other threads:[~2016-01-22 7:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-22 1:30 [U-Boot] [PATCH 7/7] usb: dwc2: Do not mix data toggle for IN and OUT endpoints, check bounds Stefan Brüns
2016-01-22 1:52 ` Stefan Bruens
2016-01-22 7:24 ` 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=201601220824.05111.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.