Hi Rafał,
On 01/20/2017 10:56 PM, Rafał Miłecki wrote:
> From: Rafał Miłecki
>
> Some LEDs can be related to particular devices described in DT. This
> property allows specifying such relations. E.g. USB LED should usually
> be used to indicate some USB port(s) state.
>
> Signed-off-by: Rafał M
From: Rafał Miłecki
This adds support for using description of relation between LEDs and USB
ports from device tree. If DT has properly described LEDs, trigger will
know when to turn them on.
Signed-off-by: Rafał Miłecki
---
V2: Update to use "led-triggers"
---
drivers/usb/core/ledtrig-usbport
From: Rafał Miłecki
Some LEDs can be related to particular devices described in DT. This
property allows specifying such relations. E.g. USB LED should usually
be used to indicate some USB port(s) state.
Signed-off-by: Rafał Miłecki
---
V2: Replace "usb-ports" with "led-triggers" property which
From: Rafał Miłecki
Signed-off-by: Rafał Miłecki
---
This patch *should not* be applied. It's only an EXAMPLE and that's why it uses
weird 3/2 number.
It's a proof of concept, it was tested & will be submitted through ARM tree if
previous patches get accepted.
---
arch/arm/boot/dts/bcm47189-te
On 01/19/2017 11:55 AM, Krzysztof Opasiak wrote:
Since commit ba1582f22231 ("usb: gadget: f_hid: use alloc_ep_req()")
we cannot allocate any requests in bind() as we check if we should
align request buffer based on endpoint descriptor which is assigned
in set_alt().
Allocating request in bind()
On Fri, Jan 20, 2017 at 12:01:04PM -0800, Tony Lindgren wrote:
> I noticed in sprz360i.pdf there's "Advisory 1.0.34 USB2PHY: Register
> Accesses After a USB Subsystem Soft Reset May Lock Up the Entire System"
> that seems to affect am335x revisions 1.0, 2.0 and 2.1:
>
> "The synchronization bridge
* Bin Liu [170120 13:08]:
> On Fri, Jan 20, 2017 at 12:07:53PM -0800, Tony Lindgren wrote:
> > With patches "dmaengine: cppi41: Fix runtime PM timeouts with USB mass
> > storage", and "dmaengine: cppi41: Fix oops in cppi41_runtime_resume",
> > the pm_runtime_get/put() in cppi41_irq() is no longer
* Bin Liu [170120 12:32]:
> On Fri, Jan 20, 2017 at 12:01:04PM -0800, Tony Lindgren wrote:
> > I noticed in sprz360i.pdf there's "Advisory 1.0.34 USB2PHY: Register
> > Accesses After a USB Subsystem Soft Reset May Lock Up the Entire System"
> > that seems to affect am335x revisions 1.0, 2.0 and 2.
On Fri, Jan 20, 2017 at 12:07:53PM -0800, Tony Lindgren wrote:
> With patches "dmaengine: cppi41: Fix runtime PM timeouts with USB mass
> storage", and "dmaengine: cppi41: Fix oops in cppi41_runtime_resume",
> the pm_runtime_get/put() in cppi41_irq() is no longer needed. We now
> guarantee that cpp
On Thu, Jan 19, 2017 at 11:06:59AM +0100, Alexandre Bailon wrote:
> Despite the CPPI 4.1 is a generic DMA, it is tied to USB.
> On the dsps, CPPI 4.1 interrupt's registers are in USBSS (the MUSB glue).
> Currently, to enable / disable and clear interrupts, the CPPI 4.1 driver
> maps and accesses to
With patches "dmaengine: cppi41: Fix runtime PM timeouts with USB mass
storage", and "dmaengine: cppi41: Fix oops in cppi41_runtime_resume",
the pm_runtime_get/put() in cppi41_irq() is no longer needed. We now
guarantee that cppi41 is enabled when dma is in use.
We can still get pointless error -1
I noticed in sprz360i.pdf there's "Advisory 1.0.34 USB2PHY: Register
Accesses After a USB Subsystem Soft Reset May Lock Up the Entire System"
that seems to affect am335x revisions 1.0, 2.0 and 2.1:
"The synchronization bridge connecting the USB2PHY register interface
to the L3S interconnect may h
On Thu, Jan 19, 2017 at 11:06:57AM +0100, Alexandre Bailon wrote:
> Currently, the CPPI 4.1 driver is not completely generic and
> only work on dsps. This is because of IRQ management.
> Add a callback to dma_controller that could be invoked on DMA completion
> to acknodlege the IRQ.
>
> Signed-of
On 1/17/2017 8:30 PM, John Youn wrote:
> Hi Felipe,
>
> This is a consolidation, rebase, and resend of several dwc2 patch
> series that were submitted to linux-usb in the past month or so. These
> should all be applied to testing/next for 4.11.
>
> See the following links for the original list mess
While testing musb host mode cable plugging on a BeagleBone, I came across this
error:
Unhandled fault: external abort on non-linefetch (0x1008) at 0xd1dcfc60
...
[] (musb_default_readb [musb_hdrc]) from []
(musb_irq_work+0x1c/0x180 [musb_hdrc])
[] (musb_irq_work [musb_hdrc]) from []
(process_on
On Wed, Jan 18, 2017 at 06:29:58PM -0800, Tony Lindgren wrote:
> Commit 467d5c980709 ("usb: musb: Implement session bit based runtime PM for
> musb-core") started implementing musb generic runtime PM support by
> introducing devctl register session bit based state control.
>
> This caused a regres
The HSIC USB controller on qcom SoCs has an integrated all
digital phy controlled via the ULPI viewport.
Acked-by: Rob Herring
Cc:
Signed-off-by: Stephen Boyd
---
No changes.
.../devicetree/bindings/phy/qcom,usb-hsic-phy.txt | 65 +
drivers/phy/Kconfig
This patch series continues the usb chipidea rewrite for
Qualcommm platforms. I've dropped the patches that were applied
to Peter's tree for chipidea. Now the phy drivers are left,
along with a new hook to set the vbus in the phy and changes
to chipidea to call the new hook.
I've left the HSIC ph
When the qcom chipidea controller is used with an extcon, we need
to signal device mode or host mode to the phy so it can configure
itself for the correct mode. This should be done after the phy is
powered up, so that the register writes work correctly. Add in
the appropriate phy_set_mode() call he
Some USB PHYs need to be told about vbus changing state
explicitly. For example the qcom USB HS PHY needs to toggle a bit
when vbus goes from low to high (VBUSVLDEXT) to cause the
"session valid" signal to toggle. This signal will pull up D+
when the phy starts running. Add the appropriate phy_set_
The high-speed phy on qcom SoCs is controlled via the ULPI
viewport.
Cc:
Acked-by: Rob Herring
Signed-off-by: Stephen Boyd
---
phy_set_mode() hook split up to toggle two bits independently
with new set_vbus() hook.
.../devicetree/bindings/phy/qcom,usb-hs-phy.txt| 78 +++
drivers/phy
Some USB PHYs need to be told about vbus changing state
explicitly. For example the qcom USB HS PHY needs to toggle a bit
when vbus goes from low to high (VBUSVLDEXT) to cause the
"session valid" signal to toggle. This signal will pull up D+
when the phy starts running. If the vbus signal isn't rou
* Bin Liu [170120 09:24]:
> On Thu, Jan 19, 2017 at 08:56:46AM -0800, Tony Lindgren wrote:
> > * Alexandre Bailon [170119 06:09]:
> > > The DMA may hung up if a teardown is initiated while an endpoint is still
> > > active (Advisory 2.3.27 of DA8xx errata).
> > > To workaround this issue, add a d
Mathias Nyman writes:
> Remove duplicate code by using trb_to_noop() when
> handling Aborted commads
>
> Signed-off-by: Mathias Nyman
https://marc.info/?i=20161229110109.26372-25-felipe.ba...@linux.intel.com
?
--
balbi
--
To unsubscribe from this list: send the line "unsubscribe linux-u
Mathias Nyman writes:
> Remove duplicate code by using trb_to_noop() when
> handling Aborted commads
>
> Signed-off-by: Mathias Nyman
isn't this just [1]
https://marc.info/?i=20161229110109.26372-25-felipe.ba...@linux.intel.com
--
balbi
--
To unsubscribe from this list: send the line "
Mathias Nyman writes:
> Useful for turning both transfer and command trbs
> into no-ops
>
> Signed-off-by: Mathias Nyman
isn't this just [1]
[1] https://marc.info/?i=20161229110109.26372-24-felipe.ba...@linux.intel.com
--
balbi
--
To unsubscribe from this list: send the line "unsubscri
Hi Mathias,
> -Original Message-
> From: Mathias Nyman [mailto:mathias.ny...@linux.intel.com]
> Sent: Friday, January 20, 2017 10:38 PM
> To: gre...@linuxfoundation.org; Anurag Kumar Vulisha
>
> Cc: linux-usb@vger.kernel.org; mathias.ny...@intel.com; Punnaiah
> Choudary Kalluri
> Subject
On Fri, Jan 20, 2017 at 10:50:03PM +0530, Vinod Koul wrote:
> On Thu, Jan 19, 2017 at 08:49:06AM -0800, Tony Lindgren wrote:
> > Hi all,
> >
> > I'm using v4 naming here as the earlier patch "dmaengine: cppi41: Add dma
> > support to da8xx" has been separated from the error -115 issue. We've
> > i
On Thu, Jan 19, 2017 at 08:56:46AM -0800, Tony Lindgren wrote:
> * Alexandre Bailon [170119 06:09]:
> > The DMA may hung up if a teardown is initiated while an endpoint is still
> > active (Advisory 2.3.27 of DA8xx errata).
> > To workaround this issue, add a delay before to initiate the teardown.
On Thu, Jan 19, 2017 at 08:49:06AM -0800, Tony Lindgren wrote:
> Hi all,
>
> I'm using v4 naming here as the earlier patch "dmaengine: cppi41: Add dma
> support to da8xx" has been separated from the error -115 issue. We've
> identified so far three musb and cppi41 regressions:
Hi,
Can we get som
On 20.01.2017 10:41, gre...@linuxfoundation.org wrote:
On Fri, Jan 20, 2017 at 07:59:48AM +, Anurag Kumar Vulisha wrote:
Hi,
Hi!
Minor nit, vger.kernel.org rejects html emails, so this didn't make it
through to that list. Now it should with my response :)
I have a usecase where I want
On 01/20/2017 05:47 PM, Mathias Nyman wrote:
Useful for turning both transfer and command trbs
into no-ops
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci-ring.c | 32
1 file changed, 20 insertions(+), 12 deletions(-)
diff --git a/drivers/usb/host/xhci
Hello!
On 01/20/2017 05:47 PM, Mathias Nyman wrote:
From: Felipe Balbi
If we add that newline, the output will like like the following:
Look like. :-)
kworker/2:1-42[002] 169.811435: xhci_address_ctx:
ctx_64=0, ctx_type=2, ctx_dma=@153fbd000, ctx_va=@880153fbd000
W
From: Hayes Wang
Date: Fri, 20 Jan 2017 14:33:55 +0800
> The rtl8152_post_reset() should sumbit rx urb and interrupt transfer,
> otherwise the rx wouldn't work and the linking change couldn't be
> detected.
>
> Signed-off-by: Hayes Wang
Applied, thank you.
--
To unsubscribe from this list: sen
On 20.01.2017 16:49, Patrice CHOTARD wrote:
On 01/13/2017 05:12 PM, Patrice Chotard wrote:
On 01/12/2017 06:17 PM, Mathias Nyman wrote:
On 09.01.2017 18:42, Mathias Nyman wrote:
On 09.01.2017 16:23, Patrice Chotard wrote:
On 01/09/2017 01:30 PM, Mathias Nyman wrote:
On 09.01.2017 11:51, Pat
From: Cristian Birsan
Update atmel udc driver with a new enpoint allocation scheme. The data
sheet requires that all endpoints are allocated in order.
Signed-off-by: Cristian Birsan
---
drivers/usb/gadget/udc/Kconfig | 14 ++
drivers/usb/gadget/udc/atmel_usba_udc.c | 236
From: Cristian Birsan
Hi,
This patch updates the usb endpoint allocation scheme for atmel usba
driver to make sure all endpoints are allocated in order. This requirement
comes from the datasheet of the controller.
The allocation scheme is decided by fifo_mode parameter. For fifo_mode = 0
the dr
On 01/19/2017 05:56 PM, Tony Lindgren wrote:
> * Alexandre Bailon [170119 06:09]:
>> The DMA may hung up if a teardown is initiated while an endpoint is still
>> active (Advisory 2.3.27 of DA8xx errata).
>> To workaround this issue, add a delay before to initiate the teardown.
>>
>> Signed-off-by:
urb_priv structure has a count on how many TDs the
URB contains, and how many of those TD's we have handled.
rename:
length -> num_tds
td_cnt -> num_tds_done
No functional changes
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci-ring.c | 10 +-
drivers/usb/host/xhci.c | 14 +
Instead of storing a zero length array of td pointers, and then
allocate memory both for the td pointer array and the td's, just
use a zero length array of actual td's in urb private data.
old:
struct urb_priv {
struct xhci_td *td[0]
}
new:
struct urb_priv {
struct xhci_td td[0]
From: Felipe Balbi
If we add that newline, the output will like like the following:
kworker/2:1-42[002] 169.811435: xhci_address_ctx:
ctx_64=0, ctx_type=2, ctx_dma=@153fbd000, ctx_va=@880153fbd000
We would rather have that in a single line.
Signed-off-by: Felipe Balbi
Sign
From: Felipe Balbi
when getting endpoint type, a switch statement looks
better than a series of if () branches. There are no
functional changes with this patch, cleanup only.
Signed-off-by: Felipe Balbi
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci-mem.c | 10 ++
1 file chang
Use switch instead of several if statements
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci.c | 93 -
1 file changed, 37 insertions(+), 56 deletions(-)
diff --git a/drivers/usb/host/xhci.c b/drivers/usb/host/xhci.c
index dde5c2d..6d6c460 10
From: Felipe Balbi
If we just provide a helper to convert completion code to string, we can
combine all debugging messages into a single print.
[keep the old debug messages, for warn and grep -Mathias]
Signed-off-by: Felipe Balbi
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci.h | 80 +
From: Felipe Balbi
Let's start tracing at least part of an xhci_virt_device lifetime. We
might want to extend this tracepoint class later, but for now it already
exposes quite a bit of valuable information.
Signed-off-by: Felipe Balbi
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci-hub
No functinal changes.
num_tds describes the number of transfer descriptor better than "size"
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci.c | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/drivers/usb/host/xhci.c b/drivers/usb/host/xhci.c
index 4968e
From: Felipe Balbi
no functional changes. Simple cleanup to make sure variables are ordered
in a 'reverse christmas tree' fashion. While at that, also remove an
obsolete comment which doesn't apply anymore.
Signed-off-by: Felipe Balbi
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci-rin
From: Felipe Balbi
When calling xhci_dbg_regs() we actually _do_ want to know XHCI's
version. This might help figure out why certain problems only happen
in some cases.
Signed-off-by: Felipe Balbi
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci-dbg.c | 2 --
1 file changed, 2 deletions
Remove duplicate code by using trb_to_noop() when
handling Aborted commads
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci-ring.c | 12 ++--
1 file changed, 2 insertions(+), 10 deletions(-)
diff --git a/drivers/usb/host/xhci-ring.c b/drivers/usb/host/xhci-ring.c
index 699fc2d..b3
Useful for turning both transfer and command trbs
into no-ops
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci-ring.c | 32
1 file changed, 20 insertions(+), 12 deletions(-)
diff --git a/drivers/usb/host/xhci-ring.c b/drivers/usb/host/xhci-ring.c
index 8b7
From: Felipe Balbi
Replace list_entry() with list_first_entry() and list_for_each() with
list_for_each_entry(). This makes the code slightly more readable.
Signed-off-by: Felipe Balbi
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci-ring.c | 19 ++-
1 file changed, 10 in
A counter was used to find out if the stop endpoint completion raced with
the stop endpoint timeout timer. This was needed in case the stop ep
completion failed to delete the timer as it was running on anoter cpu.
The EP_STOP_CMD_PENDING flag was not enough as a new stop endpoint command
may be qu
From: Felipe Balbi
handle_tx_event() is not releasing xhci->lock nor reacquiring it, remove
the bogus annotation.
Signed-off-by: Felipe Balbi
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci-ring.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/usb/host/xhci-ring.c b/drive
From: Felipe Balbi
This way we can remove checks for valid ring from call sites of
xhci_unmap_td_bounce_buffer()
Signed-off-by: Felipe Balbi
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci-ring.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/host/xhci-
From: Felipe Balbi
In case 'quirk-broken-port-ped' property is passed in via device property,
we should enable the corresponding BROKEN_PED quirk flag for XHCI core.
[rog...@ti.com] Updated code from platform data to device property
and added DT binding.
Signed-off-by: Felipe Balbi
Signed-off-
Hi Greg
A lot of xhci cleanups, refactoring and changes for 4.11
Including major tracing rework by Felipe
-Mathias
Alexander Stein (1):
xhci: Put warning message on a single line
Baolin Wang (1):
usb: host: xhci: Remove unused 'addr_64' variable in xhci_hcd
structure
Felipe Balbi (20):
From: Lu Baolu
Remove the unnecessary return line in xhci_pci_setup().
Signed-off-by: Lu Baolu
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci-pci.c | 6 +-
1 file changed, 1 insertion(+), 5 deletions(-)
diff --git a/drivers/usb/host/xhci-pci.c b/drivers/usb/host/xhci-pci.c
index
From: Alexander Stein
This allows someone to grep for the complete warning message as in;
xhci-hcd xhci-hcd.0.auto: USB core suspending device not in U0/U1/U2.
Signed-off-by: Alexander Stein
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci-hub.c | 3 +--
1 file changed, 1 insertion(+),
From: Lu Baolu
No need to calculate remainder and length_field, if there is
no data phase of a control transfer.
Signed-off-by: Lu Baolu
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci-ring.c | 20 ++--
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/dri
We don't want to confuse halted and stalled endpoint states with
a flag indicating we are waiting for a stop endpoint command to
finish or timeout
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci-ring.c | 6 +++---
drivers/usb/host/xhci.c | 6 +++---
drivers/usb/host/xhci.h | 2 +
From: Lu Baolu
Drop an unnecessary assignment in prepare_transfer().
Signed-off-by: Lu Baolu
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci-ring.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/usb/host/xhci-ring.c b/drivers/usb/host/xhci-ring.c
index bcc0894..61b5fea 10
From: Felipe Balbi
By extracting xhci_td_cleanup() from finish_td(), code before clearer
and easier to follow.
There are no functional changes with this patch. It's merely a cleanup.
Signed-off-by: Felipe Balbi
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci-ring.c | 92 ++
From: Felipe Balbi
Some devices from Texas Instruments [1] suffer from
a silicon bug where Port Enabled/Disabled bit
should not be used to silence an erroneous device.
The bug is so that if port is disabled with PED
bit, an IRQ for device removal (or attachment)
will never fire.
Just for the sa
From: Felipe Balbi
xhci_unmap_td_bounce_buffer() already checks for a valid td->bounce_seg
and bails out early if that's invalid. There's no need to check for this
twice.
Signed-off-by: Felipe Balbi
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci-ring.c | 9 +++--
1 file changed, 3
From: Lu Baolu
Use list_is_singular() to check if cmd_list has only one entry.
[use list_empty() in queue command instead -Mathias]
Signed-off-by: Lu Baolu
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci-ring.c | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/
No functional change, De Morgan !(A && B) = (!A || !B)
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci-ring.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/usb/host/xhci-ring.c b/drivers/usb/host/xhci-ring.c
index e32029a..46df89e 100644
--- a/drivers/usb/h
On 01/13/2017 05:12 PM, Patrice Chotard wrote:
> On 01/12/2017 06:17 PM, Mathias Nyman wrote:
>> On 09.01.2017 18:42, Mathias Nyman wrote:
>>> On 09.01.2017 16:23, Patrice Chotard wrote:
On 01/09/2017 01:30 PM, Mathias Nyman wrote:
>
> On 09.01.2017 11:51, Patrice Chotard wrote:
>>
From: Baolin Wang
Since the 'addr_64' variable as legacy is unused now, then remove it from
xhci_hcd structure.
Signed-off-by: Baolin Wang
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/usb/host/xhci.h b/drivers/usb/host/xhc
From: Lu Baolu
The second try was a workaround for (what we thought was) command
ring failing to stop in the first place. But this turns out to be
due to the race that we have fixed(see "xhci: Fix race related to
abort operation"). With that fix, it is time to remove the second
try.
Signed-off-b
Checking if the command timeout timer is pending when queueing the
first command to the command ring is not really useful, remove it.
Suggested-by: Lu Baolu
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci-ring.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/driver
From: Felipe Balbi
Instead of having several return points, let's use a local variable and
a single place to return. This makes the code slightly easier to read.
[set ret = IRQ_HANDLED in default working case -Mathias]
Signed-off-by: Felipe Balbi
Signed-off-by: Mathias Nyman
---
drivers/usb/
From: Felipe Balbi
instead of using while(!list_empty()) followed by list_first_entry(), we
can actually use list_for_each_entry_safe().
Signed-off-by: Felipe Balbi
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci-ring.c | 15 ---
1 file changed, 8 insertions(+), 7 deletions
From: Felipe Balbi
This is a cleanup patch only, no functional changes. The idea is just to
make sure for loops look the same all over the driver.
Signed-off-by: Felipe Balbi
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci-dbg.c | 20 ++--
drivers/usb/host/xhci-mem.c |
From: Felipe Balbi
Cleanup only. This patch is a mechaninal rename to make sure our macros
for TRB completion codes match what the specification uses to refer to
such errors. The idea behind this is that it makes it far easier to grep
the specification and match it with implementation.
Signed-of
From: Felipe Balbi
instead of having a tracer that can only trace command completions,
let's promote this tracer so it can trace and decode any TRB.
With that, it will be easier to extrapolate the lifetime of any TRB
which might help debugging certain issues.
Signed-off-by: Felipe Balbi
Signed
From: Felipe Balbi
it does no good, let's remove it.
Signed-off-by: Felipe Balbi
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci-ext-caps.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/host/xhci-ext-caps.h b/drivers/usb/host/xhci-ext-caps.h
index e024
From: Felipe Balbi
These three new tracers will help us tie TRBs into URBs by *also*
looking into URB lifetime.
Signed-off-by: Felipe Balbi
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci-ring.c | 1 +
drivers/usb/host/xhci-trace.h | 70 +++
dr
On 20/01/17 12:10, Felipe Balbi wrote:
>>> And unfortunately, whether this is set or not is not visible to the
>>> software so it will require a quirk.
>>
>> but arrived at this conclusion because I couldn't think of a reasonable
>> guess value for IN/OUT endpoint numbers that would work if
>> DWC_
On Thu, Jan 19, 2017 at 4:56 PM, Florian Fainelli
wrote:
> On 01/19/2017 02:36 PM, Scott Branden wrote:
> The driver stands alone from the SoC and does not need compatibility
> strings per SoC. New SoCs will use the exact same block.
Even if you take the exact same block and put
le.
>
100% reproducible on Intel Edison
BEFORE
# uname -a
Linux buildroot 4.10.0-rc4-next-20170120+ #245 SMP Fri Jan 20 15:49:08
EET 2017 x86_64 GNU/Linux
# dmesg | grep WARN
[ 19.25] WARNING: CPU: 0 PID: 1 at
/home/andy/prj/linux-topic-mfld/drivers/usb/host/xhci-plat.c:168
xhci_pla
t_p
Hi Greg
Here's the patch that removes the scary WARN_ON in 4.10 xhci platform
driver
-Mathias
Mathias Nyman (1):
xhci: remove WARN_ON if dma mask is not set for platform devices
drivers/usb/host/xhci-plat.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
1.9.1
--
To unsubscribe f
The warn on is a bit too much, we will anyway set the dma mask if not set
previously.
The main reason for this fix is that 4.10-rc1 has a dwc3 change that
pass a parent sysdev dev pointer instead of setting the dma mask of
its xhci platform device. xhci platform driver can then get more
attribute
Hi,
Greg KH writes:
>> >> > > > > This series by Arnd Bergmann was originally six patches, but last
>> >> > > > > two of
>> >> > > > > them were already taken to 4.10. Without the rest of them there
>> >> > > > > will
>> >> > > > > be a regression in 4.10.
>> >> > > >
>> >> > > > Is it really
On Fri, Jan 20, 2017 at 02:08:50PM +0200, Felipe Balbi wrote:
>
> Hi,
>
> Greg KH writes:
> > On Fri, Jan 20, 2017 at 01:35:39PM +0200, Mathias Nyman wrote:
> >> On 20.01.2017 12:22, Greg KH wrote:
> >> > On Fri, Jan 20, 2017 at 11:23:36AM +0200, Mathias Nyman wrote:
> >> > > On 19.01.2017 20:48
Hi,
Bryan O'Donoghue writes:
> On 19/01/17 22:49, John Youn wrote:
>
>> So it is valid to have say, DWC_USB3_NUM_EPS=8 and
>> DWC_USB3_NUM_IN_EPS=8. Even though it is not possible to use all 8 EPs
>> as IN since you need at least one of them to be a control OUT. So you
>> could have a configurat
Hi,
Greg KH writes:
> On Fri, Jan 20, 2017 at 01:35:39PM +0200, Mathias Nyman wrote:
>> On 20.01.2017 12:22, Greg KH wrote:
>> > On Fri, Jan 20, 2017 at 11:23:36AM +0200, Mathias Nyman wrote:
>> > > On 19.01.2017 20:48, Greg KH wrote:
>> > > > On Thu, Jan 19, 2017 at 02:21:26PM +0200, Mathias Ny
Hi Rob,
On Thu, Jan 19, 2017 at 11:06 PM, Rob Herring wrote:
> On Tue, Jan 17, 2017 at 01:35:07PM +0530, Raviteja Garimella wrote:
>> This patch adds device tree bindings documentation for Synopsys
>> USB device controller platform driver.
>
> Bindings describe h/w, not drivers.
Will correct th
On Fri, Jan 20, 2017 at 01:35:39PM +0200, Mathias Nyman wrote:
> On 20.01.2017 12:22, Greg KH wrote:
> > On Fri, Jan 20, 2017 at 11:23:36AM +0200, Mathias Nyman wrote:
> > > On 19.01.2017 20:48, Greg KH wrote:
> > > > On Thu, Jan 19, 2017 at 02:21:26PM +0200, Mathias Nyman wrote:
> > > > > Hi Greg
On 01/20/2017 02:00 PM, Roger Quadros wrote:
Vivek,
On 19/01/17 17:15, vivek.gau...@codeaurora.org wrote:
Hi Roger,
On 2017-01-19 17:45, Roger Quadros wrote:
Vivek,
On 19/01/17 13:56, Vivek Gautam wrote:
Hi,
On Wed, Jun 22, 2016 at 2:00 PM, Roger Quadros wrote:
Luckily hit this thread
On 20.01.2017 12:22, Greg KH wrote:
On Fri, Jan 20, 2017 at 11:23:36AM +0200, Mathias Nyman wrote:
On 19.01.2017 20:48, Greg KH wrote:
On Thu, Jan 19, 2017 at 02:21:26PM +0200, Mathias Nyman wrote:
Hi Greg
This series by Arnd Bergmann was originally six patches, but last two of
them were alre
On Fri, Jan 20, 2017 at 11:23:36AM +0200, Mathias Nyman wrote:
> On 19.01.2017 20:48, Greg KH wrote:
> > On Thu, Jan 19, 2017 at 02:21:26PM +0200, Mathias Nyman wrote:
> > > Hi Greg
> > >
> > > This series by Arnd Bergmann was originally six patches, but last two of
> > > them were already taken t
On Fri, Jan 20, 2017 at 8:52 AM, Peter Chen wrote:
> On Tue, Jan 10, 2017 at 03:02:41PM +0800, Peter Chen wrote:
>> On Sat, Jan 07, 2017 at 10:54:56AM +0200, Krzysztof Kozlowski wrote:
>> > On Thu, Jan 05, 2017 at 02:01:53PM +0800, Peter Chen wrote:
>> > > We have an well-known problem that the de
On 01/20/2017 10:24 AM, Sekhar Nori wrote:
> On Thursday 19 January 2017 11:01 PM, Alexandre Bailon wrote:
>> On 01/19/2017 05:49 PM, Grygorii Strashko wrote:
>>> On 01/19/2017 09:08 AM, Alexandre Bailon wrote:
On 01/19/2017 03:48 PM, Sekhar Nori wrote:
> On Thursday 19 January 2017 07:39
On 19/01/17 22:49, John Youn wrote:
> So it is valid to have say, DWC_USB3_NUM_EPS=8 and
> DWC_USB3_NUM_IN_EPS=8. Even though it is not possible to use all 8 EPs
> as IN since you need at least one of them to be a control OUT. So you
> could have a configuration of EP0 IN and OUT plus 6 IN EPs (to
On Thursday 19 January 2017 11:01 PM, Alexandre Bailon wrote:
> On 01/19/2017 05:49 PM, Grygorii Strashko wrote:
>> On 01/19/2017 09:08 AM, Alexandre Bailon wrote:
>>> On 01/19/2017 03:48 PM, Sekhar Nori wrote:
On Thursday 19 January 2017 07:39 PM, Alexandre Bailon wrote:
> Add usb20 to th
On 19.01.2017 20:48, Greg KH wrote:
On Thu, Jan 19, 2017 at 02:21:26PM +0200, Mathias Nyman wrote:
Hi Greg
This series by Arnd Bergmann was originally six patches, but last two of
them were already taken to 4.10. Without the rest of them there will
be a regression in 4.10.
Is it really a regr
Vivek,
On 19/01/17 17:15, vivek.gau...@codeaurora.org wrote:
> Hi Roger,
>
> On 2017-01-19 17:45, Roger Quadros wrote:
>> Vivek,
>>
>> On 19/01/17 13:56, Vivek Gautam wrote:
>>> Hi,
>>>
>>>
>>> On Wed, Jun 22, 2016 at 2:00 PM, Roger Quadros wrote:
>>>
>>> Luckily hit this thread while checking a
On Fri, Jan 20, 2017 at 07:59:48AM +, Anurag Kumar Vulisha wrote:
> Hi,
Hi!
Minor nit, vger.kernel.org rejects html emails, so this didn't make it
through to that list. Now it should with my response :)
> I have a usecase where I want to stream a stereo video from the ZED Stereo
> Camera (
split the old SuperSpeed port node into a HighSpeed one and a new
SuperSpeed one.
Signed-off-by: Chunfeng Yun
---
arch/arm64/boot/dts/mediatek/mt8173.dtsi | 19 +--
1 file changed, 13 insertions(+), 6 deletions(-)
diff --git a/arch/arm64/boot/dts/mediatek/mt8173.dtsi
b/arch/a
the reference clock of HighSpeed port is 48M which comes from PLL;
the reference clock of SuperSpeed port is 26M which usually comes
from 26M oscillator directly, but some SoCs are not, add it for
compatibility, and put them into port node for flexibility.
Signed-off-by: Chunfeng Yun
---
drivers
1 - 100 of 105 matches
Mail list logo
