The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Jim Lin <jilin@nvidia.com>
To: <gregkh@linuxfoundation.org>, <swarren@wwwdotorg.org>
Cc: <linux-usb@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	Jim Lin <jilin@nvidia.com>
Subject: [PATCH v2 1/1] USB: EHCI: Tegra: Fix wrong register definition
Date: Wed, 19 Sep 2012 11:48:50 +0800	[thread overview]
Message-ID: <1348026530-17327-1-git-send-email-jilin@nvidia.com> (raw)

Fix the issue that EHCI registers, hostpc[0] and usbmode_ex,
are not correctly accessed on Tegra3 platform.

Signed-off-by: Jim Lin <jilin@nvidia.com>
---
Changes in v2:
- Modify array size for reserved4[] only.
- Note that defining hostpc[0] is for a variable-length object.
 
 include/linux/usb/ehci_def.h |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/include/linux/usb/ehci_def.h b/include/linux/usb/ehci_def.h
index de4b9ed..b3c9d1b 100644
--- a/include/linux/usb/ehci_def.h
+++ b/include/linux/usb/ehci_def.h
@@ -171,7 +171,7 @@ struct ehci_regs {
 #define USBMODE_CM_HC	(3<<0)		/* host controller mode */
 #define USBMODE_CM_IDLE	(0<<0)		/* idle state */
 
-	u32		reserved4[7];
+	u32		reserved4[6];
 
 /* Moorestown has some non-standard registers, partially due to the fact that
  * its EHCI controller has both TT and LPM support. HOSTPCx are extensions to
-- 
1.7.3


             reply	other threads:[~2012-09-19  3:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-19  3:48 Jim Lin [this message]
2012-09-19  6:29 ` [PATCH v2 1/1] USB: EHCI: Tegra: Fix wrong register definition Greg KH
2012-09-19  7:53   ` Jim Lin
2012-09-19  8:04     ` Greg KH
2012-09-19  8:32       ` Jim Lin
2012-09-19  8:04   ` Jim Lin

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=1348026530-17327-1-git-send-email-jilin@nvidia.com \
    --to=jilin@nvidia.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=swarren@wwwdotorg.org \
    /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