On Tue, Dec 16, 2014 at 10:50:59AM +0530, Sanchayan Maity wrote:
> On 12/16/2014 06:16 AM, Peter Chen wrote:
> > On Mon, Dec 15, 2014 at 02:59:31PM +0530, Sanchayan Maity wrote:
> >> Hello,
> >>
> >> On 12/15/2014 07:42 AM, Peter Chen wrote:
> >>> On Fri, Dec 12, 2014 at 06:55:36PM +0530, Sanchayan
Greg,
On Mon, Dec 15, 2014 at 08:38:01AM -0800, Greg Kroah-Hartman wrote:
> On Mon, Dec 15, 2014 at 04:53:05AM -0800, Jeremiah Mahler wrote:
> > Johan,
> >
> > On Mon, Dec 15, 2014 at 11:23:21AM +0100, Johan Hovold wrote:
> > > On Thu, Dec 11, 2014 at 03:29:52PM -0800, Jeremiah Mahler wrote:
> >
On 12/16/2014 06:16 AM, Peter Chen wrote:
> On Mon, Dec 15, 2014 at 02:59:31PM +0530, Sanchayan Maity wrote:
>> Hello,
>>
>> On 12/15/2014 07:42 AM, Peter Chen wrote:
>>> On Fri, Dec 12, 2014 at 06:55:36PM +0530, Sanchayan Maity wrote:
Hello,
On 12/12/2014 07:21 AM, Peter Chen wrote:
These patches add support for EHCI and XHCI compliant Host controller found
on Fujitsu Socs, and are based on
http://www.spinics.net/lists/arm-kernel/msg385573.html
First patch is EHCI platform glue driver. Patch 2 introduces Fujitsu
Specific Glue layer in Synopsis DesignWare USB3 IP driver. Patch
This patch adds support for EHCI compliant Host controller found
on Fujitsu Socs.
Signed-off-by: Sneeker Yeh
---
.../devicetree/bindings/usb/fujitsu-ehci.txt | 22 ++
drivers/usb/host/Kconfig | 11 +
drivers/usb/host/Makefile |1 +
This patch adds support for Synopsis DesignWare USB3 IP Core found
on Fujitsu Socs.
Signed-off-by: Sneeker Yeh
---
.../devicetree/bindings/usb/fujitsu-dwc3.txt | 25 +++
drivers/usb/dwc3/Kconfig | 11 ++
drivers/usb/dwc3/Makefile |
Synopsis DesignWare USB3 IP Core integrated with a config-free
phy needs special handling during device disconnection to avoid
the host controller dying.
This quirk makes sure PORT_CSC is cleared after the disable slot
command when usb device is disconnected from internal root hub,
otherwise, Syno
On Mon, Dec 15, 2014 at 02:59:31PM +0530, Sanchayan Maity wrote:
> Hello,
>
> On 12/15/2014 07:42 AM, Peter Chen wrote:
> > On Fri, Dec 12, 2014 at 06:55:36PM +0530, Sanchayan Maity wrote:
> >> Hello,
> >>
> >> On 12/12/2014 07:21 AM, Peter Chen wrote:
> >>> On Thu, Dec 11, 2014 at 08:34:45AM -060
On Mon, Dec 15, 2014 at 6:53 PM, Michael Tessier
wrote:
> Before attempting to upgrade to an earlier kernel driver (this is
> a fairly big amount of work), I would really like to know if this
> problem would still be in the 3.x kernels. Has anyone seen that
> issue in 3.x kernels?
In fact it is
Hi Guys,
*
Issue description
*
I'm having troubles for communication between a NXT - Lego Brick
device (http://www.lego.com/) and a Notebook with USB 3.0.
I'm using a Java development SDK, to build apps and flash the B
On the Renesas R8A7791 SoC based boards there's MAX3355 USB OTG chip and mini-AB
USB connector corresponding to USB port 0 driven either by EHCI/OHCI or Renesas
USBHS gadget controller. And we'd like the host/gadget drivers to work based on
the cable type connected. An 'extcon' driver for MAX3355
On Mon, Dec 15, 2014 at 08:53:20PM +, Michael Tessier wrote:
> <5>Linux version 2.6.31-770-g0e46b52-0897
> (michael.tess...@vsvr-compile-01.pocatec.com) (gcc version 4.1.2) #12 PREEMPT
> Mon Nov 24 18:34:19 EST 2014
That is a _very_ old and obsolete kernel version, you need to get
support fr
Hi,
I am dealing with a USB EHCI driver bug. Here is the info:
My configuration:
-
Host: Freescale i.MX512 with ARM Cortex A8 (USB 2.0 host controller)
Linux kernel: 2.6.31, using EHCI USB driver
Hub: 4-PORT USB 1.1 HUB (Texas Instruments PN: tusb2046b)
Devices: 4 USB 1.1 audio c
Hi Vladimir,
On Mon, Dec 15, 2014 at 6:23 PM, Vladimir Zapolskiy wrote:
> Recently I was told by Mark Brown that this is an incorrect hack --- you
> should either create a regulator consumer or pass "regulator-always-on"
> property.
Exactly, I passed "regulator-always-on" in the official patch
Hi Fabio,
On 15.12.2014 17:05, Fabio Estevam wrote:
> On Tue, Dec 9, 2014 at 11:48 AM, Matthieu CASTET
> wrote:
>
>> Is your usb phy ok ?
>>
>> I saw freeze like that when there was no ulpi communication with the
>> usb phy.
>
> Thanks. I fixed it by passing 'regulator-boot-on' to the USB regul
On Mon, Dec 15, 2014 at 3:32 AM, Hans de Goede wrote:
>
> Code wise this looks good and I've just given:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
>
> a spin with an uas disk enclosure, and verified that tcq is being used,
> and everything works fine.
Thanks for
Yunzhi,
On Fri, Dec 12, 2014 at 7:09 AM, Yunzhi Li wrote:
> Get PHY parameters from devicetree and power off usb PHY during
> system suspend.
>
> Signed-off-by: Yunzhi Li
> Acked-by: Paul Zimmerman
>
> ---
>
> Changes in v7: None
> Changes in v6: None
> Changes in v5: None
> Changes in v4: None
Yunzhi,
On Fri, Dec 12, 2014 at 7:07 AM, Yunzhi Li wrote:
> This patch to add a generic PHY driver for ROCKCHIP usb PHYs,
> currently this driver can support RK3288. The RK3288 SoC have
> three independent USB PHY IPs which are all configured through a
> set of registers located in the GRF (gener
On Mon, 15 Dec 2014 17:22:04 +
David Laight wrote:
> From: Boris Brezillon
> > Hi David,
> >
> > On Mon, 15 Dec 2014 13:34:56 +
> > David Laight wrote:
> >
> > > From: Sergei Shtylyov
> > > > Hello.
> > > >
> > > > On 12/15/2014 4:03 PM, Boris Brezillon wrote:
> > > >
> > > > > Avoid i
1) Summary pasted
summary: scanimage -L finds fitjitsu 04c5:11fc but if repeated does
not find it
+ 04c5:11fc [System76 gazp9b] Excuting scanimage -L finds Fujitsu 6110
+ Scanner but if repeated does not
2) full description:
i plug a fitjitsu 04c5:11fc into a usb2.0 plug
lsusb shows the equip
From: Boris Brezillon
> Hi David,
>
> On Mon, 15 Dec 2014 13:34:56 +
> David Laight wrote:
>
> > From: Sergei Shtylyov
> > > Hello.
> > >
> > > On 12/15/2014 4:03 PM, Boris Brezillon wrote:
> > >
> > > > Avoid interpreting useless status flags when we're not waiting for such
> > > > events b
Hi David,
On Mon, 15 Dec 2014 13:34:56 +
David Laight wrote:
> From: Sergei Shtylyov
> > Hello.
> >
> > On 12/15/2014 4:03 PM, Boris Brezillon wrote:
> >
> > > Avoid interpreting useless status flags when we're not waiting for such
> > > events by masking the status variable with the inter
On Mon, Dec 15, 2014 at 04:53:05AM -0800, Jeremiah Mahler wrote:
> Johan,
>
> On Mon, Dec 15, 2014 at 11:23:21AM +0100, Johan Hovold wrote:
> > On Thu, Dec 11, 2014 at 03:29:52PM -0800, Jeremiah Mahler wrote:
> > > If a USB serial device (e.g. /dev/ttyUSB0) with an active program is
> > > unplugge
On Mon, Dec 15, 2014 at 02:26:29PM +0100, Andreas Herrmann wrote:
> This is a re-submission of patches 2 and 3 from
> http://marc.info/?i=1415914590-31647-1-git-send-email-andreas.herrm...@caviumnetworks.com
> (Only patch 1/3 made it into usb-next and meanwhile is in mainline.)
>
> Please apply.
On Fri, 12 Dec 2014, Robert Baldyga wrote:
> As usb function drivers assumes that all usb request will be completed
> before function unbind call, we should supply such behavior. In some
> cases ep_disable() won't kill all request effectively, because some
> IN requests can be in running state. In
On Mon, Dec 15, 2014 at 3:52 AM, Johan Hovold wrote:
> On Sun, Dec 14, 2014 at 11:51:11AM -0600, George McCollister wrote:
>> Johan,
>>
>> While working on the tx_empty changes you suggested it occurred to me
>> that it might not be obvious to others that the firmware doesn't send
>> a packet with
On Mon, Dec 15, 2014 at 02:28:41PM +0100, Andreas Herrmann wrote:
> Instead rely on device tree information for ehci and ohci.
>
> This was suggested with
> http://www.linux-mips.org/archives/linux-mips/2014-05/msg00307.html
Please use the permanent link from that page:
http://www.linux-mips
On 12/11/2014 08:34 PM, Paul Zimmerman wrote:
>> From: Robert Baldyga [mailto:r.bald...@samsung.com]
>> Sent: Tuesday, December 09, 2014 5:42 AM
>>
>> This makes us sure that all requests are completed before we unbind
>> gadget. There are assumptions in gadget API that all requests have to
>> be c
On Tue, Dec 9, 2014 at 11:48 AM, Matthieu CASTET
wrote:
> Is your usb phy ok ?
>
> I saw freeze like that when there was no ulpi communication with the
> usb phy.
Thanks. I fixed it by passing 'regulator-boot-on' to the USB regulators
--- a/arch/arm/boot/dts/imx51-babbage.dts
+++ b/arch/arm/boo
On Mon, 15 Dec 2014 13:34:56 +
David Laight wrote:
> From: Sergei Shtylyov
> > Hello.
> >
> > On 12/15/2014 4:03 PM, Boris Brezillon wrote:
> >
> > > Avoid interpreting useless status flags when we're not waiting for such
> > > events by masking the status variable with the interrupt enable
Instead rely on device tree information for ehci and ohci.
This was suggested with
http://www.linux-mips.org/archives/linux-mips/2014-05/msg00307.html
"The device tree will *always* have correct ehci/ohci clock
configuration, so use it. This allows us to remove a big chunk of
platform conf
From: Sergei Shtylyov
> Hello.
>
> On 12/15/2014 4:03 PM, Boris Brezillon wrote:
>
> > Avoid interpreting useless status flags when we're not waiting for such
> > events by masking the status variable with the interrupt enabled register
> > value.
>
> > Reported-by: Patrice VILCHEZ
> > Signed-o
Hello.
On 12/15/2014 4:03 PM, Boris Brezillon wrote:
Avoid interpreting useless status flags when we're not waiting for such
events by masking the status variable with the interrupt enabled register
value.
Reported-by: Patrice VILCHEZ
Signed-off-by: Boris Brezillon
---
drivers/usb/gadget
ehci-octeon driver used a 64-bit dma_mask. With removal of ehci-octeon
and usage of ehci-platform ehci dma_mask is now limited to 32 bits
(coerced in ehci_platform_probe).
Provide a flag in ehci platform data to allow use of 64 bits for
dma_mask.
Cc: David Daney
Cc: Alex Smith
Cc: Alan Stern
This is a re-submission of patches 2 and 3 from
http://marc.info/?i=1415914590-31647-1-git-send-email-andreas.herrm...@caviumnetworks.com
(Only patch 1/3 made it into usb-next and meanwhile is in mainline.)
Please apply.
Thanks,
Andreas
--
To unsubscribe from this list: send the line "unsubscri
at91sam9g45, at91sam9x5 and sama5 SoCs should not use
"atmel,at91sam9rl-udc" for their USB device compatible property since
this compatible is attached to a specific hardware bug fix.
Signed-off-by: Boris Brezillon
---
arch/arm/boot/dts/at91sam9g45.dtsi | 2 +-
arch/arm/boot/dts/at91sam9x5.dtsi
Avoid interpreting useless status flags when we're not waiting for such
events by masking the status variable with the interrupt enabled register
value.
Reported-by: Patrice VILCHEZ
Signed-off-by: Boris Brezillon
---
drivers/usb/gadget/udc/atmel_usba_udc.c | 6 +-
1 file changed, 5 insertio
at91sam9g45 and at91sam9x5 SoCs have an hardware bug forcing us to
generate a pulse on the BIAS signal on "USB end of reset” and
“USB end of resume" events.
Reported-by: Patrice VILCHEZ
Signed-off-by: Boris Brezillon
---
drivers/usb/gadget/udc/atmel_usba_udc.c | 28 +++-
Hello,
Here is a set of patches porting existing at91sam9rl erratum handling to
DT and adding new code to handle at91sam9g45/9x5 erratum.
It also adds several compatible strings to differentiate those errata.
These patches should be backported to 3.17 and 3.18 stable releases but
they do not appl
at91sam9rl SoC has an erratum forcing us to toggle the BIAS on USB
suspend/resume events.
This specific handling is only activated when CONFIG_ARCH_AT91SAM9RL is
set and this option is only set when building a non-DT kernel, which is
problematic since non-DT support for at91sam9rl SoC has been rem
On Mon, Dec 15, 2014 at 1:50 PM, Andrzej Pietrasiewicz
wrote:
> A maximum value which fits in 16 bits, unsigned, is 65535.
>
> Signed-off-by: Andrzej Pietrasiewicz
Acked-by: Geert Uytterhoeven
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux bey
Johan,
On Mon, Dec 15, 2014 at 11:23:21AM +0100, Johan Hovold wrote:
> On Thu, Dec 11, 2014 at 03:29:52PM -0800, Jeremiah Mahler wrote:
> > If a USB serial device (e.g. /dev/ttyUSB0) with an active program is
> > unplugged, a bunch of -ENODEV and -EPROTO errors will be produced in the
> > logs. T
A maximum value which fits in 16 bits, unsigned, is 65535.
Signed-off-by: Andrzej Pietrasiewicz
---
drivers/usb/gadget/function/f_hid.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/gadget/function/f_hid.c
b/drivers/usb/gadget/function/f_hid.c
index 488ac66..00
On Thu, Dec 11, 2014 at 03:02:31PM +0200, Octavian Purdila wrote:
> Without suspend/resume functionality in the USB driver the USB core
> will disconnect and reconnect the DLN2 port and because the GPIO
> framework does not yet support removal of an in-use controller a
> suspend/resume operation wi
Hi Linus,
On 15-12-14 00:06, Linus Torvalds wrote:
On Sun, Dec 14, 2014 at 2:35 PM, Greg KH wrote:
Hans de Goede (1):
uas: Make uas work with blk-mq
So I got some fairly trivial conflicts on this one (conflicting with
the scsi cleanups mainly by Christoph Hellwig.
I resolved the con
On Mon, Dec 15, 2014 at 12:06 AM, Linux Kernel Mailing List
wrote:
> Gitweb:
> http://git.kernel.org/linus/;a=commit;h=21a9476a7ba847e413bf1c144d7c614532aed6dd
> Commit: 21a9476a7ba847e413bf1c144d7c614532aed6dd
> Parent: 5ca8d3ec9970f4798e68bd21a9d44db3d0ff4da7
> Refname:refs/head
On Thu, Dec 11, 2014 at 03:29:52PM -0800, Jeremiah Mahler wrote:
> If a USB serial device (e.g. /dev/ttyUSB0) with an active program is
> unplugged, a bunch of -ENODEV and -EPROTO errors will be produced in the
> logs. This patch set quiets these messages without changing the
> original behavior.
On Sat, Dec 13, 2014 at 05:17:42PM +0530, Muthu Mani wrote:
> Adds support for USB-I2C/GPIO interfaces of Cypress Semiconductor
> CYUSBS234 USB-Serial Bridge controller.
>
> Details about the device can be found at:
> http://www.cypress.com/?rID=84126
>
> Separate cell drivers are available for I
On 12/15/2014 06:13 AM, Peter Chen wrote:
> On Fri, Dec 12, 2014 at 02:17:28PM +0100, Robert Baldyga wrote:
>> As usb function drivers assumes that all usb request will be completed
>> before function unbind call, we should supply such behavior. In some
>> cases ep_disable() won't kill all request
On Sun, Dec 14, 2014 at 11:51:11AM -0600, George McCollister wrote:
> Johan,
>
> While working on the tx_empty changes you suggested it occurred to me
> that it might not be obvious to others that the firmware doesn't send
> a packet with the NT124_CTRL_TXEMPTY flag cleared when it begins
> transm
On 12/12/14 17:08, Fabio Estevam wrote:
> From: Fabio Estevam
>
> Since bd27fa44e13830d2b ("usb: phy: generic: Don't use regulator framework for
> RESET line") we no longer model the reset line as a regulator supply, so
> adapt the documentation accordingly.
It seems that the description of vcc
On Fri, Dec 12, 2014 at 09:01:03AM -0600, George McCollister wrote:
> On Wed, Dec 10, 2014 at 7:04 AM, Johan Hovold wrote:
> > On Mon, Dec 08, 2014 at 05:24:17PM -0600, George McCollister wrote:
> >> + switch (termios->c_cflag & CSIZE) {
> >
> > C_CSIZE(tty)
> Okay
> >
> >> + case CS5:
>
Hello,
On 12/15/2014 07:42 AM, Peter Chen wrote:
> On Fri, Dec 12, 2014 at 06:55:36PM +0530, Sanchayan Maity wrote:
>> Hello,
>>
>> On 12/12/2014 07:21 AM, Peter Chen wrote:
>>> On Thu, Dec 11, 2014 at 08:34:45AM -0600, Felipe Balbi wrote:
Hi,
On Thu, Dec 11, 2014 at 04:08:43PM +053
53 matches
Mail list logo
