Hi,
Mason writes:
> Hello everyone,
>
> I'm working on a SoC which embeds an IP block from GDA Technologies
> labeled "Pravega USB3 SuperSpeed Controller" (data-sheet is v0.99r
> dated 2014-01-29). A cursory search returns:
>
> http://www.sourcing.co.jp/prod_ip.htm
> http://www.sourcing.co.jp/pr
Hi Felipe,
On Tue, Apr 19, 2016 at 02:10:45PM +0300, Heikki Krogerus wrote:
> This should allow xhci to remove handling of platform data.
>
> Signed-off-by: Heikki Krogerus
> Cc: Felipe Balbi
Is this OK now?
> ---
> drivers/usb/dwc3/host.c | 18 +-
> 1 file changed, 9 inserti
Hi,
Heikki Krogerus writes:
> Hi Felipe,
>
> On Tue, Apr 19, 2016 at 02:10:45PM +0300, Heikki Krogerus wrote:
>> This should allow xhci to remove handling of platform data.
>>
>> Signed-off-by: Heikki Krogerus
>> Cc: Felipe Balbi
>
> Is this OK now?
yeah, it should be in testing/next already
Hi Baolu,
On Mon, May 30, 2016 at 01:51:44PM +0800, Lu Baolu wrote:
> Add a maintainer entry for Intel USB dual role mux drivers and
> add myself as a maintainer.
>
> Signed-off-by: Lu Baolu
> ---
> MAINTAINERS | 10 ++
> 1 file changed, 10 insertions(+)
>
> diff --git a/MAINTAINERS b/
On Mon, May 30, 2016 at 11:12:40AM +0300, Felipe Balbi wrote:
>
> Hi,
>
> Heikki Krogerus writes:
> > Hi Felipe,
> >
> > On Tue, Apr 19, 2016 at 02:10:45PM +0300, Heikki Krogerus wrote:
> >> This should allow xhci to remove handling of platform data.
> >>
> >> Signed-off-by: Heikki Krogerus
>
Hello Felipe,
On 30/05/2016 08:58, Felipe Balbi wrote:
> Mason writes:
>
>> I'm working on a SoC which embeds an IP block from GDA Technologies
>> labeled "Pravega USB3 SuperSpeed Controller" (data-sheet is v0.99r
>> dated 2014-01-29). A cursory search returns:
>>
>> http://www.sourcing.co.jp/pr
On 30.05.2016 11:31, Mason wrote:
Hello Felipe,
On 30/05/2016 08:58, Felipe Balbi wrote:
Mason writes:
I'm working on a SoC which embeds an IP block from GDA Technologies
labeled "Pravega USB3 SuperSpeed Controller" (data-sheet is v0.99r
dated 2014-01-29). A cursory search returns:
http://w
On Fri, May 13, 2016 at 01:03:14PM +0300, Roger Quadros wrote:
> Hi,
>
> This series centralizes OTG/Dual-role functionality in the kernel.
> As of now I've got Dual-role functionality working pretty reliably on
> dra7-evm and am437x-gp-evm.
> NOTE: my am437x-gp-evm broke so I couldn't test v8 on
Hi,
Mason writes:
> Hello Felipe,
>
> On 30/05/2016 08:58, Felipe Balbi wrote:
>
>> Mason writes:
>>
>>> I'm working on a SoC which embeds an IP block from GDA Technologies
>>> labeled "Pravega USB3 SuperSpeed Controller" (data-sheet is v0.99r
>>> dated 2014-01-29). A cursory search returns:
>>
Hi,
Heikki Krogerus writes:
> On Mon, May 30, 2016 at 11:12:40AM +0300, Felipe Balbi wrote:
>>
>> Hi,
>>
>> Heikki Krogerus writes:
>> > Hi Felipe,
>> >
>> > On Tue, Apr 19, 2016 at 02:10:45PM +0300, Heikki Krogerus wrote:
>> >> This should allow xhci to remove handling of platform data.
>> >
Hi,
Am Freitag, den 27.05.2016, 09:06 +0200 schrieb Hans de Goede:
[...]
> >> So IMHO the following change would be a better way to fix this:
> >>
> >> --- a/include/linux/reset.h
> >> +++ b/include/linux/reset.h
> >> @@ -65,14 +65,14 @@ static inline struct reset_control
> >> *__of_reset_control
Hi,
On 30-05-16 12:18, Philipp Zabel wrote:
Hi,
Am Freitag, den 27.05.2016, 09:06 +0200 schrieb Hans de Goede:
[...]
So IMHO the following change would be a better way to fix this:
--- a/include/linux/reset.h
+++ b/include/linux/reset.h
@@ -65,14 +65,14 @@ static inline struct reset_control *
valid range for storage buffers is encoded in
Kconfig already. Instead of checking again, let's
drop fsg_num_buffers_validate() altogether.
Signed-off-by: Felipe Balbi
---
drivers/usb/gadget/function/f_mass_storage.c | 22 +-
1 file changed, 1 insertion(+), 21 deletions(-)
d
Hi folks,
I've lost track of which patches had already been sent on linux-usb (sorry), so
I'll just go ahead and send everything that I have on testing/next today rebased
on v4.7-rc1.
Please go through dwc3's changes (for those of you using dwc3) as there's a ton
of important stuff happening with
Instead of returning -EINVAL when someone calls
__dwc3_gadget_wakeup() in speeds > highspeed, let's
return 0. There are no problems for the driver for
calling it in superspeed as we cleanly just return.
This avoids an annoying WARN_ONCE() always
triggering during superspeed enumeration with LPM
en
now that we have re-factored dwc3_core_init() and
dwc3_core_exit() we can use them for suspend/resume
operations.
This will help us avoid some common mistakes when
patching code when we have duplicated pieces of code
doing the same thing.
Signed-off-by: Felipe Balbi
---
drivers/usb/dwc3/core.c
as it turns out, we don't need the extra 'start_new'
argument as that can be inferred from DWC3_EP_BUSY
flag.
Because of that, we can simplify
__dwc3_gadget_kick_transfer() by quite a bit, even
allowing us to prepare more TRBs unconditionally.
Signed-off-by: Felipe Balbi
---
drivers/usb/dwc3/ga
When we send an endpoint command, we want that to
complete as soon as possible, so let's remove the
unnecessary udelay(1) call.
Signed-off-by: Felipe Balbi
---
drivers/usb/dwc3/gadget.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/usb/dwc3/gadget.c b/drivers/usb/dwc3/gadget.c
ind
that macro is unnecessary and just adds pointless
obfuscation. Let's remove it.
Signed-off-by: Felipe Balbi
---
drivers/usb/dwc3/core.c | 8 ++--
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git a/drivers/usb/dwc3/core.c b/drivers/usb/dwc3/core.c
index a590cd225bb7..245f4ff6ae16 1
In all call sites of dwc3_send_gadget_ep_cmd() we
already had a valid dep pointer, so instead of
passing dwc and dep->number, which would be used to
fetch the same pointer we already had, just pass dep
directly.
In other words, we're changing:
struct dwc3_ep *dep = dwc[dep->number];
to j
sg_is_last() and list_is_last() will encode the
required information for the driver to make
decisions WRT CHN and LST bits.
While at that, also replace '1' with 'true' for
consistency.
Signed-off-by: Felipe Balbi
---
drivers/usb/dwc3/gadget.c | 10 +-
1 file changed, 5 insertions(+), 5
Instead of using burst size to configure NUMP, we
should be using RxFIFO Size instead. DWC3 is smart
enough to know that it shouldn't burst in case burst
size is 0.
Reported-by: John Youn
Signed-off-by: Felipe Balbi
---
drivers/usb/dwc3/core.h | 12 +++
drivers/usb/dwc3/gadget.c | 54
this patch implements the most basic pm_runtime
support for dwc3. Whenever USB cable is dettached,
then we will allow core to runtime_suspend.
Runtime suspending will involve completely tearing
down event buffers and require a full soft-reset of
the IP.
Note that a further optimization could be
i
by holding gadget's IRQ number in dwc->irq_gadget,
it'll be simpler to free_irq() and disable the IRQ
in case an IRQ fires while we are runtime suspended.
Signed-off-by: Felipe Balbi
---
drivers/usb/dwc3/core.h | 2 ++
drivers/usb/dwc3/gadget.c | 5 ++---
2 files changed, 4 insertions(+), 3 de
From: Tim Harvey
The PLX USB2380 is a PCIe version of the NET2280 and behaves more like the
USB338x but without the USB3.0 superspeed support.
This was tested with g_ether, g_serial, g_mass_storage on a Gateworks
Ventana GW2383.
Cc: Justin DeFields
Signed-off-by: Tim Harvey
Signed-off-by: Fel
we will be re-using it for suspend/resume, so
instead of duplicating code, let's just re-factor
the functions so they can be re-used.
Signed-off-by: Felipe Balbi
---
drivers/usb/dwc3/gadget.c | 90 ++-
1 file changed, 49 insertions(+), 41 deletions(-)
If we're updating transfers, we can also prepare as
many TRBs as we can fit in the ring. Let's start
doing that.
This patch 'solves' a limitation of how many TRBs we
can prepare when we're getting close the end of the
ring. Instead driver to prepare only up to end of
the ring, we check if we have
As a micro-power optimization, let's only resume the
USB2 PHY if we're working on <=HIGHSPEED. If we're
gonna work on SUPERSPEED or SUPERSPEED+, there's no
point in resuming the USB2 PHY.
Fixes: 2b0f11df84bb ("usb: dwc3: gadget: clear SUSPHY bit before ep cmds")
Signed-off-by: Felipe Balbi
---
d
To aid code readability, we're gonna split
__dwc3_gadget_kick_transfer() into its constituent
parts: scatter gather and linear buffers.
That way, it's easier to follow the code and focus
debug effort when one or the other fails.
Signed-off-by: Felipe Balbi
---
drivers/usb/dwc3/gadget.c | 122 ++
By adding a pointer to endpoint registers' base
address, we can avoid using our controller-wide
struct dwc3 pointer for everything. At some point
this will allow us to have per-endpoint locks which
will, in turn, let us queue requests to separate
endpoints in parallel.
Because of this change our d
With a default size of 16kiB and with maximum of 32
buffers, we can transfer up to 512kiB, however Linux
can transfer up to 1MiB in a single mass storage
block transfer to USB3 storage devices.
Because of this, 1MiB block transfers end up being
slower than 512kiB block transfers. Let's increase
ma
Instead of trying hard to stay connected to the
host, it's best (and far easier) to disconnect from
the host already.
Anything relying on KEEP_CONNECT will just have that
ignored, but we don't have proper hibernation
implementation yet, so there are no regressions.
In any case, hibernation is onl
From: Konrad Leszczynski
commit f3af36511e60 ("usb: dwc3: gadget: always
enable IOC on bulk/interrupt transfers") ended up
regressing Isochronous endpoints by clearing
DWC3_EP_BUSY flag too early, which resulted in
choppy audio playback over USB.
Fix that by partially reverting original commit a
From: John Youn
The TRBs left calculation didn't account for the link TRB taking up one
spot.
If the trb_dequeue < trb_enqueue, then the result includes the link
TRB slot so it must be adjusted.
Signed-off-by: John Youn
Signed-off-by: Felipe Balbi
---
drivers/usb/dwc3/gadget.c | 3 +++
1 fil
Instead of printing command's status with a separate
trace printout, let's print it within a single call.
Signed-off-by: Felipe Balbi
---
drivers/usb/dwc3/debug.h | 16
drivers/usb/dwc3/gadget.c | 8 +---
drivers/usb/dwc3/trace.h | 15 +--
3 files changed, 30
From: John Youn
If the trb->enqueue == trb->dequeue, then it could be full or empty.
This could also happen at TRB index 0, so modify the check to handle
that condition. At index 0, the previous TRB is the one just before the
link TRB.
Signed-off-by: John Youn
Signed-off-by: Felipe Balbi
---
From: John Youn
Cleans up the sparse warning:
warning: dubious: x | !y
Since we do want a bitwise OR here, don't use a logical (true/false)
value. Probably is not a real issue but it cleans up the warning.
Signed-off-by: John Youn
Signed-off-by: Felipe Balbi
---
drivers/usb/dwc3/gadget.c | 2
This will allow us to process several endpoints at a
time by making sure that we lock only shared
resources.
Signed-off-by: Felipe Balbi
---
drivers/usb/dwc3/core.h | 2 ++
drivers/usb/dwc3/gadget.c | 1 +
2 files changed, 3 insertions(+)
diff --git a/drivers/usb/dwc3/core.h b/drivers/usb/dwc
Allow for dwc3-pci to reach D3 and enable pm_runtime
by providing dummy PM hooks. Without them, PCI
subsystem won't put device to D3.
Signed-off-by: Felipe Balbi
---
drivers/usb/dwc3/dwc3-pci.c | 30 ++
1 file changed, 30 insertions(+)
diff --git a/drivers/usb/dwc3/d
We want commands to finish ASAP, so let's remove
that udelay() call.
Signed-off-by: Felipe Balbi
---
drivers/usb/dwc3/gadget.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/usb/dwc3/gadget.c b/drivers/usb/dwc3/gadget.c
index f384ad379234..5cec5811169a 100644
--- a/drivers/usb/dwc3
From: John Youn
Sparse complains even though it looks ok. Probably it cannot detect that
the wValue, wIndex, and wLength are declared __le16 due to the macro
magic.
Redeclare them as CPU endianness and make the conversion on assignment.
Signed-off-by: John Youn
Signed-off-by: Felipe Balbi
---
From: John Youn
If trbs_left == 0, we don't have any space left in the TRB ring so don't
prepare anything.
Signed-off-by: John Youn
Signed-off-by: Felipe Balbi
---
drivers/usb/dwc3/gadget.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/usb/dwc3/gadget.c b/drivers/usb/dwc3/gadg
From: John Youn
The DWC3_USB31_REVISION_110A macro uses an invalid constant name in its
definition. This is currently not used.
Signed-off-by: John Youn
Signed-off-by: Felipe Balbi
---
drivers/usb/dwc3/core.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/dwc3
We don't need the extra %s when command fails.
Let's remove it
Signed-off-by: Felipe Balbi
---
drivers/usb/dwc3/gadget.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/usb/dwc3/gadget.c b/drivers/usb/dwc3/gadget.c
index 770664c9c83e..efb758e5c6c7 100644
--- a/dri
From: William Wu
GUCTL1 reg has some useful functions which can be
written by user. For rockchip platform, we set
GUCTL1.DEV_FORCE_20_CLK_FOR_30_CLK (bit26, applicable
for the core is programmed to operate in 2.0 device
only) to 1 in bootrom, and after start the kernel,
we want to check whether t
I really thought this would be useful, but as it
turns out, it creates more problems than fixes. The
amount of times we had to fix this because some
other commit shuffled things around and ended up
regressing this tiny little string manupulation...
Might as well remove it, since it has a negligibl
From: John Youn
The current calculation takes dep->trb_dequeue - dep->trb_enqueue to
find the TRB space left.
If you enqueue 1, that results in:
(u8) 0 - (u8) 1 = 0xff = 255 TRBs left.
This is correct if DWC3_TRB_NUM == 256.
If DWC3_TRB_NUM is less than 256 (but still a power of 2) you need to
From: John Youn
Correct the use of the DWC3_DSTS_XXX_SPEED and DWC3_DCFG_XXX_SPEED
macros. The wrong set of macros were being used in a few places.
This is only a cosmetic change as the values for both sets are
identical.
Signed-off-by: John Youn
Signed-off-by: Felipe Balbi
---
drivers/usb/d
this patch is in preparation for some further
re-factoring in dwc3 initialization. No functional
changes.
Signed-off-by: Felipe Balbi
---
drivers/usb/dwc3/core.c | 16 +++-
drivers/usb/dwc3/core.h | 2 ++
2 files changed, 9 insertions(+), 9 deletions(-)
diff --git a/drivers/usb/dwc
when we call dwc3_gadget_giveback(), we end up
releasing our controller's lock. Another thread
could get scheduled and disable the endpoint,
subsequently setting dep->endpoint.desc to NULL.
In that case, we would end up dereferencing a NULL
pointer which would result in a Kernel Oops. Let's
avoid
From: John Youn
u2sel and u2pel should be __le16. Doesn't fix any issue.
Found with sparse.
Signed-off-by: John Youn
Signed-off-by: Felipe Balbi
---
drivers/usb/dwc3/ep0.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/usb/dwc3/ep0.c b/drivers/usb/dwc3/ep0.c
The idea of this patch is for dwc3_core_init() to
abstract all the details about how to initialize
dwc3 and dwc3_core_exit() to do the same for
teardown.
With this, we can simplify suspend/resume operations
by a large margin and always know that we're going
to start dwc3 from a known starting poin
instead of having infinite loop and always checking
timeout value as a break condition, we can just
decrement timeout inside while's condition.
Signed-off-by: Felipe Balbi
---
drivers/usb/dwc3/gadget.c | 18 ++
1 file changed, 6 insertions(+), 12 deletions(-)
diff --git a/driver
From: John Youn
Clears out all the TRBs in the ring to clean up any stale data that
might be in them from the previous time the endpoint was enabled.
Also removed the existing clear of the LINK trb since the entire ring is
cleard just before.
Signed-off-by: John Youn
Signed-off-by: Felipe Balb
Just like we did for endpoint commands, let's have a
single trace output for the command and its
status. This will improve trace readability
Signed-off-by: Felipe Balbi
---
drivers/usb/dwc3/debug.h | 14 ++
drivers/usb/dwc3/gadget.c | 14 ++
drivers/usb/dwc3/trace.h | 1
From: John Youn
The wIndex passed in here is CPU endianness, but the function expects
little endian.
Found with sparse.
Signed-off-by: John Youn
Signed-off-by: Felipe Balbi
---
drivers/usb/dwc3/ep0.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/dwc3/ep0.c b
From: John Youn
Make the skipping of the link TRBS built-in to the increment operation.
This simplifies the code wherever we increment the trb index and ensures
that we never end up pointing to a link trb.
Signed-off-by: John Youn
Signed-off-by: Felipe Balbi
---
drivers/usb/dwc3/gadget.c | 34
This will make it more human-friendly to read trace
output from dwc3.
Signed-off-by: Felipe Balbi
---
drivers/usb/dwc3/debug.h | 110 +--
drivers/usb/dwc3/ep0.c | 7 +--
drivers/usb/dwc3/trace.h | 3 +-
3 files changed, 92 insertions(+), 28 delet
Just like we did for endpoint commands, let's use a
single return point for generic commands as
well. This aids readability.
Signed-off-by: Felipe Balbi
---
drivers/usb/dwc3/gadget.c | 25 -
1 file changed, 12 insertions(+), 13 deletions(-)
diff --git a/drivers/usb/dwc3/
From: Janusz Dziedzic
Improve trb tracing by showing trb flags, interrupts
trb type.
trb flags:
- h - hardware owner of descriptor
- l - last TRB
- c - chain buffers
- s - continue on short packet
interrupt flags:
- s - interrupt on short packet
- c - interrupt on complete
Capital letter means
From: John Youn
>From sparse:
warning: cast truncates bits from constant value (100 becomes 0)
The DWC3_TRB_NUM constant is too big for u8. Do the calculation a
slightly different way that should still be optimized out for the case
where DWC3_TRB_NUM == 256.
Signed-off-by: John Youn
Signed-off
If we don't, we will overwrite valid TRBs.
Signed-off-by: Felipe Balbi
---
drivers/usb/dwc3/gadget.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/dwc3/gadget.c b/drivers/usb/dwc3/gadget.c
index c42786ff4752..3d0745dece0c 100644
--- a/drivers/usb/dwc3/gadget.c
+
Now we can try to issue Update Transfer every time
gadget driver queues a new request. This will make
sure we keep controller's queue busy for as long as
possible.
Signed-off-by: Felipe Balbi
---
drivers/usb/dwc3/gadget.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/driv
Instead of relying on empty list of queued requests,
let's rely on the number of incomplete requests
actually in traffic.
Signed-off-by: Felipe Balbi
---
drivers/usb/dwc3/gadget.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/usb/dwc3/gadget.c b/drivers/usb/dwc3
According to SNPS databook, we need to pass transfer
resource on update transfer command, let's do it.
Signed-off-by: Felipe Balbi
---
drivers/usb/dwc3/gadget.c | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/drivers/usb/dwc3/gadget.c b/drivers/usb/dwc3/gadget.c
index
We will be using this information to change how we
figure out when we need LST bit. For now, just
update our counters.
Signed-off-by: Felipe Balbi
---
drivers/usb/dwc3/core.h | 4
drivers/usb/dwc3/gadget.c | 7 +++
drivers/usb/dwc3/trace.h | 9 +++--
3 files changed, 18 insertion
From: Roger Quadros
On OMAPs, OTG events come on the same IRQ so we need to share
this IRQ with the OTG device driver.
Signed-off-by: Roger Quadros
Signed-off-by: Felipe Balbi
---
drivers/usb/dwc3/dwc3-omap.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/dwc3
From: Heikki Krogerus
No more users for it.
Tested-by: John Youn
Signed-off-by: Heikki Krogerus
Signed-off-by: Felipe Balbi
---
drivers/usb/dwc3/core.c | 35 --
drivers/usb/dwc3/platform_data.h | 53
2 files changed, 8
From: Heikki Krogerus
This should allow the core driver to drop handling of
platform data and expect the platform specific details to
always come from properties.
Tested-by: John Youn
Signed-off-by: Heikki Krogerus
Cc: Huang Rui
CC: John Youn
Signed-off-by: Felipe Balbi
---
drivers/usb/dwc
Let's only set LST bit when we run out of space in
our TRB ring. For all other cases, we keep LST bit
unset which will prevent constant allocation and
deallocation of endpoint transfer resources.
Signed-off-by: Felipe Balbi
---
drivers/usb/dwc3/gadget.c | 20 ++--
1 file changed,
We don't need this IRQ anymore.
Signed-off-by: Felipe Balbi
---
drivers/usb/dwc3/gadget.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/drivers/usb/dwc3/gadget.c b/drivers/usb/dwc3/gadget.c
index 7a0c787cecdd..613dde9fb538 100644
--- a/drivers/usb/dwc3/gadget.c
+++ b/
From: Roger Quadros
TRM [1] recommends that POWERPRESENT bit must not be
set and left at it's default value of 0.
[1] OMAP542x TRM - http://www.ti.com/lit/pdf/swpu249
Section 23.11.4.5.1 Mailbox VBUS/ID Management
"Because PIPE powerpresent has a different meaning in host and in device mode,
an
when passing strings to trace, we don't need the
trailing newline character. Trace already appends a
newline character automatically.
Signed-off-by: Felipe Balbi
---
drivers/usb/dwc3/ep0.c| 4 ++--
drivers/usb/dwc3/gadget.c | 32
2 files changed, 14 insertio
From: Roger Quadros
Don't make any decisions regarding VBUS session based on ID
status. That is best left to the OTG core.
Pass ID and VBUS events independent of each other so that OTG
core knows exactly what to do.
This makes dual-role with extcon work with OTG irq on OMAP platforms.
Signed-o
From: Roger Quadros
We intend to share this interrupt with the OTG driver an to ensure
that irqflags match for the shared interrupt handlers we use
request_threaded_irq()
If we don't use request_treaded_irq() then forced threaded irq will
set IRQF_ONESHOT and this won't match with the OTG IRQ ha
Am Montag, den 30.05.2016, 13:32 +0200 schrieb Hans de Goede:
> Hi,
>
> On 30-05-16 12:18, Philipp Zabel wrote:
> > Hi,
> >
> > Am Freitag, den 27.05.2016, 09:06 +0200 schrieb Hans de Goede:
> > [...]
> So IMHO the following change would be a better way to fix this:
>
> --- a/includ
Hi Felipe,
On 30/05/16 14:35, Felipe Balbi wrote:
> this patch implements the most basic pm_runtime
> support for dwc3. Whenever USB cable is dettached,
> then we will allow core to runtime_suspend.
>
> Runtime suspending will involve completely tearing
> down event buffers and require a full sof
Hi,
Roger Quadros writes:
> On 30/05/16 14:35, Felipe Balbi wrote:
>> this patch implements the most basic pm_runtime
>> support for dwc3. Whenever USB cable is dettached,
>> then we will allow core to runtime_suspend.
>>
>> Runtime suspending will involve completely tearing
>> down event buffe
Hi guys,
On Fri, May 27, 2016 at 07:06:41AM -0700, Guenter Roeck wrote:
> On 05/27/2016 12:55 AM, Heikki Krogerus wrote:
> > I'll merge this into any case to v3, and I'll send on Monday.
> >
> Sounds good.
>
> Couple of additional comments.
>
> I don't really know what to do with the 'desc' fie
Hi Heikki,
On 05/30/2016 04:16 PM, Heikki Krogerus wrote:
> Hi Baolu,
>
> On Mon, May 30, 2016 at 01:51:44PM +0800, Lu Baolu wrote:
>> Add a maintainer entry for Intel USB dual role mux drivers and
>> add myself as a maintainer.
>>
>> Signed-off-by: Lu Baolu
>> ---
>> MAINTAINERS | 10 ++
Hi guys,
I'm attaching a diff instead of full v3. I'm not yet adding attributes
for the reset and cable_reset. I still don't understand what is the
case where the userspace would need to be able to tricker reset? Why
isn't it enough for the userspace to be able to enter/exit modes?
Oliver! Can you
On 19 May 2016 at 15:42, Srinivas Kandagatla
wrote:
> Fixes 4bb3cad7125b ("usb: host: ehci-msm: Register usb shutdown function")
> Signed-off-by: Srinivas Kandagatla
Was seeing this crash while doing a reboot on db410c which is fixed
with this patch:
Tested-by: Pramod Gurav
--
To unsubscrib
On Mon, 2016-05-30 at 16:19 +0300, Heikki Krogerus wrote:
> Hi guys,
>
> I'm attaching a diff instead of full v3. I'm not yet adding attributes
> for the reset and cable_reset. I still don't understand what is the
> case where the userspace would need to be able to tricker reset? Why
> isn't it en
On 30/05/16 12:29, Peter Chen wrote:
> On Fri, May 13, 2016 at 01:03:14PM +0300, Roger Quadros wrote:
>> Hi,
>>
>> This series centralizes OTG/Dual-role functionality in the kernel.
>> As of now I've got Dual-role functionality working pretty reliably on
>> dra7-evm and am437x-gp-evm.
>> NOTE: my a
This is mostly cosmetic. usb_ep_disable(), which
will be called by ->reset(), should force transfers
to be stopped. We're just making sure it runs before
that.
Signed-off-by: Felipe Balbi
---
drivers/usb/dwc3/gadget.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/driv
Instead of looping through all endpoints when
enabling ep0, let's allow for each endpoint to set
its own xfer resource. This solves an issue which
happens when we issue END_TRANSFER due to a reset
interrupt. Endpoints will be left without a xfer
resource to use.
Signed-off-by: Felipe Balbi
---
d
On Sun, 29 May 2016, Marco Chiappero wrote:
> Hello,
>
> I'm experiencing a problem I'm not able to troubleshoot.
>
> I own a WD Elements Portable USB 3.0 HDD (WDBU6Y0020BBK) containing a
> drive model WD20NMVW-11AV3S3. When connected to a USB 3.0 port the drive
> works perfectly fine until I
On unplugging this USB Touchscreen, everytime I get either:
[ 161.596055] BUG: unable to handle kernel NULL pointer dereference at 0015
[ 161.596093] IP: [] get_next_timer_interrupt+0x80/0x270
or
[ 155.892061] BUG: unable to handle kernel paging request at 30303046
[ 155.892101] IP: [] get
On Fri, May 27, 2016 at 04:26:42PM +0300, Felipe Balbi wrote:
>> Sent. As a fix, there's a chance it could go into 4.7, right?
> yup, shouldn't be a problem. But only after v4.7-rc1 is tagged.
Seemingly v4.7-rc1 is out today (I was surprised at how quick that was).
/* Steinar */
--
Homepage: htt
parport subsystem has introduced parport_del_port() to delete a port
when it is going away. Without parport_del_port() the registered port
will not be unregistered.
To reproduce and verify the error:
Command to be used is : ls /sys/bus/parport/devices
1) without the device attached there is no outp
On Mon, 30 May 2016, Pierre Sauter wrote:
> On unplugging this USB Touchscreen, everytime I get either:
>
> [ 161.596055] BUG: unable to handle kernel NULL pointer dereference at
> 0015
> [ 161.596093] IP: [] get_next_timer_interrupt+0x80/0x270
> or
> [ 155.892061] BUG: unable to handle k
On Mon, May 30, 2016 at 09:02:54PM +0200, Marc Haber wrote:
> Hi,
>
> on my Bananapis, in kernel 4.6 USB does not work. Kernel configuration
> is USB-wise identical to 4.5 (grepped for differences in (hci|usb)),
> and in 4.6 there is not even /dev/bus/usb.
Hint, include linux-usb@vger in usb-spec
4.6-stable review patch. If anyone has any objections, please let me know.
--
From: John Stultz
commit cd9e2e5d3ff148be9ea210f622ce3e8e8292fcd6 upstream.
In testing with HiKey, we found that since
commit 3f30b158eba5 ("asix: On RX avoid creating bad Ethernet
frames"),
we're se
4.5-stable review patch. If anyone has any objections, please let me know.
--
From: John Stultz
commit cd9e2e5d3ff148be9ea210f622ce3e8e8292fcd6 upstream.
In testing with HiKey, we found that since
commit 3f30b158eba5 ("asix: On RX avoid creating bad Ethernet
frames"),
we're se
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: John Stultz
commit cd9e2e5d3ff148be9ea210f622ce3e8e8292fcd6 upstream.
In testing with HiKey, we found that since
commit 3f30b158eba5 ("asix: On RX avoid creating bad Ethernet
frames"),
we're se
On Sat, May 28, 2016 at 11:36:13AM +0800, Peter Chen wrote:
> On Tue, May 10, 2016 at 01:02:08PM +0200, Ulf Hansson wrote:
> > + Arnd
> >
> > [...]
> >
> > >> >> Solution
> > >> >>
> > >> >> This is very similar to the MMC pwrseq behavior so the idea is to:
> > >> >> 1. Move MMC pwrseq d
This driver is for Fintek F81532/F81534 USB to Serial Ports IC.
F81532 spec:
https://drive.google.com/file/d/0B8vRwwYO7aMFOTRRMmhWQVNvajQ/view?
usp=sharing
F81534 spec:
https://drive.google.com/file/d/0B8vRwwYO7aMFV29pQWJqbVBNc00/view?
usp=sharing
Features:
1. F81532 is 1-to-2 & F81534 is 1-to-4
Hi,
Ji-Ze Hong (Peter Hong) 於 2016/5/31 上午 09:33 寫道:
This driver is for Fintek F81532/F81534 USB to Serial Ports IC.
Sorry, I forgot to change the mail title for "PATCH V9". I'll resend a
patch with title "PATCH V9".
Thanks
--
With Best Regards,
Peter Hung
--
To unsubscribe from this list: s
This driver is for Fintek F81532/F81534 USB to Serial Ports IC.
F81532 spec:
https://drive.google.com/file/d/0B8vRwwYO7aMFOTRRMmhWQVNvajQ/view?
usp=sharing
F81534 spec:
https://drive.google.com/file/d/0B8vRwwYO7aMFV29pQWJqbVBNc00/view?
usp=sharing
Features:
1. F81532 is 1-to-2 & F81534 is 1-to-4
Is this the right mailing list for ttyACM device issues, or should I be
contactring the serial device people? Just in case this is the right place,
here's the issue.
I'm using Linux kernel 3.11.10-100.fc18.x86_64. I'm using termios, among other
things, to turn ICANON off and to set both VTIME a
1 - 100 of 112 matches
Mail list logo
