From: balbi@kernel.org (Felipe Balbi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v1] usb: host: Implement workaround for Erratum A-007463
Date: Thu, 21 Sep 2017 09:48:03 +0300 [thread overview]
Message-ID: <87fubg4kf0.fsf@linux.intel.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1709201004040.1563-100000@iolanthe.rowland.org>
Hi,
Alan Stern <stern@rowland.harvard.edu> writes:
> The Subject: line should specify which type of USB host controller the
> patch is for. The kernel contains lots of different USB host
> controller drivers. How are we supposed to know that Erratum A-007463
> applies to dwc3 xHCI controllers?
>
> The Subject: line should say something like:
>
> [PATCH v1] USB: host: dwc3: Implement workaround for Erratum A-007643
If we're talking about a dwc3 implementation, we need a quirk flag on
dwc3 core to be passed down to the xhci-plat device, like every other
quirk on this controller.
I also need a reference to SNPS stars ticket that talks about this problem.
--
balbi
WARNING: multiple messages have this Message-ID (diff)
From: Felipe Balbi <balbi-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Alan Stern
<stern-nwvwT67g6+6dFdvTe/nMLpVzexx5G7lz@public.gmane.org>,
yinbo.zhu-3arQi8VN3Tc@public.gmane.org
Cc: Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
Russell King <linux-I+IVW8TIWO2tmTQ+vhA3Yw@public.gmane.org>,
Greg Kroah-Hartman
<gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org>,
Mathias Nyman
<mathias.nyman-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"moderated list:ARM PORT"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
open list <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"open list:DESIGNWARE USB3 DRD IP DRIVER"
<linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH v1] usb: host: Implement workaround for Erratum A-007463
Date: Thu, 21 Sep 2017 09:48:03 +0300 [thread overview]
Message-ID: <87fubg4kf0.fsf@linux.intel.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1709201004040.1563-100000-IYeN2dnnYyZXsRXLowluHWD2FQJk+8+b@public.gmane.org>
Hi,
Alan Stern <stern-nwvwT67g6+6dFdvTe/nMLpVzexx5G7lz@public.gmane.org> writes:
> The Subject: line should specify which type of USB host controller the
> patch is for. The kernel contains lots of different USB host
> controller drivers. How are we supposed to know that Erratum A-007463
> applies to dwc3 xHCI controllers?
>
> The Subject: line should say something like:
>
> [PATCH v1] USB: host: dwc3: Implement workaround for Erratum A-007643
If we're talking about a dwc3 implementation, we need a quirk flag on
dwc3 core to be passed down to the xhci-plat device, like every other
quirk on this controller.
I also need a reference to SNPS stars ticket that talks about this problem.
--
balbi
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Felipe Balbi <balbi@kernel.org>
To: Alan Stern <stern@rowland.harvard.edu>, yinbo.zhu@nxp.com
Cc: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Russell King <linux@armlinux.org.uk>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Mathias Nyman <mathias.nyman@intel.com>,
"open list\:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
"moderated list\:ARM PORT" <linux-arm-kernel@lists.infradead.org>,
open list <linux-kernel@vger.kernel.org>,
"open list\:DESIGNWARE USB3 DRD IP DRIVER"
<linux-usb@vger.kernel.org>
Subject: Re: [PATCH v1] usb: host: Implement workaround for Erratum A-007463
Date: Thu, 21 Sep 2017 09:48:03 +0300 [thread overview]
Message-ID: <87fubg4kf0.fsf@linux.intel.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1709201004040.1563-100000@iolanthe.rowland.org>
Hi,
Alan Stern <stern@rowland.harvard.edu> writes:
> The Subject: line should specify which type of USB host controller the
> patch is for. The kernel contains lots of different USB host
> controller drivers. How are we supposed to know that Erratum A-007463
> applies to dwc3 xHCI controllers?
>
> The Subject: line should say something like:
>
> [PATCH v1] USB: host: dwc3: Implement workaround for Erratum A-007643
If we're talking about a dwc3 implementation, we need a quirk flag on
dwc3 core to be passed down to the xhci-plat device, like every other
quirk on this controller.
I also need a reference to SNPS stars ticket that talks about this problem.
--
balbi
next prev parent reply other threads:[~2017-09-21 6:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-20 9:24 [PATCH v1] usb: host: Implement workaround for Erratum A-007463 yinbo.zhu at nxp.com
2017-09-20 9:24 ` yinbo.zhu
2017-09-20 9:24 ` yinbo.zhu-3arQi8VN3Tc
2017-09-20 9:50 ` Greg Kroah-Hartman
2017-09-20 9:50 ` Greg Kroah-Hartman
2017-09-20 9:53 ` Greg Kroah-Hartman
2017-09-20 9:53 ` Greg Kroah-Hartman
2017-09-20 9:53 ` Greg Kroah-Hartman
2017-09-20 12:57 ` Mathias Nyman
2017-09-20 12:57 ` Mathias Nyman
2017-09-20 12:57 ` Mathias Nyman
2017-09-20 14:07 ` Alan Stern
2017-09-20 14:07 ` Alan Stern
2017-09-20 14:07 ` Alan Stern
2017-09-21 6:48 ` Felipe Balbi [this message]
2017-09-21 6:48 ` Felipe Balbi
2017-09-21 6:48 ` Felipe Balbi
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=87fubg4kf0.fsf@linux.intel.com \
--to=balbi@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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.