All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mathias Nyman <mathias.nyman@linux.intel.com>
To: Peter Chen <peter.chen@nxp.com>
Cc: linux-usb@vger.kernel.org, gregkh@linuxfoundation.org,
	Lu Baolu <baolu.lu@linux.intel.com>,
	stable <stable@vger.kernel.org>
Subject: Re: [PATCH 1/1] usb: host: xhci-dbg: HCIVERSION should be a binary number
Date: Tue, 7 Mar 2017 16:20:24 +0200	[thread overview]
Message-ID: <58BEC1A8.8070206@linux.intel.com> (raw)
In-Reply-To: <1488855874-18837-1-git-send-email-peter.chen@nxp.com>

On 07.03.2017 05:04, Peter Chen wrote:
> According to xHCI spec, HCIVERSION containing a BCD encoding
> of the xHCI specification revision number, 0100h corresponds
> to xHCI version 1.0. Change "100" as "0x100".
>
> Cc: Lu Baolu <baolu.lu@linux.intel.com>
> Cc: stable <stable@vger.kernel.org>
> Fixes: 04abb6de2825 ("xhci: Read and parse new xhci
> 	1.1 capability register")
> Signed-off-by: Peter Chen <peter.chen@nxp.com>
> ---
>   drivers/usb/host/xhci-dbg.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/usb/host/xhci-dbg.c b/drivers/usb/host/xhci-dbg.c
> index 363d125..2b4a00f 100644
> --- a/drivers/usb/host/xhci-dbg.c
> +++ b/drivers/usb/host/xhci-dbg.c
> @@ -109,7 +109,7 @@ static void xhci_print_cap_regs(struct xhci_hcd *xhci)
>   	xhci_dbg(xhci, "RTSOFF 0x%x:\n", temp & RTSOFF_MASK);
>
>   	/* xhci 1.1 controllers have the HCCPARAMS2 register */
> -	if (hci_version > 100) {
> +	if (hci_version > 0x100) {
>   		temp = readl(&xhci->cap_regs->hcc_params2);
>   		xhci_dbg(xhci, "HCC PARAMS2 0x%x:\n", (unsigned int) temp);
>   		xhci_dbg(xhci, "  HC %s Force save context capability",
>

Thanks, queuing this

-Mathias
   

      reply	other threads:[~2017-03-07 20:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-07  3:04 [PATCH 1/1] usb: host: xhci-dbg: HCIVERSION should be a binary number Peter Chen
2017-03-07 14:20 ` Mathias Nyman [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=58BEC1A8.8070206@linux.intel.com \
    --to=mathias.nyman@linux.intel.com \
    --cc=baolu.lu@linux.intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=peter.chen@nxp.com \
    --cc=stable@vger.kernel.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 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.