On Sun, Aug 07, 2016 at 06:55:36PM +0200, stéphane bryant wrote:
> Hi
>
> We are working on a project where a user-space application (a device
> emulator) creates a USB device on the host machine (thus allowing the
> emulated device to emulate a USB slave and to act as a usb dongle on the
> host m
Sorry, I just realized that in gmail `Default reply behaviour` was set
to `Reply` not `Reply All`, so I skipped the list when I replied
last(for I forgot to select Reply All as I did before). Oops. So now
hopefully everyone else can see the quoted previous email below.
On Mon, Aug 8, 2016 at 4:35
On Sun, 2016-08-07 at 23:37 +0200, Pavel Machek wrote:
> Hi!
>
> > > With these boards, you will not see anything on the screen that is
> > > attached to a Type-C connector until the OS has booted to the point
> > > where it has negotiated the power contract and entered a mode.
> > >
> > > If the
Add binding doc for generic power sequence library.
Signed-off-by: Peter Chen
Acked-by: Philipp Zabel
Acked-by: Rob Herring
---
.../bindings/power/pwrseq/pwrseq-generic.txt | 48 ++
1 file changed, 48 insertions(+)
create mode 100644
Documentation/devicetree/binding
Hi all,
This is a follow-up for my last power sequence framework patch set [1].
According to Rob Herring and Ulf Hansson's comments[2], I use a generic
power sequence library for parsing the power sequence elements on DT,
and implement generic power sequence on library. The host driver
can allocat
Some hard-wired USB devices need to do power sequence to let the
device work normally, the typical power sequence like: enable USB
PHY clock, toggle reset pin, etc. But current Linux USB driver
lacks of such code to do it, it may cause some hard-wired USB devices
works abnormal or can't be recogniz
We have an well-known problem that the device needs to do some power
sequence before it can be recognized by related host, the typical
example like hard-wired mmc devices and usb devices.
This power sequence is hard to be described at device tree and handled by
related host driver, so we have crea
Add optional properties for power sequence.
Signed-off-by: Peter Chen
Acked-by: Rob Herring
---
Documentation/devicetree/bindings/usb/usb-device.txt | 10 +-
1 file changed, 9 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/usb/usb-device.txt
b/Documentatio
From: Peter Chen
At device tree, we have no device node for chipidea core,
the glue layer's node is the parent node for host and udc
device. But in related driver, the parent device is chipidea
core. So, in order to let the common driver get parent's node,
we let the core's device node equals glu
The current dts describes USB HUB's property at USB controller's
entry, it is improper. The USB HUB should be the child node
under USB controller, and power sequence properties are under
it.
Signed-off-by: Peter Chen
---
arch/arm/boot/dts/imx6qdl-udoo.dtsi | 26 +-
1 file
On Sun, Jul 24, 2016 at 01:53:30PM +0200, Lubomir Rintel wrote:
> The device has three interfaces; the three serial ports ought to be
I assumed you meant "four interfaces" above and updated the commit
message before applying.
> handled by this driver:
>
> 00 Diagnostic interface serial port
> 01
On Thu, Jul 28, 2016 at 06:52:55PM +, Robert Deliën wrote:
> Ivium Technologies uses the FTDI VID with custom PIDs for their line of
> electrochemical interfaces and the PalmSens they developed for PalmSens BV.
>
> PIDs are kept in numerical order, entries in id_table_combined[] are at
> the s
On Thu, Jul 28, 2016 at 05:01:45PM -0400, Sheng-Hui J. Chu wrote:
> BCM20706V2_EVAL is a WICED dev board designed with FT2232H USB 2.0 UART/FIFO
> IC.
>
> To support BCM920706V2_EVAL dev board for WICED development on Linux. Add
> the VID(0a5c) and
> PID(6422) to ftdi_sio driver to allow loadi
On Tue, Aug 02, 2016 at 11:29:25AM +0200, Daniele Palmas wrote:
> This patch adds a set of compositions for Telit LE920A4.
>
> Compositions in short are:
>
> 0x1207: tty + tty
> 0x1208: tty + adb + tty + tty
> 0x1211: tty + adb + ecm
> 0x1212: tty + adb
> 0x1213: ecm + tty
> 0x1214: tty + adb + e
On Mon, Aug 08, 2016 at 02:34:46AM +0100, Alexey Klimov wrote:
> udriver struct allocated by kzalloc() will not be freed
> if usb_register() and next calls fail. This patch fixes this
> by adding one more step with kfree(udriver) in error path.
>
> Cc: Alan Stern
> Signed-off-by: Alexey Klimov
Some SATA to USB bridges fail to cooperate with some
drives resulting in no cache being present being reported
to the host. That causes the host to skip sending
a command to synchronize caches. That causes data loss
when the drive is powered down.
Signed-off-by: Oliver Neukum
Reviewed-by: Johanne
Oliver Neukum writes:
> On Sun, 2016-07-10 at 17:45 +0200, Bjørn Mork wrote:
>> The workaround has been tested on a large number of different MBIM
>> and QMI devices, as well as the Ericsson F5521gw and H5321gw modems
>> with real Device Management functions.
>>
>> Signed-off-by: Bjørn Mork
>
>
On Mon, Aug 08, 2016 at 02:12:06PM +0200, Bjørn Mork wrote:
> Oliver Neukum writes:
> > On Sun, 2016-07-10 at 17:45 +0200, Bjørn Mork wrote:
> >> The workaround has been tested on a large number of different MBIM
> >> and QMI devices, as well as the Ericsson F5521gw and H5321gw modems
> >> with re
Oliver Neukum writes:
> On Mon, 2016-07-18 at 16:10 +0200, Kristian Evensen wrote:
>> On Mon, Jul 18, 2016 at 3:50 PM, Oliver Neukum wrote:
>> > No, you misunderstand me. I don't want quirks if we can avoid it.
>> > But if you need to do this for rndis_host and cdc_ether and maybe other
>> > driv
This patch set is based on the latest Felipe's usb.git / testing/fixes branch.
(The commit id = 10493a3c0718 ("usb: dwc3: gadget: increment request->actual
once")
Yoshihiro Shimoda (3):
usb: renesas_usbhs: Fix receiving data corrupt on R-Car Gen3 with dmac
usb: renesas_usbhs: clear the BRDYST
Since R-Car Gen3 SoC has the USB-DMAC, this driver should set
dparam->has_usb_dmac to 1. Otherwise, behavior of this driver and
the usb-dmac driver will be mismatch, then sometimes receiving data will
be corrupt.
Fixes: de18757e272d ("usb: renesas_usbhs: add R-Car Gen3 power control")
Cc: # v4.5+
This patch fixes an issue that unexpected BRDY interruption happens
when the usb_ep_{enable,disable}() are called with different direction.
In this case, the driver will cause the following message:
renesas_usbhs e659.usb: irq_ready run_error 1 : -16
This issue causes the followings:
1) A p
This patch fixes an issue that isochronous transfer's data is possible to
be lost as a workaround. Since this driver uses a workqueue to start
the dmac, the transfer is possible to be delayed when system load is high.
Fixes: 6e4b74e4690d ("usb: renesas: fix scheduling in atomic context bug")
Cc:
On Mon, Aug 8, 2016 at 11:42 AM, ican realizeum wrote:
> Sorry, I just realized that in gmail `Default reply behaviour` was set
> to `Reply` not `Reply All`, so I skipped the list when I replied
> last(for I forgot to select Reply All as I did before). Oops. So now
> hopefully everyone else can se
On Fri, Jun 10, 2016 at 03:32:41PM +0800, Chunfeng Yun wrote:
> --- /dev/null
> +++ b/drivers/usb/mtu3/Makefile
> @@ -0,0 +1,20 @@
> +
> +#ifeq ($(CONFIG_USB_DEBUG),y)
> + ccflags-y += -DDEBUG
> +#endif
There is no CONFIG_USB_DEBUG in the tree anymore, are you sure you
tested this? :)
On Mon, 2016-08-08 at 14:44 +0200, Bjørn Mork wrote:
> Oliver Neukum writes:
> > I don't see how it would be specific for a subsystem. If the patch
> > is correct, it belongs into the networking core.
>
> The bug is in the firmware implementation of the "read unique vendor
> assigned mac address
On 2016-08-07 04:59 AM, Oliver Neukum wrote:
On Thu, 2016-08-04 at 13:44 -0400, Robert Foss wrote:
On 2016-08-03 06:39 AM, Oliver Neukum wrote:
On Tue, 2016-08-02 at 10:37 -0400, Robert Foss wrote:
How can that depend on what we return to user space?
In the driver we can continue just ign
On Mon, 8 Aug 2016, ican realizeum wrote:
> >> The caller was hcd_resume_work(), which is part of a workqueue. This
> >> routine runs when the OHCI driver calls usb_hcd_resume_root_hub().
> >> There are only 3 places in the driver where this happens (two in
> >> ohci-hcd.c and one in ohci-hub.c),
From: Robert Foss
Implemented queued response handling. This queue is processed every time the
WDM_READ flag is cleared.
In case of a read error, userspace may not actually read the data, since the
driver returns an error through wdm_poll. After this, the underlying device may
attempt to send us
On Mon, Aug 08, 2016 at 12:00:38PM -0400, Nicholas Krause wrote:
> This removes the unneeded marco definitions for the marcos
> of XHCI_PORT_RW1S, XHCI_PORT_RW1C, XHCI_PORT_RWand
> XHCI_PORT_RZ due to no uses of these marcos in the file
> xhci-hub.c or any other related kernel source code f
On Mon, Aug 8, 2016 at 5:38 PM, Alan Stern wrote:
> On Mon, 8 Aug 2016, ican realizeum wrote:
>
>> >> The caller was hcd_resume_work(), which is part of a workqueue. This
>> >> routine runs when the OHCI driver calls usb_hcd_resume_root_hub().
>> >> There are only 3 places in the driver where thi
Hi,
On 05-08-2016 20:15, kbuild test robot wrote:
> Hi Felipe,
>
> [auto build test ERROR on balbi-usb/next]
> [also build test ERROR on v4.7 next-20160805]
> [if your patch is applied to the wrong git tree, please drop us a note to
> help improve the system]
>
> url:
> https://github.com/0
On Mon, Aug 8, 2016 at 7:43 PM, ican realizeum wrote:
> On Mon, Aug 8, 2016 at 5:38 PM, Alan Stern wrote:
>> On Mon, 8 Aug 2016, ican realizeum wrote:
>>
>>> >> The caller was hcd_resume_work(), which is part of a workqueue. This
>>> >> routine runs when the OHCI driver calls usb_hcd_resume_root
On Mon, 8 Aug 2016, ican realizeum wrote:
> Ok, here's what I found out:
> tlp being enabled in /etc/default/tlp (as TLP_ENABLE=1) would always
> set those to 'auto' aka they show up as 'suspended', regardless of
> what I did (eg. set them 'on') before executing shutdown(from X, in
> menu, Shutdow
Oliver Neukum writes:
> But why fix similar issues at two different places? And what about
> PCI or other cards that show the same problem?
I guess some sort of common helper would be nice to avoid open coding
this fix everywhere. But you would still have to modify every driver
where it is appl
On Mon, Aug 8, 2016 at 8:41 PM, Alan Stern wrote:
> On Mon, 8 Aug 2016, ican realizeum wrote:
>
>> Ok, here's what I found out:
>> tlp being enabled in /etc/default/tlp (as TLP_ENABLE=1) would always
>> set those to 'auto' aka they show up as 'suspended', regardless of
>> what I did (eg. set them
Hi Kishon,
As discussed before, here is a resend now that rc1 is out (and includes
the new of_usb_get_dr_mode_by_phy helper this patch needs).
Please merge this for 4.9-rcX some of the musb-sunxi glue changes
already merged have a runtime dependency on this patch, without
this patch boards using
Use the new of_usb_get_dr_mode_by_phy() function to get the dr_mode
from the musb controller node instead of assuming that having an id_det
gpio means otg mode, and not having one means host mode.
Implement peripheral-only mode by adding a sun4i_usb_phy0_get_id_det
helper which looks at the dr_mod
On Mon, 8 Aug 2016, ican realizeum wrote:
> >> 1. if I have line in debug.sh which attempts to poweroff manually via
> >> sysrq, like this:
> >> echo o > /proc/sysrq-trigger ; sleep 5
> >> then, there are no 'controller won't resume' and no 'HC died'
> >> messages, but there are only those with PM
This refactor results in a cleaner state machine code and promotes
consistency, readability, and maintanability of this driver.
This refactor state machine was well tested and it is currently running in
production code and devices.
Signed-off-by: Felipe F. Tonello
---
drivers/usb/gadget/functio
Use gadget's framework allocation function instead of directly calling
usb_ep_alloc_request().
Signed-off-by: Felipe F. Tonello
---
drivers/usb/gadget/function/f_hid.c | 6 +-
1 file changed, 1 insertion(+), 5 deletions(-)
diff --git a/drivers/usb/gadget/function/f_hid.c
b/drivers/usb/gadg
This change makes sure that the ALSA buffers are cleaned if an endpoint
becomes disabled.
Before this change, if the internal ALSA buffer did overflow, the MIDI
function would stop sending MIDI to the host.
Signed-off-by: Felipe F. Tonello
---
drivers/usb/gadget/function/f_midi.c | 27 +
We should always use free_ep_req() when allocating requests with
alloc_ep_req().
Signed-off-by: Felipe F. Tonello
---
drivers/usb/gadget/function/f_hid.c | 10 +++---
1 file changed, 3 insertions(+), 7 deletions(-)
diff --git a/drivers/usb/gadget/function/f_hid.c
b/drivers/usb/gadget/funct
The default_length parameter of alloc_ep_req was not really necessary
and gadget drivers would almost always create an inline function to pass
the same value to len and default_len.
So this patch also removes duplicate code from few drivers.
Signed-off-by: Felipe F. Tonello
---
drivers/usb/gadg
As discussed with Baolin Wang, Michal Nazarewicz and Felipe Balbi. I propose
the forced buffer alignment of OUT endpoints USB requests. This is implemented
by patches #1 and #3.
That not just simplifies the driver code, but it also prevents nasty bugs when
buflen is not aligned or even less than w
512 is the value used by wMaxPacketSize, as specified by the USB Spec. This
makes sure this driver uses, by default, the most optimal value for IN and OUT
endpoint requests.
Signed-off-by: Felipe F. Tonello
---
drivers/usb/gadget/function/f_midi.c | 2 +-
drivers/usb/gadget/legacy/gmidi.c| 2
Length of buffers should be of type size_t whenever possible. Altough
recommended, this change has no real practical change, unless a driver has a
uses a huge or negative buffer size - it might help find these bugs.
Signed-off-by: Felipe F. Tonello
---
drivers/usb/gadget/u_f.c | 2 +-
drivers/us
Using usb_ep_align() makes sure that the buffer size for OUT endpoints is
always aligned with wMaxPacketSize (512 usually). This makes sure
that no buffer has the wrong size, which can cause nasty bugs.
Signed-off-by: Felipe F. Tonello
---
drivers/usb/gadget/u_f.c | 3 +++
drivers/usb/gadget/u_
USB spec specifies wMaxPacketSize to be little endian (as other properties),
so when using this variable in the driver we should convert to the current
CPU endianness if necessary.
This patch also introduces usb_ep_align() which does always returns the
aligned buffer size for an endpoint. This is
The new version of alloc_ep_req() already aligns the buffer size to
wMaxPacketSize on OUT endpoints.
Signed-off-by: Felipe F. Tonello
---
drivers/usb/gadget/function/f_midi.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/drivers/usb/gadget/function/f_midi.c
b/drivers/
From: Robert Foss
This series enables runtime PM and asynchronous resume/suspend support for
xhci-plat devices.
This is a resumbmission of v3.
Changes since v1:
- Added Signed-off-by: Robert Foss
- Added proper metadata tags to series.
Changes since v2:
- Added missing changelog to cover-lett
From: Andrew Bresticker
USB host controllers can take a significant amount of time to suspend
and resume, adding several hundred miliseconds to the kernel resume
time. Since the XHCI controller has no outside dependencies (other than
clocks, which are suspended late/resumed early), allow it to su
From: Andrew Bresticker
Enable runtime PM for the xhci-plat device so that the parent device
may implement runtime PM.
Signed-off-by: Andrew Bresticker
Tested-by: Robert Foss
Signed-off-by: Robert Foss
---
drivers/usb/host/xhci-plat.c | 24 ++--
1 file changed, 22 inserti
On Mon, Aug 8, 2016 at 11:01 PM, Alan Stern wrote:
> On Mon, 8 Aug 2016, ican realizeum wrote:
>
>> >> 1. if I have line in debug.sh which attempts to poweroff manually via
>> >> sysrq, like this:
>> >> echo o > /proc/sysrq-trigger ; sleep 5
>> >> then, there are no 'controller won't resume' and n
El Mon, Aug 08, 2016 at 04:52:07PM +0800 Peter Chen ha dit:
> We have an well-known problem that the device needs to do some power
> sequence before it can be recognized by related host, the typical
> example like hard-wired mmc devices and usb devices.
>
> This power sequence is hard to be descr
unsubscsribe
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
>Quoting Peter Chen (2016-08-06 00:54:35)
>> On Fri, Aug 05, 2016 at 02:53:56PM -0700, Stephen Boyd wrote:
>> > Quoting Peter Chen (2016-07-08 02:45:28)
>> > > On Thu, Jul 07, 2016 at 03:20:59PM -0700, Stephen Boyd wrote:
>> > > > We don't call hw_device_reset() with the ci->lock held, so it
>> > >
> "Oliver" == Oliver Neukum writes:
Oliver> Some SATA to USB bridges fail to cooperate with some drives
Oliver> resulting in no cache being present being reported to the
Oliver> host. That causes the host to skip sending a command to
Oliver> synchronize caches. That causes data loss when the
From: Yonglong Wu
According to USB30 specification, the Function Remote Wakeup field can be
modified by the SetFeature() requests. SetFeature() is recommended to use.
Change-Id: Ie744b95f12d7d21d9519e77ed706c8cc33fa
Signed-off-by: Yonglong Wu
---
drivers/usb/core/hub.c |2 +-
1 file ch
From: Yonglong Wu
According to USB30 specification, the Function Remote Wakeup field can be
modified by the SetFeature() requests. SetFeature() is recommended to use.
Signed-off-by: Yonglong Wu
---
drivers/usb/core/hub.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dr
In sg_timeout(), req->status is set to "-ETIMEDOUT" before calling
into usb_sg_cancel(). usb_sg_cancel() will do nothing and return
directly if req->status has been set to a non-zero value. This will
cause driver hang as soon as transfer time out is triggered.
In my test case, below system log sho
On Fri, 5 Aug 2016 23:21:35 -0700
Tony Lindgren wrote:
> * Andreas Kemnade [160805 08:35]:
> > I repeat the subject line of the patch:
> > [PATCH v2] musb: omap2430: do not assume balanced enable()/disable()
> > It is *not* fix charging.
> >
> > So you mean that the phy should magically know at
On Tue, Aug 9, 2016 at 11:31 AM, Yonglong Wu wrote:
> From: Yonglong Wu
>
> According to USB30 specification, the Function Remote Wakeup field can be
> modified by the SetFeature() requests. SetFeature() is recommended to use.
>
> Signed-off-by: Yonglong Wu
> ---
> drivers/usb/core/hub.c |2
63 matches
Mail list logo
