This patch fixes problem with unnecessary usb_ep_set_maxpacket_limit() usage.
It should not be used in at91udc_probe() function, where maxpacket values are
set for field "maxpacket" of struct at91_ep, which is representation of
endpoint in driver internals. Function usb_ep_set_maxpacket_limit() is
Dear Matt,
I would like to make your life easier and help you to merge all patches
from the list as soon as possible. I have forked [1] libusbg repository
[2], uploaded all the commits which were sent (mine and authored by
Stanislaw Wadas also) on the list and created a pull request [3]. In my
rep
From: "Ivan T. Ivanov"
Document device tree binding information as required by
the Qualcomm USB controller.
Signed-off-by: Ivan T. Ivanov
---
.../devicetree/bindings/usb/msm-hsusb.txt | 17 +
1 file changed, 17 insertions(+)
diff --git a/Documentation/devicetree/bin
Hi Felipe,
Hope you had a good vacation :).
Could you please take a look at these two fixes? Thanks.
cheers,
-roger
On 02/04/2014 03:25 PM, Roger Quadros wrote:
> Hi Greg,
>
> Patch 1 fixes SuperSpeed hub enumeration on beaglebone.
> Patch 2 fixes remote-wakeup resume on beaglebone.
>
> Felip
Hi !
I've tried your patch but that was not ok.
Here are the logs:
Feb 19 20:44:24 10.0.0.254 kernel: [517090.88]
drivers/usb/serial/io_ti.c: read_download_mem - @ 0 for 1
Feb 19 20:44:24 10.0.0.254 kernel: [517090.90]
drivers/usb/serial/io_ti.c: read_download_mem - @ 2 for 4
Feb 19 20:4
Hi Benoit, Tony & Lee,
This patchset brings up USB Host ports and Ethernet port on
the OMAP5 uEVM board.
It also does some cleanup with respect to DT clock binding
for the mfd/omap-usb-host driver.
Please queue these for -next.
Tested on:
- OMAP5 uEVM
- Pandaboard ES Rev. B1
- Beagleboard-XM
The omap-usb-host driver expects a certain name for internal
and external reference clocks. Provide these clocks.
Signed-off-by: Roger Quadros
---
arch/arm/boot/dts/omap4.dtsi | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/boot/dts/omap4.dtsi b/arch/arm/boot/dts/omap4.dtsi
in
The omap-usb-host driver expects a certain name for internal
and external reference clocks. Provide these clocks.
Signed-off-by: Roger Quadros
---
arch/arm/boot/dts/omap5.dtsi | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/boot/dts/omap5.dtsi b/arch/arm/boot/dts/omap5.dtsi
in
The USB PHY gets its clock from AUXCLK3. Provide this
information.
Signed-off-by: Roger Quadros
---
arch/arm/boot/dts/omap4-panda-common.dtsi | 8 ++--
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git a/arch/arm/boot/dts/omap4-panda-common.dtsi
b/arch/arm/boot/dts/omap4-panda-com
The omap-usb-host driver expects certained named clocks.
Add this information to the DT binding document.
CC: Lee Jones
CC: Samuel Ortiz
Signed-off-by: Roger Quadros
---
.../devicetree/bindings/mfd/omap-usb-host.txt | 23 ++
1 file changed, 23 insertions(+)
diff --git
The USB Host driver manages this clock so no need to have it in
the hwmod data. We also get rid of the 'ehci_logic_fck' alias
for 'usbhost_120m_fck' clock.
CC: Paul Walmsley
Signed-off-by: Roger Quadros
---
arch/arm/mach-omap2/omap_hwmod_3xxx_data.c | 6 --
1 file changed, 6 deletions(-)
d
The OMAP USB Host MFD driver no longer expects these non-existing
clocks from the OMAP3 platform, so get rid of them.
CC: Tero Kristo
CC: Mike Turquette
Signed-off-by: Roger Quadros
---
arch/arm/mach-omap2/cclock3xxx_data.c | 4
drivers/clk/ti/clk-3xxx.c | 4
2 files chan
Use a meaningful name for the reference clocks so that it indicates the
function.
CC: Lee Jones
CC: Samuel Ortiz
Signed-off-by: Roger Quadros
---
drivers/mfd/omap-usb-host.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers/mfd/omap-usb-host.c b/drivers/
Not all revisions have all the clocks so get the necessary clocks
based on hardware revision.
This should avoid un-necessary clk_get failure messages that were
observed earlier.
CC: Lee Jones
CC: Samuel Ortiz
Signed-off-by: Roger Quadros
---
drivers/mfd/omap-usb-host.c | 43 ++
The OMAP EHCI and OHCI controllers are not compatible with drivers
other than "ti,ehci-omap" and "ti,ohci-omap3" respectively, so get
rid of the incompatible ids.
CC: Alan Stern
Signed-off-by: Roger Quadros
---
arch/arm/boot/dts/omap3.dtsi | 4 ++--
arch/arm/boot/dts/omap4.dtsi | 4 ++--
arch/a
Be more strict and always fail on clk_get() error.
For OMAP3 platforms, get the 120MHz EHCI clock by its proper name
'usbhost_120m_fck' instead of its alias 'ehci_logic_fck'.
CC: Lee Jones
CC: Samuel Ortiz
Signed-off-by: Roger Quadros
---
drivers/mfd/omap-usb-host.c | 65 +
The HS USB 2 PHY gets its clock from AUXCLK1. Provide this
information.
Signed-off-by: Roger Quadros
---
arch/arm/boot/dts/omap5-uevm.dts | 8 ++--
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git a/arch/arm/boot/dts/omap5-uevm.dts b/arch/arm/boot/dts/omap5-uevm.dts
index 002fa70.
Remove non-compatible id from examples.
CC: Alan Stern
Signed-off-by: Roger Quadros
---
Documentation/devicetree/bindings/usb/ehci-omap.txt | 2 +-
Documentation/devicetree/bindings/usb/ohci-omap3.txt | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/devicetr
The necessary clock phandle for the EHCI clock is now provided
via device tree so we no longer need this legacy method.
Signed-off-by: Roger Quadros
---
arch/arm/mach-omap2/pdata-quirks.c | 16
1 file changed, 16 deletions(-)
diff --git a/arch/arm/mach-omap2/pdata-quirks.c
b/a
The omap-usb-tll driver needs one clock for each TLL channel.
Add this information to the DT binding document.
CC: Lee Jones
CC: Samuel Ortiz
Signed-off-by: Roger Quadros
---
Documentation/devicetree/bindings/mfd/omap-usb-tll.txt | 10 ++
1 file changed, 10 insertions(+)
diff --git a/
[ Please do not drop recipients from your replies, that is, in this case
respond directly to me while keeping the list on CC to avoid messages
being overlooked.
Keeping some context and responding inline is also recommended. ]
On Thu, Feb 20, 2014 at 11:09:55AM +, Ludovic wrote:
> Hi
Hi Greg,
Here's a pull request for final round of fixes. All patches have
been soaking for a long time in linux-usb, passed my 300 randconfig
builds and work on real HW (where applicable).
This pull request is based off of greg/usb-linus in order for me
to avoid merging patches you had already me
Hi,
On Thu, Feb 20, 2014 at 12:59:38PM +0200, Roger Quadros wrote:
> Hi Felipe,
>
> Hope you had a good vacation :).
sure had.
> Could you please take a look at these two fixes? Thanks.
you should have received my confirmation email ;-)
--
balbi
signature.asc
Description: Digital signature
On Wed, 19 Feb 2014, Greg KH wrote:
> > + pr_warn("Process %d (%s) called USBDEVFS_%s for active endpoint
> > %s ep %02x\n",
> > + task_pid_nr(current), current->comm,
> > + ioctl_name, dev_name(&udev->dev), epnum);
> > +}
>
> If you
It is an error for a driver to call usb_clear_halt() or
usb_reset_endpoint() while there are URBs queued for the endpoint,
because the end result is not well defined. At the time the endpoint
gets reset, it may or may not be actively running.
As far as I know, no kernel drivers do this. But some
Hi,
On Mon, Dec 16, 2013 at 07:23:32PM -0600, Felipe Balbi wrote:
> Add a few flags to tell gadget framework which
> features a particular endpoint supports.
>
> Signed-off-by: Felipe Balbi
looks like nobody has any further comments to this series. I'm assuming
it's ok to apply.
--
balbi
si
On Fri, Feb 7, 2014 at 2:11 PM, Alan Stern wrote:
> On Fri, 31 Jan 2014, Dan Williams wrote:
>
>> In general we do not want khubd to act on port status changes that are
>> the result of in progress resets or port pm runtime operations.
>
> The nomenclature is a little confusing. Let's agree that
Am 19.02.2014 18:14, schrieb Johan Hovold:
> On Wed, Feb 19, 2014 at 06:05:54PM +0100, Karsten Malcher wrote:
>> Am 19.02.2014 18:00, schrieb Johan Hovold:
>>> I need an adapter that can handle 2400 Baud to talk to the
>>> ft639/ede639 servo controller chip or possibly a pl2303 driver
>>> that is
Hi,
On Wed, Feb 19, 2014 at 03:10:45PM +0530, Subbaraya Sundeep Bhatta wrote:
> This patch adds xilinx axi usb2 device driver support
>
> Signed-off-by: Subbaraya Sundeep Bhatta
> ---
> .../devicetree/bindings/usb/xilinx_usb.txt | 21 +
> drivers/usb/gadget/Kconfig
Hi,
On Thu, Feb 20, 2014 at 07:30:13AM +0100, Robert Baldyga wrote:
> This patch adds support for deferred gadget driver bind as a remedy
> for situation when UDC drivers and gadget drivers are builded into
> the kernel, and gadget driver is loaded as first.
>
> Till now, it that case gadget driv
On Thu, 20 Feb 2014, Dan Williams wrote:
> > You forgot to acquire the port lock in usb_reset_device. The lock and
> > unlock calls should surround the call to usb_reset_and_verify_device.
> > Both that routine and hub_port_init should be documented as requiring
> > their caller to hold the port
On Thu, Feb 20, 2014 at 07:19:13PM +0100, Frank Schäfer wrote:
> Am 19.02.2014 18:14, schrieb Johan Hovold:
> > What driver is that? The latest clone-related patch from Frank that I've
> > seen stated:
> >
> > "According to Prolific, several (unauthorized) cheap and less
> > functional cl
Hi,
I've been trying to understand why the uboot code is unable to work with
USB1.1 devices.
The board has a hub chip connected to the one of the 2 usb controllers.
On a USB analyzer:
I notice on an analyzer that there are no SOF or IN tokens seen on the
bus at all. After the very first setup pac
PREPARE_[DELAYED_]WORK() are being phased out. They have few users
and a nasty surprise in terms of reentrancy guarantee as workqueue
considers work items to be different if they don't have the same work
function.
usb_hub->init_work is multiplexed with multiple work functions.
Introduce hub_init_
On Thu, Feb 20, 2014 at 03:44:27PM -0500, Tejun Heo wrote:
> PREPARE_[DELAYED_]WORK() are being phased out. They have few users
> and a nasty surprise in terms of reentrancy guarantee as workqueue
> considers work items to be different if they don't have the same work
> function.
>
> usb_hub->ini
On Thu, Feb 20, 2014 at 02:48:02PM -0600, Ruchika wrote:
> Hi,
> I've been trying to understand why the uboot code is unable to work with
> USB1.1 devices.
> The board has a hub chip connected to the one of the 2 usb controllers.
>
> On a USB analyzer:
> I notice on an analyzer that there are no S
On 19.2.2014 15:46, Daniel Mack wrote:
On 02/18/2014 02:44 AM, Michal Šmucr wrote:
during searching for solution to problem with Beaglebone Black USB
unreliable reconnections, which i had, when i tried to reconnect devices
to external powered hub, I came to that older patch from Ravi Babu,
which
Alan,
The Lenovo Yogi 13 tablet comes with a Realtek RTL8723AU wireless device built
in. Realtek sent me a driver that I modified so that it would build on new
kernels, and created a GitHub repo so that it would be available to the
community. One of the users of this driver is reporting interm
On Thu, Feb 20, 2014 at 09:26:50AM -0600, Felipe Balbi wrote:
> Hi Greg,
>
> Here's a pull request for final round of fixes. All patches have
> been soaking for a long time in linux-usb, passed my 300 randconfig
> builds and work on real HW (where applicable).
>
> This pull request is based off o
I tried yet another USB 3.0 external HDD enclosure with the 1 TB WD
drive that has been the source of all these problems. This one is made
by Icy Dock. It's a MB080U35-1SB, and has USB 3.0 as well as eSATA. I
figured the eSATA would work even if the USB 3.0 failed.
Eureka! It works via USB 3.0
On Thu, Feb 20, 2014 at 10:19:27PM +0100, Michal Šmucr wrote:
> On 19.2.2014 15:46, Daniel Mack wrote:
> >On 02/18/2014 02:44 AM, Michal Šmucr wrote:
> >>during searching for solution to problem with Beaglebone Black USB
> >>unreliable reconnections, which i had, when i tried to reconnect devices
>
Peter, Dmitry et al,
This is a real bug that dents the usability of Linux against Windows
or MacOS. We can enable model-specific workarounds, but what approach
would catch phantom stuck keys in the input stack?
On 18 February 2014 10:21, Peter Stuge wrote:
> Clinton Sprain wrote:
>> I noticed yo
We have observed a rare cycle state desync bug after Set TR Dequeue
Pointer commands on Intel LynxPoint xHCs (resulting in an endpoint that
doesn't fetch new TRBs and thus an unresponsive USB device). It always
triggers when a previous Set TR Dequeue Pointer command has set the
pointer to the final
Hi,
>> + * Copyright (C) 2010 - 2014 Xilinx, Inc.
>> + *
>> + * Some parts of this driver code is based on the driver for at91-series
>> + * USB peripheral controller (at91_udc.c).
>> + *
>> + * This program is free software; you can redistribute it
>> + * and/or modify it under the terms of the G
Currently the ppc-of driver uses the compatibility string
"usb-ehci". This means platforms that use device-tree and implement an
EHCI compatible interface have to either use the ppc-of driver or add
a compatible line to the ehci-platform driver. It would be more
appropriate for the platform driver
The IBM Akebono board uses the PPC476GTR SoC which has a OHCI
compliant USB host interface. This patch adds support for it to the
OHCI platform driver.
As we use device tree to pass platform specific data instead of
platform data we remove the check for platform data and instead
provide reasonable
The IBM Akebono board is a development board for the new PPC476GTR
system on chip (SoC).
This is just a resubmission of the previous patches rebased on kernel
v3.13. Ben H has indicated the subsystem specific changes should be
merged via the appropriate kernel trees.
Alistair Popple (7):
IBM Ak
On 02/20/2014 07:26 PM, Felipe Balbi wrote:
> Hi,
>
> On Thu, Feb 20, 2014 at 07:30:13AM +0100, Robert Baldyga wrote:
>> This patch adds support for deferred gadget driver bind as a remedy
>> for situation when UDC drivers and gadget drivers are builded into
>> the kernel, and gadget driver is loa
48 matches
Mail list logo
