From: Greg KH <gregkh@linuxfoundation.org>
To: Jim Lin <jilin@nvidia.com>
Cc: mathias.nyman@intel.com, stern@rowland.harvard.edu,
kai.heng.feng@canonical.com, drinkcat@chromium.org,
keescook@chromium.org, nsaenzjulienne@suse.de,
jflat@chromium.org, malat@debian.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v8 1/2] usb: hub : Add devaddr in struct usb_device
Date: Fri, 10 May 2019 11:31:05 +0200 [thread overview]
Message-ID: <20190510093105.GA9357@kroah.com> (raw)
In-Reply-To: <1557478937-30486-2-git-send-email-jilin@nvidia.com>
On Fri, May 10, 2019 at 05:02:16PM +0800, Jim Lin wrote:
> The Clear_TT_Buffer request sent to the hub includes the address of
> the LS/FS child device in wValue field. usb_hub_clear_tt_buffer()
> uses udev->devnum to set the address wValue. This won't work for
> devices connected to xHC.
>
> For other host controllers udev->devnum is the same as the address of
> the usb device, chosen and set by usb core. With xHC the controller
> hardware assigns the address, and won't be the same as devnum.
>
> Here we add devaddr in "struct usb_device" for
> usb_hub_clear_tt_buffer() to use.
>
> Signed-off-by: Jim Lin <jilin@nvidia.com>
> ---
> v2: xhci_clear_tt_buffer_complete: add static, shorter indentation
> , remove its claiming in xhci.h
> v3: Add description for clearing_tt (xhci.h)
> v4: Remove clearing_tt flag because hub_tt_work has hub->tt.lock
> to protect for Clear_TT_Buffer to be run serially.
> Remove xhci_clear_tt_buffer_complete as it's not necessary.
> Same reason as the above.
> Extend usb_hub_clear_tt_buffer parameter
> v5: Not extending usb_hub_clear_tt_buffer parameter
> Add description.
> v6: Remove unused parameter slot_id from xhci_clear_hub_tt_buffer
> v7: Add devaddr field in "struct usb_device"
> v8: split as two patches, change type from int to u8 for devaddr.
>
> drivers/usb/core/hub.c | 4 +++-
> include/linux/usb.h | 2 ++
> 2 files changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/usb/core/hub.c b/drivers/usb/core/hub.c
> index 15a2934dc29d..078894023797 100644
> --- a/drivers/usb/core/hub.c
> +++ b/drivers/usb/core/hub.c
> @@ -873,7 +873,7 @@ int usb_hub_clear_tt_buffer(struct urb *urb)
> /* info that CLEAR_TT_BUFFER needs */
> clear->tt = tt->multi ? udev->ttport : 1;
> clear->devinfo = usb_pipeendpoint (pipe);
> - clear->devinfo |= udev->devnum << 4;
> + clear->devinfo |= (u16) (udev->devaddr << 4);
> clear->devinfo |= usb_pipecontrol(pipe)
> ? (USB_ENDPOINT_XFER_CONTROL << 11)
> : (USB_ENDPOINT_XFER_BULK << 11);
> @@ -2125,6 +2125,8 @@ static void update_devnum(struct usb_device *udev, int devnum)
> /* The address for a WUSB device is managed by wusbcore. */
> if (!udev->wusb)
> udev->devnum = devnum;
> + if (!udev->devaddr)
> + udev->devaddr = (u8) devnum;
Checkpatch did not complain here? Or above? Please don't put a space
before the ) when casting.
> }
>
> static void hub_free_dev(struct usb_device *udev)
> diff --git a/include/linux/usb.h b/include/linux/usb.h
> index 4229eb74bd2c..db38c13a6b1d 100644
> --- a/include/linux/usb.h
> +++ b/include/linux/usb.h
> @@ -565,6 +565,7 @@ struct usb3_lpm_parameters {
> * @tx_lanes: number of tx lanes in use, USB 3.2 adds dual-lane support
> * @tt: Transaction Translator info; used with low/full speed dev, highspeed hub
> * @ttport: device port on that tt hub
> + * @devaddr: device address, XHCI: assigned by HW, others: same as devnum
> * @toggle: one bit for each endpoint, with ([0] = IN, [1] = OUT) endpoints
> * @parent: our hub, unless we're the root
> * @bus: bus we're part of
> @@ -641,6 +642,7 @@ struct usb_device {
>
> struct usb_tt *tt;
> int ttport;
> + u8 devaddr;
That's some horrible variable alignment :(
Please use pahole to find a better place to put it.
thanks,
greg k-h
next prev parent reply other threads:[~2019-05-10 9:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-10 9:02 [PATCH v8 0/2] usb: xhci: Add Clear_TT_Buffer Jim Lin
2019-05-10 9:02 ` [PATCH v8 1/2] usb: hub : Add devaddr in struct usb_device Jim Lin
2019-05-10 9:31 ` Greg KH [this message]
2019-05-10 9:02 ` [PATCH v8 2/2] usb: xhci: Add Clear_TT_Buffer support 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=20190510093105.GA9357@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=drinkcat@chromium.org \
--cc=jflat@chromium.org \
--cc=jilin@nvidia.com \
--cc=kai.heng.feng@canonical.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=malat@debian.org \
--cc=mathias.nyman@intel.com \
--cc=nsaenzjulienne@suse.de \
--cc=stern@rowland.harvard.edu \
/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