Hi,
On Monday 15 September 2014 05:36 PM, Heikki Krogerus wrote:
On Fri, Sep 12, 2014 at 07:41:56PM +0530, Kishon Vijay Abraham I wrote:
I don't think create lookup should be in host init. If it's dt boot, the
binding should be in dt data or for other boot modes the bindig should be
done
in
On 2014-09-16 07:15, Felipe Balbi wrote:
Hi,
On Tue, Sep 16, 2014 at 10:02:25AM +0800, Peter Chen wrote:
On Mon, Sep 15, 2014 at 12:42:27PM +0200, Andreas Larsson wrote:
The state attribute is connected to the kobj of the udc, not the gadget.
Signed-off-by: Andreas Larsson
On 09/16/2014 12:29 AM, Gunter Königsmann wrote:
If after applying the patch I still get the warning and the scanner still
isn't working - did I do something wrong?
cat /proc/version is telling me I'm running the kernel I have compiled.
Thanks a lot,
and
You got two warnings previously,
On 09/15/2014 10:50 PM, Alan Stern wrote:
On Mon, 15 Sep 2014, Mathias Nyman wrote:
I haven't had time to dig into the usbmon traces, but I just got another
report from Gunter K�ningsmann about similar scanner problem, and I just
noticed
that in both cases we round the interval for high
On Fri 12-09-14 11:44:14, Alan Stern wrote:
On Fri, 12 Sep 2014, Petr Mladek wrote:
I don't think you can eliminate the lock quite so easily. This patch
introduces some nasty races.
@@ -577,18 +571,20 @@ static int hub_port_status(struct usb_hub *hub,
int port1,
On 15 September 2014 19:06, Andrew Bresticker abres...@chromium.org wrote:
On Mon, Sep 15, 2014 at 12:00 AM, Tomeu Vizoso to...@tomeuvizoso.net wrote:
On 12 September 2014 18:37, Andrew Bresticker abres...@chromium.org wrote:
On Tue, Sep 9, 2014 at 1:21 AM, Tomeu Vizoso to...@tomeuvizoso.net
On Tue, Sep 16, 2014 at 12:07:00PM +0530, Kishon Vijay Abraham I wrote:
Hi,
On Monday 15 September 2014 05:36 PM, Heikki Krogerus wrote:
On Fri, Sep 12, 2014 at 07:41:56PM +0530, Kishon Vijay Abraham I wrote:
I don't think create lookup should be in host init. If it's dt boot, the
On Tue, Sep 16, 2014 at 08:51:30AM +0800, Peter Chen wrote:
On Mon, Sep 15, 2014 at 12:36:13PM +0200, Antoine Tenart wrote:
Add a USB2 ChipIdea driver for ci13xxx, with optional PHY, clock
and DMA mask, to support USB2 ChipIdea controllers that don't need
specific functions.
Tested on
On Mon, 15 Sep 2014 11:59:15 -0400
Alan Stern st...@rowland.harvard.edu wrote:
On Sat, 13 Sep 2014, Joe Lawrence wrote:
Hi Alan,
I've collected 16 crashes since kicking off automated tests a little
over 24 hrs ago.
Each crash hit the BUG in qh_destroy() and the only unique
On Tue, Sep 16, 2014 at 08:07:21AM +0800, Peter Chen wrote:
On Mon, Sep 15, 2014 at 12:35:09PM +0200, Antoine Tenart wrote:
diff --git a/drivers/usb/chipidea/debug.c b/drivers/usb/chipidea/debug.c
index 8f437e1512fa..999e9d683d7a 100644
--- a/drivers/usb/chipidea/debug.c
+++
On Mon, Sep 15, 2014 at 09:09:06PM +0300, Sergei Shtylyov wrote:
On 9/15/2014 1:35 PM, Antoine Tenart wrote:
The USB PHY member of the HCD structure is renamed to 'usb_phy' and
modifications are done in all drivers accessing it.
Signed-off-by: Antoine Tenart
On Tue, Sep 16, 2014 at 03:53:47PM +0200, Antoine Tenart wrote:
On Mon, Sep 15, 2014 at 09:09:06PM +0300, Sergei Shtylyov wrote:
On 9/15/2014 1:35 PM, Antoine Tenart wrote:
The USB PHY member of the HCD structure is renamed to 'usb_phy' and
modifications are done in all drivers accessing
On Tue, Sep 16, 2014 at 03:38:41PM +0200, Antoine Tenart wrote:
On Tue, Sep 16, 2014 at 08:51:30AM +0800, Peter Chen wrote:
On Mon, Sep 15, 2014 at 12:36:13PM +0200, Antoine Tenart wrote:
Add a USB2 ChipIdea driver for ci13xxx, with optional PHY, clock
and DMA mask, to support USB2
On Tue, 16 Sep 2014, Mathias Nyman wrote:
It's not fully clear how xHCI controllers use the Interval field in the
Endpoint Context. Table 65 notably fails to include a line for HS
bulk-OUT/control endpoints, and the text isn't clear as to whether the
field is interpreted using
Use the local queue variable instead of computing it every time.
Signed-off-by: Laurent Pinchart laurent.pinch...@ideasonboard.com
---
drivers/usb/gadget/function/uvc_video.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/drivers/usb/gadget/function/uvc_video.c
The struct usb_endpoint_descriptor wMaxPacketSize field the struct
usb_ss_ep_comp_descriptor wBytesPerInterval field are stored in
little-endian format. Convert the values from CPU order to little endian
before storing the values.
Signed-off-by: Laurent Pinchart laurent.pinch...@ideasonboard.com
Hello,
This patch set fixes small issues with the UVC function driver.
The first patch has been received as part of one of Fengguang's 0day warning
report, I've just added a commit message body and collected acked-by's.
The other two patches are new, they fix an endianness problem on big-endian
On Tue, 16 Sep 2014, Joe Lawrence wrote:
You can check for this. Sprinkle ehci_info messages throughout
ehci_stop, printing the value of ehci-async-qh_next.qh. It should be
NULL the entire time.
I re-ran the tests with the following changes:
- moved num_async debug up above
On Tue, Sep 16, 2014 at 05:26:45PM +0300, Laurent Pinchart wrote:
Hello,
This patch set fixes small issues with the UVC function driver.
The first patch has been received as part of one of Fengguang's 0day warning
report, I've just added a commit message body and collected acked-by's.
On Tuesday 16 September 2014 09:56:51 Felipe Balbi wrote:
On Tue, Sep 16, 2014 at 05:26:45PM +0300, Laurent Pinchart wrote:
Hello,
This patch set fixes small issues with the UVC function driver.
The first patch has been received as part of one of Fengguang's 0day
warning report,
Hi,
On Mon, 15 Sep 2014 11:01:33 -0400 (EDT)
Alan Stern st...@rowland.harvard.edu wrote:
On Sun, 14 Sep 2014, Mark wrote:
Shuttle Technology/SCM Microsystems was the OEM manufacturer of SCSI-USB
converter cables sold by various companies including Adaptec [untested
patch posted
Hi,
[This is revised over the patch I posted previously.]
The Adaptec USBConnect 2000 is another SCSI-USB converter which uses
Shuttle Technology/SCM Microsystems chips. The US_FL_SCM_MULT_TARG quirk is
required to use SCSI devices with ID other than 0.
I don't have a USBConnect 2000, but based
On 09/15/2014 01:30 PM, Andrew Bresticker wrote:
On Mon, Sep 15, 2014 at 11:09 AM, Stephen Warren swar...@wwwdotorg.org wrote:
On 09/15/2014 11:06 AM, Andrew Bresticker wrote:
On Mon, Sep 15, 2014 at 12:00 AM, Tomeu Vizoso to...@tomeuvizoso.net wrote:
On 12 September 2014 18:37, Andrew
On Tue, 16 Sep 2014 10:44:45 -0400
Alan Stern st...@rowland.harvard.edu wrote:
On Tue, 16 Sep 2014, Joe Lawrence wrote:
You can check for this. Sprinkle ehci_info messages throughout
ehci_stop, printing the value of ehci-async-qh_next.qh. It should be
NULL the entire time.
I
On Tue, 16 Sep 2014, Petr [iso-8859-1] Ml�dek wrote:
Anyway, the solution for the race between kick_hub_wq() and
hub_event() might be to get the reference already in kick_hub_wq().
Yes, this probably would work.
I mean something like:
static void kick_hub_wq(struct usb_hub *hub)
{
Alright folks, we have -rc5 and I have applied the last 5 patches which
were pending. My tree is now closed for v3.18 merge window with 87
non-merge commits.
If your patches aren't there, good luck next time :-)
Now, please, refrain from sending patches because I won't look much at
them until
On Tue, 16 Sep 2014, Mark wrote:
It's probably better just to rely on entries to the unusual_devs.h
file. Those are automatically be available to anyone with an
up-to-date kernel, with no need for messing around with module
parameters.
The trouble is though, that requires the user
On Tue, 16 Sep 2014, Joe Lawrence wrote:
Anyway, the log above means that a QH was linked before the HC died,
but then it was never unlinked. Please add a line at the start of
ehci_endpoint_disable, printing out the value of ep-hcpriv for
comparison with the values listed above.
Will
Hi,
The Ariston Technologies iConnect 025 and iConnect 050 (also known as e.g.
iSCSI-50) are SCSI-USB converters which use Shuttle Technology/SCM
Microsystems chips. Only the connectors differ; both have the same USB ID.
The US_FL_SCM_MULT_TARG quirk is required to use SCSI devices with ID other
2014-09-11 0:32 GMT+04:00 Alan Stern st...@rowland.harvard.edu:
If all else fails, git bisect might pinpoint the cause of the problem.
Alan Stern
I would have need config bisect.
--
With best regards,
Matwey V. Kornilov
http://blog.matwey.name
xmpp://0x2...@jabber.ru
--
To unsubscribe from
Hi Greg, et al,
Another day, another uas quirk. Although you may not see it that way, this
is
actually a good thing :) With the new uas error handling code (which users
are
testing through a stand-alone version of the uas driver), people are now
actually sending me logs with useful error messages
Besides the ASM1051 (*) needing sdev-no_report_opcodes = 1, it turns out that
the JMicron JMS567 also needs it to work properly with uas (usb-storage always
sets it). Since some of the scsi devs were not to keen on the idea to
outrightly set sdev-no_report_opcodes = 1 for all uas devices, so add a
2014-09-10 23:50 GMT+04:00 Felipe Balbi ba...@ti.com:
hmmm, protocol error.
Hi,
I've found the root of the problem. CONFIG_USB_MUSB_TUSB6010=m affects
the code inside musb_hdrc inspite of tusb6010 not loaded at all.
When I disable CONFIG_USB_MUSB_TUSB6010 in my configuration,
everything works
Hi,
On Tue, Sep 16, 2014 at 08:40:14PM +0400, Matwey V. Kornilov wrote:
2014-09-10 23:50 GMT+04:00 Felipe Balbi ba...@ti.com:
hmmm, protocol error.
Hi,
I've found the root of the problem. CONFIG_USB_MUSB_TUSB6010=m affects
the code inside musb_hdrc inspite of tusb6010 not loaded at all.
On Tue, Sep 16, 2014 at 8:26 AM, Stephen Warren swar...@wwwdotorg.org wrote:
On 09/15/2014 01:30 PM, Andrew Bresticker wrote:
On Mon, Sep 15, 2014 at 11:09 AM, Stephen Warren swar...@wwwdotorg.org
wrote:
On 09/15/2014 11:06 AM, Andrew Bresticker wrote:
On Mon, Sep 15, 2014 at 12:00 AM,
2014-09-16 20:51 GMT+04:00 Felipe Balbi ba...@ti.com:
this can't be applied as it would break tusb6010.
Sure.
MUSB_FIFO_OFFSET is used only in musb_core_init to set endpoints.
Can not understand whether endpoint setup can be moved to musb_platform_init.
Or yet another callback to
Hi,
On Tue, Sep 16, 2014 at 09:08:17PM +0400, Matwey V. Kornilov wrote:
2014-09-16 20:51 GMT+04:00 Felipe Balbi ba...@ti.com:
this can't be applied as it would break tusb6010.
Sure.
MUSB_FIFO_OFFSET is used only in musb_core_init to set endpoints.
Can not understand whether endpoint
2014-09-16 21:25 GMT+04:00 Felipe Balbi ba...@ti.com:
we could, perhaps, pass a flag to change those offsets, but not a new
callback, I'm trying to get rid of some of them :-)
We could have a tool musb_is_tusb(musb) (like dev_is_pci(dev)) instead
of just a flag. But it is also a leakage in
Ok. What is about musb_io.h? What does it mean TUSB6010 doesn't allow
8-bit access; 16-bit access is the minimum.?
I think __raw_readb is kind of return *(u8_t*)(addr), but this is CPU
stuff as far as I understand.
--
With best regards,
Matwey V. Kornilov
http://blog.matwey.name
Hi Andy,
On Fri, Sep 12, 2014 at 02:28:06PM -0500, Andy Gross wrote:
+Example device nodes:
+
+ hs_phy: phy@100f8800 {
+ compatible = qcom,dwc3-hs-usb-phy;
+ reg = 0x100f8800 0x30;
Just wanted to point out that in our downstream code, the
On Tue, 16 Sep 2014 11:56:14 -0400
Alan Stern st...@rowland.harvard.edu wrote:
On Tue, 16 Sep 2014, Joe Lawrence wrote:
Anyway, the log above means that a QH was linked before the HC died,
but then it was never unlinked. Please add a line at the start of
ehci_endpoint_disable,
Hi,
On Tue, Sep 16, 2014 at 11:15:43AM -0700, Jack Pham wrote:
Hi Andy,
On Fri, Sep 12, 2014 at 02:28:06PM -0500, Andy Gross wrote:
+Example device nodes:
+
+ hs_phy: phy@100f8800 {
+ compatible = qcom,dwc3-hs-usb-phy;
+ reg = 0x100f8800
Hi Andy,
On Fri, Sep 12, 2014 at 02:28:08PM -0500, Andy Gross wrote:
+static int qcom_dwc3_hs_phy_init(struct qcom_dwc3_usb_phy *phy_dwc3)
+{
+ u32 val;
+
+ /*
+ * HSPHY Initialization: Enable UTMI clock, select 19.2MHz fsel
+ * enable clamping, and disable RETENTION
Hi,
(man, talk about trimming... leave some context ;-)
On Tue, Sep 16, 2014 at 10:06:33PM +0400, Matwey V. Kornilov wrote:
Ok. What is about musb_io.h? What does it mean TUSB6010 doesn't allow
8-bit access; 16-bit access is the minimum.?
it means that readb() won't work.
I think
On Tue, 16 Sep 2014 11:40:03 -0400 (EDT)
Alan Stern st...@rowland.harvard.edu wrote:
On Tue, 16 Sep 2014, Mark wrote:
...
Another issue relates to manufacturer USB ID screw-ups. The Buffalo
USB-SCSI cable is a good example. According to the Windows INF file
available from
On Tue, 16 Sep 2014, Joe Lawrence wrote:
Quick turn around on this one :)
crash log | grep :2c:00.0
pci :2c:00.0: [8086:1d26] type 00 class 0x0c0320
pci :2c:00.0: reg 0x10: [mem 0x9000-0x93ff]
pci :2c:00.0: PME# supported from D0 D3hot D3cold
ehci-pci
On Tue, 16 Sep 2014, Mark wrote:
On Tue, 16 Sep 2014 11:40:03 -0400 (EDT)
Alan Stern st...@rowland.harvard.edu wrote:
On Tue, 16 Sep 2014, Mark wrote:
...
Another issue relates to manufacturer USB ID screw-ups. The Buffalo
USB-SCSI cable is a good example. According to the Windows
This is a series of updates to the dwc2 driver, all related
to the handling of non-dword-aligned transfers. I have tested
all of these on the Raspberry Pi and Altera SOCFPGA platform,
and have not seen any regressions.
v2: Remove pass gfp_t flags down to dwc2_hc_setup_align_buf()
patch, since it
The driver's handling of DMA buffers for non-aligned transfers
was kind of nuts. For IN transfers, it left the URB DMA buffer
mapped until the transfer completed, then synced it, copied the
data from the bounce buffer, then synced it again.
Instead of that, just call usb_hcd_unmap_urb_for_dma()
Clip max_transfer_size to 65535 for host. dwc2_hc_setup_align_buf()
allocates coherent buffers with this size, and if it's too large we
can exhaust the coherent DMA pool.
Tested on Raspberry Pi and Altera SOCFPGA.
Signed-off-by: Paul Zimmerman pa...@synopsys.com
---
drivers/usb/dwc2/core.c | 7
On Tue, 16 Sep 2014 15:36:42 -0400 (EDT)
Alan Stern st...@rowland.harvard.edu wrote:
On Tue, 16 Sep 2014, Mark wrote:
On Tue, 16 Sep 2014 11:40:03 -0400 (EDT)
Alan Stern st...@rowland.harvard.edu wrote:
On Tue, 16 Sep 2014, Mark wrote:
...
Another issue relates to
Fix line length in uwb-internal.h
Signed-off-by: Thomas Pugliese thomas.pugli...@gmail.com
---
drivers/uwb/uwb-internal.h | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/uwb/uwb-internal.h b/drivers/uwb/uwb-internal.h
index 9a103b1..6d1bed1 100644
---
On Tue, Sep 16, 2014 at 11:27:52AM -0700, Jack Pham wrote:
Hi Andy,
On Fri, Sep 12, 2014 at 02:28:08PM -0500, Andy Gross wrote:
+static int qcom_dwc3_hs_phy_init(struct qcom_dwc3_usb_phy *phy_dwc3)
+{
+ u32 val;
+
+ /*
+* HSPHY Initialization: Enable UTMI clock, select
UWB does not require PCI to be enabled so remove build dependency.
Signed-off-by: Thomas Pugliese thomas.pugli...@gmail.com
---
drivers/uwb/Kconfig | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/uwb/Kconfig b/drivers/uwb/Kconfig
index 2431eed..c204094 100644
--- a/drivers/uwb/Kconfig
Print info about the radio controller device instead of the its parent
when UWB devices connect and disconnect.
Signed-off-by: Thomas Pugliese thomas.pugli...@gmail.com
---
drivers/uwb/lc-dev.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/uwb/lc-dev.c
Some UWB cleanups for 3.18
Thomas Pugliese (3):
uwb: line length cleanup
uwb: update uwb device prints to be more useful
uwb: remove UWB build dependency on PCI
drivers/uwb/Kconfig| 1 -
drivers/uwb/lc-dev.c | 8
drivers/uwb/uwb-internal.h | 3 ++-
3 files changed,
Sigh. Not my week for submitting patches, I guess. Patch #2
was missing the freeing of the bounce buffers. I didn't
notice the leak in my testing.
This is a series of updates to the dwc2 driver, all related
to the handling of non-dword-aligned transfers. I have tested
all of these on the
The driver's handling of DMA buffers for non-aligned transfers
was kind of nuts. For IN transfers, it left the URB DMA buffer
mapped until the transfer completed, then synced it, copied the
data from the bounce buffer, then synced it again.
Instead of that, just call usb_hcd_unmap_urb_for_dma()
Clip max_transfer_size to 65535 for host. dwc2_hc_setup_align_buf()
allocates coherent buffers with this size, and if it's too large we
can exhaust the coherent DMA pool.
Tested on Raspberry Pi and Altera SOCFPGA.
Signed-off-by: Paul Zimmerman pa...@synopsys.com
---
drivers/usb/dwc2/core.c | 7
Documentation/usb/WUSB-Design-overview.txt states that UWB devices seen
by a UWB radio controller are added to /sys/bus/uwb/devices, but this
was not actually being done. This functionality is needed in order for
UWB peer devices to be enumerated by user mode tools. This patch
creates a uwb
The existing UWB documentation states that UWB devices show up in
/sys/class/uwb and /sys/bus/uwb/devices. Up until the most recent
changes to add uwb devices to their own bus, neither of these statements
were actually true. Now, UWB devices do show up in /sys/bus/uwb/devices
so the
Create a system bus for UWB devices and add in-range UWB devices to it
as they are detected. Prior to this change, UWB devices were added to
the device tree, but since they did not exist on a bus, they would be
enumerated by udev.
Thomas Pugliese (2):
uwb: create a uwb bus type and add
Add an ASIE sysfs attribute to uwb_rc devices. This allows user mode to
add and remove application specific information elements (ASIEs) to the
beacon of a uwb_rc device.
Thomas Pugliese (2):
uwb: add an ASIE sysfs attribute to uwb_rc devices
uwb: doc: add documentation for ASIE sysfs
Document the /sys/class/uwb_rc/uwbN/ASIE sysfs attribute
Signed-off-by: Thomas Pugliese thomas.pugli...@gmail.com
---
Documentation/ABI/testing/sysfs-class-uwb_rc | 13 +
1 file changed, 13 insertions(+)
diff --git a/Documentation/ABI/testing/sysfs-class-uwb_rc
Allow user mode to add and remove application specific information
elements (ASIEs) to the beacon of a uwb_rc device.
Signed-off-by: Thomas Pugliese thomas.pugli...@gmail.com
---
drivers/uwb/lc-rc.c | 99 +
1 file changed, 99 insertions(+)
Wireless USB does not require PCI so remove USB_WUSB build dependency on
PCI.
Signed-off-by: Thomas Pugliese thomas.pugli...@gmail.com
---
drivers/usb/wusbcore/Kconfig | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/usb/wusbcore/Kconfig b/drivers/usb/wusbcore/Kconfig
index
Add USB build dependency for USB_WUSB_CBAF.
Signed-off-by: Thomas Pugliese thomas.pugli...@gmail.com
---
drivers/usb/wusbcore/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/usb/wusbcore/Kconfig b/drivers/usb/wusbcore/Kconfig
index f5c92f6..348de1d 100644
---
An HWA is a USB device so it depends on USB.
Signed-off-by: Thomas Pugliese thomas.pugli...@gmail.com
---
drivers/usb/host/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/host/Kconfig b/drivers/usb/host/Kconfig
index 82800a7..64805d9 100644
---
Fix build dependencies for WUSB devices.
Thomas Pugliese (3):
usb: hwa: add USB build dependency for USB_HWA_HCD
usb: wusbcore: remove USB_WUSB build dependency on PCI
usb: wusbcore: USB_WUSB_CBAF depends on USB
drivers/usb/host/Kconfig | 2 +-
drivers/usb/wusbcore/Kconfig | 2 +-
2
When completing an aborted transfer, skip done segs before calling
wa_complete_remaining_xfer_segs to avoid a runtime warning. The warning
is harmless in this case but avoiding it prevents false error reports.
Signed-off-by: Thomas Pugliese thomas.pugli...@gmail.com
---
Hello,
I'm experiencing an issue on a MacBook Pro 11,1 (late 2013 model, 13)
with kernel 3.16.2, libusb-1.0.19, using qemu-2.1.1 (I tried qemu git
master as well) where my USB devices get reset a bunch of times when I
attach them to a guest/vm, and eventually completely disconnect from
both the
On 09/16/2014 10:57 AM, Andrew Bresticker wrote:
On Tue, Sep 16, 2014 at 8:26 AM, Stephen Warren swar...@wwwdotorg.org wrote:
On 09/15/2014 01:30 PM, Andrew Bresticker wrote:
On Mon, Sep 15, 2014 at 11:09 AM, Stephen Warren swar...@wwwdotorg.org
wrote:
On 09/15/2014 11:06 AM, Andrew
On Tue, Sep 16, 2014 at 9:57 AM, Andrew Bresticker
abres...@chromium.org wrote:
On Tue, Sep 16, 2014 at 8:26 AM, Stephen Warren swar...@wwwdotorg.org wrote:
On 09/15/2014 01:30 PM, Andrew Bresticker wrote:
On Mon, Sep 15, 2014 at 11:09 AM, Stephen Warren swar...@wwwdotorg.org
wrote:
On
On Tue, Sep 16, 2014 at 3:40 PM, Stephen Warren swar...@wwwdotorg.org wrote:
On 09/16/2014 10:57 AM, Andrew Bresticker wrote:
On Tue, Sep 16, 2014 at 8:26 AM, Stephen Warren swar...@wwwdotorg.org
wrote:
On 09/15/2014 01:30 PM, Andrew Bresticker wrote:
On Mon, Sep 15, 2014 at 11:09 AM,
On 09/16/2014 04:46 PM, Andrew Bresticker wrote:
On Tue, Sep 16, 2014 at 9:57 AM, Andrew Bresticker
abres...@chromium.org wrote:
On Tue, Sep 16, 2014 at 8:26 AM, Stephen Warren swar...@wwwdotorg.org wrote:
On 09/15/2014 01:30 PM, Andrew Bresticker wrote:
On Mon, Sep 15, 2014 at 11:09 AM,
On Tue, 09 Sep 2014, Octavian Purdila wrote:
This patch implements the USB part of the Diolan USB-I2C/SPI/GPIO
Master Adapter DLN-2. Details about the device can be found here:
https://www.diolan.com/i2c/i2c_interface.html.
Information about the USB protocol can be found in the
On Tue, Sep 16, 2014 at 4:15 PM, Stephen Warren swar...@wwwdotorg.org wrote:
On 09/16/2014 04:46 PM, Andrew Bresticker wrote:
On Tue, Sep 16, 2014 at 9:57 AM, Andrew Bresticker
abres...@chromium.org wrote:
On Tue, Sep 16, 2014 at 8:26 AM, Stephen Warren swar...@wwwdotorg.org
wrote:
On
Tested on the Marvell Berlin SoCs USB controllers.
Signed-off-by: Antoine Tenart antoine.ten...@free-electrons.com
---
drivers/usb/chipidea/Makefile | 1 +
drivers/usb/chipidea/ci_hdrc_usb2.c | 137
2 files changed,
From: Alan Stern st...@rowland.harvard.edu
This patch adds support for the new udc-core reset notifier to the
net2280 driver.
Signed-off-by: Alan Stern st...@rowland.harvard.edu
Signed-off-by: Felipe Balbi ba...@ti.com
Signed-off-by: Peter Chen peter.c...@freescale.com
---
Replace usb_gadget_driver's disconnect with udc-core's reset notifier at
bus reset handler.
Signed-off-by: Peter Chen peter.c...@freescale.com
---
drivers/usb/gadget/udc/m66592-udc.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/gadget/udc/m66592-udc.c
Replace usb_gadget_driver's disconnect with udc-core's reset notifier at
bus reset handler.
Signed-off-by: Peter Chen peter.c...@freescale.com
---
drivers/usb/gadget/udc/fsl_qe_udc.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/gadget/udc/fsl_qe_udc.c
From: Felipe Balbi ba...@ti.com
Replace usb_gadget_driver's disconnect with udc-core's reset notifier at
bus reset handler.
Signed-off-by: Felipe Balbi ba...@ti.com
Signed-off-by: Peter Chen peter.c...@freescale.com
---
drivers/usb/musb/musb_gadget.c |9 ++---
1 file changed, 6
Replace usb_gadget_driver's disconnect with udc-core's reset notifier at
bus reset handler.
Signed-off-by: Peter Chen peter.c...@freescale.com
---
drivers/usb/gadget/udc/pxa25x_udc.c | 29 -
1 file changed, 28 insertions(+), 1 deletion(-)
diff --git
From: Alan Stern st...@rowland.harvard.edu
Replace usb_gadget_driver's disconnect with udc-core's reset notifier at
bus reset handler.
Signed-off-by: Alan Stern st...@rowland.harvard.edu
Signed-off-by: Felipe Balbi ba...@ti.com
Signed-off-by: Peter chen peter.c...@freescale.com
---
From: Felipe Balbi ba...@ti.com
Replace usb_gadget_driver's disconnect with udc-core's reset notifier at
bus reset handler.
Signed-off-by: Felipe Balbi ba...@ti.com
Signed-off-by: Peter Chen peter.c...@freescale.com
---
drivers/usb/dwc3/gadget.c | 17 -
1 file changed, 12
Replace usb_gadget_driver's disconnect with udc-core's reset notifier at
bus reset handler.
Signed-off-by: Peter Chen peter.c...@freescale.com
---
drivers/usb/chipidea/udc.c |8 ++--
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git a/drivers/usb/chipidea/udc.c
Replace usb_gadget_driver's disconnect with udc-core's reset notifier at
bus reset handler.
Signed-off-by: Peter Chen peter.c...@freescale.com
---
drivers/usb/gadget/udc/at91_udc.c | 27 ++-
1 file changed, 26 insertions(+), 1 deletion(-)
diff --git
Hi Felipe,
In this series, I convert udc driver to use udc-core's reset notifier
which has added recently, I only change the drivers which has
bus reset handler and call usb_gadget_driver's -disconnect in it.
For five you and Alan's patches, I cherry-pick them from your
gadget-add-reset-method
From: Alan Stern st...@rowland.harvard.edu
This patch adds support for the new udc-core reset notifier to the
net2272 driver.
Signed-off-by: Alan Stern st...@rowland.harvard.edu
Signed-off-by: Felipe Balbi ba...@ti.com
Signed-off-by: Peter Chen peter.c...@freescale.com
---
Replace usb_gadget_driver's disconnect with udc-core's reset notifier at
bus reset handler.
Signed-off-by: Peter Chen peter.c...@freescale.com
---
drivers/usb/gadget/udc/mv_udc_core.c | 19 ++-
1 file changed, 18 insertions(+), 1 deletion(-)
diff --git
Replace usb_gadget_driver's disconnect with udc-core's reset notifier at
bus reset handler.
Signed-off-by: Peter Chen peter.c...@freescale.com
---
drivers/usb/gadget/udc/fsl_udc_core.c | 11 +++
1 file changed, 7 insertions(+), 4 deletions(-)
diff --git
Replace usb_gadget_driver's disconnect with udc-core's reset notifier at
bus reset handler.
Signed-off-by: Peter Chen peter.c...@freescale.com
---
drivers/usb/gadget/udc/bcm63xx_udc.c |6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git
Replace usb_gadget_driver's disconnect with udc-core's reset notifier at
bus reset handler.
Signed-off-by: Peter Chen peter.c...@freescale.com
---
drivers/usb/gadget/udc/amd5536udc.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/gadget/udc/amd5536udc.c
Replace usb_gadget_driver's disconnect with udc-core's reset notifier at
bus reset handler.
Signed-off-by: Peter Chen peter.c...@freescale.com
---
drivers/usb/gadget/udc/r8a66597-udc.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/gadget/udc/r8a66597-udc.c
Replace usb_gadget_driver's disconnect with udc-core's reset notifier at
bus reset handler.
Signed-off-by: Peter Chen peter.c...@freescale.com
---
drivers/usb/gadget/udc/atmel_usba_udc.c |5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git
Replace usb_gadget_driver's disconnect with udc-core's reset notifier at
bus reset handler.
Signed-off-by: Peter Chen peter.c...@freescale.com
---
drivers/usb/gadget/udc/pch_udc.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/usb/gadget/udc/pch_udc.c
Hi,
On Wed, Sep 17, 2014 at 09:13:53AM +0800, Peter Chen wrote:
Hi Felipe,
In this series, I convert udc driver to use udc-core's reset notifier
which has added recently, I only change the drivers which has
bus reset handler and call usb_gadget_driver's -disconnect in it.
For five you
According to xHCI specification, PORT_DEV_REMOVE(bit 30) in PORTSC
true means Device is non-removable.
Reported-by: Juro Bystricky jurobystri...@hotmail.com
Signed-off-by: Lu Baolu baolu...@linux.intel.com
---
drivers/usb/host/xhci.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
98 matches
Mail list logo
