From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] usb: r8a66597: Fix initialization hub that using, R8A66597_MAX_ROOT_HUB
Date: Thu, 17 Apr 2014 16:07:21 +0200 [thread overview]
Message-ID: <201404171607.21190.marex@denx.de> (raw)
In-Reply-To: <534F8750.70201@renesas.com>
On Thursday, April 17, 2014 at 09:48:32 AM, yasuhisa umano wrote:
> This driver is processed as two USB hub despite one.
> The number of root hub is defined in R8A66597_MAX_ROOT_HUB.
> This fixes that register is accessed by using the definition
> of R8A66597_MAX_ROOT_HUB.
>
> Signed-off-by: Yasuhisa Umano <yasuhisa.umano.zc@renesas.com>
> ---
> drivers/usb/host/r8a66597-hcd.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/usb/host/r8a66597-hcd.c
> b/drivers/usb/host/r8a66597-hcd.c index dfe5423..c58d2a9 100644
> --- a/drivers/usb/host/r8a66597-hcd.c
> +++ b/drivers/usb/host/r8a66597-hcd.c
> @@ -164,8 +164,8 @@ static int enable_controller(struct r8a66597 *r8a66597)
>
> r8a66597_bset(r8a66597, INTL, SOFCFG);
> r8a66597_write(r8a66597, 0, INTENB0);
> - r8a66597_write(r8a66597, 0, INTENB1);
> - r8a66597_write(r8a66597, 0, INTENB2);
> + for (port = 0; port < R8A66597_MAX_ROOT_HUB; port++)
> + r8a66597_write(r8a66597, 0, get_intenb_reg(port));
Hmm, looking at get_intenb_reg(), this is slightly dangerous, but I will trust
you you know what you are doing . I am a bit worried someone might set
R8A66597_MAX_ROOT_HUB to value >2 and will wonder why doesn't it work.
Anyway, I will apply this and if you feel my rant is valid, submit subsequent
patch.
Best regards,
Marek Vasut
next prev parent reply other threads:[~2014-04-17 14:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-17 7:48 [U-Boot] [PATCH 1/2] usb: r8a66597: Fix initialization hub that using, R8A66597_MAX_ROOT_HUB yasuhisa umano
2014-04-17 10:47 ` Marek Vasut
2014-04-18 2:25 ` Yasuhisa Umano
2014-04-17 14:07 ` Marek Vasut [this message]
2014-04-18 2:25 ` Yasuhisa Umano
2014-04-18 13:57 ` 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=201404171607.21190.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.