In big endian cases, macro cpu_to_le16 unfolds to __swab16 which
provides special case for constants. In little endian cases,
__constant_cpu_to_le16 and cpu_to_le16 expand directly to the
same expression. So, replace __constant_cpu_to_le16 with
cpu_to_le16 with the goal of getting rid of the defini
On Fri, Jun 5, 2015 at 2:58 PM, Maciej S. Szmigiero
wrote:
> That was a good lead, I've looked at imx6qdl-udoo.dtsi definition of usbh1
> USB host
> device and it overrides clock property from imx6qdl.dtsi (USBOH3) with a
> clock that is
> used to drive on-board USB hub.
>
> After commenting ou
Hi,
>>> I got some untested and not yet reviewed usb3 resume race fixes from Zhuang
>>> Jin Can
>>> If you can try them out and see if they help it would be great.
>>> They are sitting in a topic branch called "xhci_usb3_pm_fixes" in my tree:
>>> (5 extra patches on top of current usb-linus)
>>>
Hi,
On Fri, Jun 05, 2015 at 10:09:03PM +0200, Pali Rohár wrote:
> On Friday 29 May 2015 18:57:06 Felipe Balbi wrote:
> > All right, I tried merging it and it added build breaks to the tree.
> > I'll wait for another version for v4.3 merge window.
> >
> > cheers
>
> Hello, version below compiles
On Fri, 5 Jun 2015, Mark Hills wrote:
> On Fri, 5 Jun 2015, Alan Stern wrote:
>
> > On Fri, 5 Jun 2015, Mark Hills wrote:
> >
> > > I have a new USB 3.0 hard drive which appears to be throttled at
> > > approx 5Mbyte/sec.
> > >
> > > Is there a mystery kernel option that is required to enable
On Friday 29 May 2015 18:57:06 Felipe Balbi wrote:
> All right, I tried merging it and it added build breaks to the tree.
> I'll wait for another version for v4.3 merge window.
>
> cheers
Hello, version below compiles fine on top of linus tree. Please apply:
diff --git a/drivers/usb/gadget/legac
Hi Felipe and Kishon,
This musb-sunxi / phy-sun4i-usb series adds supports for the otg and
host usb-phys found on newer sunxi SoCs and for the musb ip found on
newer sunxi SoCs. This series sits on top of the 2 still outstanding
musb-sunxi / phy-sun4i-usb patches.
These patches (and the 2 still
We can cleanly handle this inside the sunxi glue, instead of adding special
casing to the core, but setting ep0 addr to 0 on a reset interrupt.
Signed-off-by: Hans de Goede
---
drivers/usb/musb/musb_core.h| 1 -
drivers/usb/musb/musb_gadget.c | 6 --
drivers/usb/musb/musb_virthub.c | 6
The A31 SoC uses the same musb controller as found in earlier SoCs, but it
is hooked up slightly different. Its SRAM is private and no longer controlled
through the SRAM controller, and its reset is controlled via a separate
reset controller. This commit adds support for this setup.
Signed-off-by:
The A33 SoC uses the same musb controller as found on the A31 and later,
but allwinner has removed the configdata register, this commit adds special
handling for this.
Signed-off-by: Hans de Goede
---
.../devicetree/bindings/usb/allwinner,sun4i-a10-musb.txt | 3 ++-
drivers/usb/musb/sunxi.c
On some boards we cannot detect the presence of an external Vusb, because
e.g. the 5V of the otg connector is directly connected to the 5V of the board,
and thus is always high.
This commit adds support for using such boards by only looking at the
id-detection pin.
Signed-off-by: Hans de Goede
-
Before this commit the code for determining the disconnect threshold was
checking for "allwinner,sun4i-a10-usb-phy" or "allwinner,sun6i-a31-usb-phy"
assuming that those where the exception and then newer SoCs would use a
disconnect threshold of 2 like sun7i does. But it turns out that newer
SoCs us
The usb-phys on the sun8i-a23 SoC have the same setup wrt clocks as on the
sun6i-a31 SoC, but there are only 2 instead of 3 like on the sun5i-a13 SoC.
Signed-off-by: Hans de Goede
---
Documentation/devicetree/bindings/phy/sun4i-usb-phy.txt | 2 ++
drivers/phy/phy-sun4i-usb.c
The usb-phys on the sun8i-a33 SoC are mostly the same as sun8i-a23 but for
some reason (hw bug?) the phyctl register was moved to a different address
and is not initialized to 0 on reset.
Signed-off-by: Hans de Goede
---
.../devicetree/bindings/phy/sun4i-usb-phy.txt | 1 +
drivers/phy/phy-
On Fri, 5 Jun 2015, Alan Stern wrote:
> On Fri, 5 Jun 2015, Mark Hills wrote:
>
> > I have a new USB 3.0 hard drive which appears to be throttled at
> > approx 5Mbyte/sec.
> >
> > Is there a mystery kernel option that is required to enable full
> > performance on these new drives?
> >
> > I h
W dniu 05.06.2015 05:38, Peter Chen pisze:
> On Fri, Jun 05, 2015 at 12:12:19AM +0200, Maciej S. Szmigiero wrote:
>> Hi Peter,
>>
>>> All imx usb controller's non core registers uses the same clock gate with
>>> core registers, the usbmisc_imx is the library for imx glue driver, the
>>> glue keeps
On Fri, Jun 05, 2015 at 04:34:54PM +0200, Valentin Longchamp wrote:
> Hello,
>
> I am currently bringing up the USB 2.0 Host controller of the Bobcat's
> (98DX4122
> Marvell switch) internal kirkwood CPU on a variation of Keymile's km_kirwood
> hardware (kirkwood-km_kirkwood.dts).
>
> When the d
On Fri, 5 Jun 2015, Mark Hills wrote:
> I have a new USB 3.0 hard drive which appears to be throttled at
> approx 5Mbyte/sec.
>
> Is there a mystery kernel option that is required to enable full
> performance on these new drives?
>
> I have tried changing following:
>
> * Switching onboard US
Hello,
I am currently bringing up the USB 2.0 Host controller of the Bobcat's (98DX4122
Marvell switch) internal kirkwood CPU on a variation of Keymile's km_kirwood
hardware (kirkwood-km_kirkwood.dts).
When the driver registers its hcd, it fails with a timemout as it can be seen in
the below log:
On Fri, Jun 05, 2015 at 03:32:37PM +0200, Johan Hovold wrote:
> Hi Greg,
>
> Here are two new device ids for 4.1 (unless you prefer to wait until
> 4.2-rc1).
>
> Thanks,
> Johan
>
>
> The following changes since commit e26081808edadfd257c6c9d81014e3b25e9a6118:
>
> Linux 4.1-rc4 (2015-05-18 1
This series fixes 3 sources of sleep while atomic bugs. Including the
one reported by Heiko Stuebner here:
http://www.spinics.net/lists/linux-usb/msg125186.html
Please review.
Thank you,
Best regards,
Yousaf
Mian Yousaf Kaukab (3):
usb: dwc2: host: allocate qh before atomic enqueue
usb: dwc
Register backup function can be called from atomic context. Instead
of using atomic memory pool, embed backup storage space in
struct dwc2_hsotg.
Also add a valid flag in each struct as NULL pointer can't be used as
the content validity check any more.
Signed-off-by: Mian Yousaf Kaukab
---
driv
To avoid sleep while atomic bugs, allocate qtd before calling
dwc2_hcd_urb_enqueue. No need to pass mem_flags to
dwc2_hcd_urb_enqueue any more as no memory allocations are done in it.
Signed-off-by: Mian Yousaf Kaukab
---
drivers/usb/dwc2/hcd.c | 26 --
1 file changed, 16
To avoid sleep while atomic bugs, allocate qh before calling
dwc2_hcd_urb_enqueue. qh pointer can be used directly now instead of
passing ep->hcpriv as double pointer.
Signed-off-by: Mian Yousaf Kaukab
---
drivers/usb/dwc2/hcd.c | 31 ++
drivers/usb/dwc2/hcd.h
On Fri, Jun 05, 2015 at 03:29:39PM +0200, Johan Hovold wrote:
> The following changes since commit e26081808edadfd257c6c9d81014e3b25e9a6118:
>
> Linux 4.1-rc4 (2015-05-18 10:13:47 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/johan/usb-s
Hi Greg,
Here are two new device ids for 4.1 (unless you prefer to wait until
4.2-rc1).
Thanks,
Johan
The following changes since commit e26081808edadfd257c6c9d81014e3b25e9a6118:
Linux 4.1-rc4 (2015-05-18 10:13:47 -0700)
are available in the git repository at:
git://git.kernel.org/pub/sc
The following changes since commit e26081808edadfd257c6c9d81014e3b25e9a6118:
Linux 4.1-rc4 (2015-05-18 10:13:47 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/johan/usb-serial.git
tags/usb-serial-4.2-rc1
for you to fetch changes up to f05b7cb6f
I have a new USB 3.0 hard drive which appears to be throttled at
approx 5Mbyte/sec.
Is there a mystery kernel option that is required to enable full
performance on these new drives?
I have tried changing following:
* Switching onboard USB 2.0 interfaces for a completely new USB 3.0
interfac
On Fri, Jun 05, 2015 at 10:37:07AM +0300, Ivan T. Ivanov wrote:
>
> On Fri, 2015-06-05 at 15:03 +0800, Peter Chen wrote:
> > On Tue, Jun 02, 2015 at 04:14:33PM +0300, Ivan T. Ivanov wrote:
> > > On recent Qualcomm platforms VBUS and ID lines are not routed to
> > > USB PHY LINK controller. Use ext
This patch set handles storage thread in error case.
Sanjay Singh Rawat (2):
usb: gadget: f_mass_storage: stop thread in bind failure case
usb: gadget: f_mass_storage: defer storage thread wakeup
drivers/usb/gadget/function/f_mass_storage.c | 12
1 file changed, 8 insertions(+),
As the bind configuration is not complete during thread
creation, defering the thread wake to end of bind.
Signed-off-by: Sanjay Singh Rawat
---
drivers/usb/gadget/function/f_mass_storage.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/usb/gadget/function/f_mas
After the worker thread is launched, bind function is doing further
configuration. In case of failure stop the thread.
Signed-off-by: Sanjay Singh Rawat
---
drivers/usb/gadget/function/f_mass_storage.c | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/drivers/usb/gadget/
32 matches
Mail list logo
