The newer SoCs (rk3366, rk3399) of Rock-chip take a different usb-phy
IP block than rk3288 and before, and most of phy-related registers are
also different from the past, so a new phy driver is required necessarily.
These series patches add phy-rockchip-inno-usb2.c and the corresponding
documentat
Signed-off-by: Frank Wang
---
Changes in v2:
- Changed vbus_host optional property from gpio to regulator.
- Specified vbus_otg-supply optional property.
- Specified otg_id and otg_bvalid property.
.../bindings/phy/phy-rockchip-inno-usb2.txt| 55
1 file changed
The newer SoCs (rk3366, rk3399) take a different usb-phy IP block
than rk3288 and before, and most of phy-related registers are also
different from the past, so a new phy driver is required necessarily.
Signed-off-by: Frank Wang
---
Changes in v2:
- Changed vbus_host operation from gpio to regu
Hi,
Nathael Pajani writes:
> From: Nathael Pajani
> Date: Wed, 1 Jun 2016 20:35:50 +0200
> Subject: [PATCH 1/1] usb: Add SMSC/Microchip USB2514 HUB support.
>
> Add SMSC/Microchip USB2514 HUB support.
> Hub configuration made through I2C from host instead of external EEPROM.
> Signed-off-by: Na
John Youn writes:
> On 5/30/2016 4:46 AM, Felipe Balbi wrote:
>> We don't need this IRQ anymore.
>>
>> Signed-off-by: Felipe Balbi
>> ---
>> drivers/usb/dwc3/gadget.c | 6 --
>> 1 file changed, 4 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/usb/dwc3/gadget.c b/drivers/usb/dwc3/
On 06/01/2016 11:24 PM, Oliver Neukum wrote:
On Wed, 2016-06-01 at 06:34 -0700, Guenter Roeck wrote:
The class code would not explicitly learn about the reset,
but it would be informed about the exited modes.
That has drawbacks
Playing devils advocate a bit here
- it doesn't tell you what
Hi,
John Youn writes:
>>> However, I'm not aware of any issue with END_TRANSFER, could you let
>>> me know how to reproduce it?
>>
>> it's a rare and difficult bug to reproduce. If you take my testing/next
>> (I didn't check if it happens with v4.7-rc1) - $subject and keep large
>> mass storage
On Wed, 2016-06-01 at 16:29 -0700, Guenter Roeck wrote:
> On Wed, Jun 01, 2016 at 11:26:09AM +0200, Oliver Neukum wrote:
> > On Thu, 2016-05-19 at 15:44 +0300, Heikki Krogerus wrote:
> > > Just noticed that the "active" file is for now read only, but it needs
> > > to be changed to writable. That f
On Wed, 2016-06-01 at 06:34 -0700, Guenter Roeck wrote:
> The class code would not explicitly learn about the reset,
> but it would be informed about the exited modes.
That has drawbacks
- it doesn't tell you what caused the mode to be left (if you
UFP, it may be the regular command)
- it is a
Mario Limonciello [mailto:mario_limoncie...@dell.com]
[...]
> static int set_ethernet_addr(struct r8152 *tp)
> {
> struct net_device *dev = tp->netdev;
> @@ -1041,6 +1075,9 @@ static int set_ethernet_addr(struct r8152 *tp)
> else
> ret = pla_ocp_read(tp, PLA_BACKUP, 8, s
On 5/31/2016 11:52 PM, Felipe Balbi wrote:
>
> Hi,
>
> John Youn writes:
>> On 5/30/2016 7:19 AM, Felipe Balbi wrote:
>>> Instead of looping through all endpoints when
>>> enabling ep0, let's allow for each endpoint to set
>>> its own xfer resource. This solves an issue which
>>> happens when we
On 5/31/2016 11:52 PM, Felipe Balbi wrote:
>
> Hi,
>
> John Youn writes:
>> On 5/30/2016 7:19 AM, Felipe Balbi wrote:
>>> Instead of looping through all endpoints when
>>> enabling ep0, let's allow for each endpoint to set
>>> its own xfer resource. This solves an issue which
>>> happens when we
On 5/30/2016 4:46 AM, Felipe Balbi wrote:
> We don't need this IRQ anymore.
>
> Signed-off-by: Felipe Balbi
> ---
> drivers/usb/dwc3/gadget.c | 6 --
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/usb/dwc3/gadget.c b/drivers/usb/dwc3/gadget.c
> index 7a0c787cecdd
Hi,
> From: Mathias Nyman
> Sent: Wednesday, June 01, 2016 8:42 PM
>
> >>> isn't the following enough?
> >>>
> >>> @@ -4886,7 +4886,7 @@ int xhci_gen_setup(struct usb_hcd *hcd,
> >>> xhci_get_quirks_t get_quirks)
> >>> xhci->hcc_params2 = readl(&xhci->cap_regs->hcc_params2);
>
Hi Heiko,
On 06/02/2016 07:46 AM, Heiko Stübner wrote:
Hi Frank,
Am Dienstag, 31. Mai 2016, 14:40:11 schrieb Frank Wang:
The newer SoCs (rk3366, rk3399) take a different usb-phy IP block
than rk3288 and before, and most of phy-related registers are also
different from the past, so a new phy dr
Hi Heiko,
On 06/02/2016 06:17 AM, Heiko Stübner wrote:
Hi Frank,
Am Mittwoch, 1. Juni 2016, 16:09:41 schrieb Frank Wang:
You might want to add the bvalid and id interrupts for the otg phys as
well
already - would make handling legacy devicetree files easier. [= if they
get specified later, the
> > +static u8 amac_ascii_to_hex(int c)
> > +{
> > + if (c <= 0x39)
> > + return (u8)(c - 0x30);
> > + else if (c <= 0x46)
> > + return (u8)(c - 0x37);
> > + return (u8)(c - 0x57);
> > +}
>
Sorry forgot to address this.
> We really don't have such a function somewhere
> -Original Message-
> From: Greg KH [mailto:gre...@linuxfoundation.org]
> Sent: Wednesday, June 1, 2016 6:06 PM
> To: Limonciello, Mario
> Cc: hayesw...@realtek.com; LKML ; Netdev
> ; Linux USB ;
> pali.ro...@gmail.com; anthony.w...@canonical.com
> Subject: Re: [PATCH] r8152: Add support
> -Original Message-
> From: Greg KH [mailto:gre...@linuxfoundation.org]
> Sent: Wednesday, June 1, 2016 6:07 PM
> To: Limonciello, Mario
> Cc: and...@lunn.ch; hayesw...@realtek.com; linux-ker...@vger.kernel.org;
> net...@vger.kernel.org; linux-usb@vger.kernel.org; pali.ro...@gmail.com;
>
In some Intel platforms, a single usb port is shared between USB host
and device controller. The shared port is under control of GPIO pins.
This patch adds the support for USB GPIO controlled port mux.
[baolu: removed .owner per platform_no_drv_owner.cocci]
[baolu: extcon usage reviewed by Chanwo
Add support to retrieve fixed voltage configure information through
ACPI interface. This is needed for Intel Bay Trail devices, where a
GPIO is used to control the USB vbus.
Signed-off-by: Lu Baolu
---
drivers/regulator/fixed.c | 46 ++
1 file changed,
Several Intel platforms implement USB dual role by having completely
separate xHCI and dwc3 IPs in PCH or SOC silicons. These two IPs share
a single USB port. There is another external port mux which controls
where the data lines should go. While the USB controllers are part of
the silicon, the por
Intel SOC chips are featured with USB dual role. The host role
is provided by Intel xHCI IP, and the gadget role is provided
by IP from designware. Tablet platform designs always share a
single port for both host and gadget controllers. There is a
mux to switch the port to the right controller acc
Some Intel platforms have an USB port mux controlled by GPIOs.
There's a single ACPI platform device that provides 1) USB ID
extcon device; 2) USB vbus regulator device; and 3) USB port
switch device. This MFD driver will split these 3 devices for
their respective drivers.
[baolu: removed .owner p
Several Intel PCHs and SOCs have an internal mux that is used to
share one USB port between device controller and host controller.
The mux is handled through the Dual Role Configuration Register.
Signed-off-by: Heikki Krogerus
Signed-off-by: Lu Baolu
Signed-off-by: Wu Hao
Reviewed-by: Felipe Ba
Add a maintainer entry for Intel USB dual role mux drivers and
add myself as a maintainer.
Signed-off-by: Lu Baolu
---
MAINTAINERS | 10 ++
1 file changed, 10 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 7304d2e..56a98d2 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -6111,
In some Intel platforms, a single usb port is shared between USB host
and device controllers. The shared port is under control of a switch
which is defined in the Intel vendor defined extended capability for
xHCI.
This patch adds the support to detect and create the platform device
for the port mu
On Wed, Jun 01, 2016 at 11:16:34AM -0700, Stephen Boyd wrote:
> Quoting Peter Chen (2016-06-01 05:05:20)
> > On Wed, Jun 01, 2016 at 01:57:23AM -0700, Stephen Boyd wrote:
> > > Quoting Krzysztof Kozlowski (2016-06-01 01:02:18)
> > > > Parse usb-pwrseq property from Device Tree to get the phandle to
Hi Frank,
Am Dienstag, 31. Mai 2016, 14:40:11 schrieb Frank Wang:
> The newer SoCs (rk3366, rk3399) take a different usb-phy IP block
> than rk3288 and before, and most of phy-related registers are also
> different from the past, so a new phy driver is required necessarily.
>
> Signed-off-by: Fra
On Wed, Jun 01, 2016 at 11:26:09AM +0200, Oliver Neukum wrote:
> On Thu, 2016-05-19 at 15:44 +0300, Heikki Krogerus wrote:
> > Just noticed that the "active" file is for now read only, but it needs
> > to be changed to writable. That file will of course provide means for
> > the userspace to Exit a
On Wed, Jun 01, 2016 at 10:31:52PM +, mario_limoncie...@dell.com wrote:
> > -Original Message-
> > From: Andrew Lunn [mailto:and...@lunn.ch]
> > Sent: Wednesday, June 1, 2016 5:27 PM
> > To: Limonciello, Mario
> > Cc: hayesw...@realtek.com; LKML ; Netdev
> > ; Linux USB ;
> > pali.ro..
On Wed, Jun 01, 2016 at 04:50:44PM -0500, Mario Limonciello wrote:
> Dell systems with Type-C ports have support for a persistent system
> specific MAC address when used with Dell Type-C docks and dongles.
> This means a dock plugged into two different systems will show different
> (but persistent)
> -Original Message-
> From: Andrew Lunn [mailto:and...@lunn.ch]
> Sent: Wednesday, June 1, 2016 5:27 PM
> To: Limonciello, Mario
> Cc: hayesw...@realtek.com; LKML ; Netdev
> ; Linux USB ;
> pali.ro...@gmail.com; anthony.w...@canonical.com
> Subject: Re: [PATCH] r8152: Add support for sett
On Wed, Jun 01, 2016 at 04:50:44PM -0500, Mario Limonciello wrote:
> Dell systems with Type-C ports have support for a persistent system
> specific MAC address when used with Dell Type-C docks and dongles.
> This means a dock plugged into two different systems will show different
> (but persistent)
Hi Frank,
Am Mittwoch, 1. Juni 2016, 16:09:41 schrieb Frank Wang:
> > You might want to add the bvalid and id interrupts for the otg phys as
> > well
> > already - would make handling legacy devicetree files easier. [= if they
> > get specified later, the driver would always need to also handle
>
On Tue, May 31, 2016 at 1:40 AM, Frank Wang wrote:
> Signed-off-by: Frank Wang
Please resend to DT list.
> ---
> .../bindings/phy/phy-rockchip-inno-usb2.txt| 48
>
> 1 file changed, 48 insertions(+)
> create mode 100644
> Documentation/devicetree/bindings/phy/
Dell systems with Type-C ports have support for a persistent system
specific MAC address when used with Dell Type-C docks and dongles.
This means a dock plugged into two different systems will show different
(but persistent) MAC addresses. Dell Type-C docks and dongles use the
r8152 driver.
This
On Wed, Jun 01, 2016 at 04:32:12PM +0300, Felipe Balbi wrote:
>
> Hi Greg,
>
> here's the first round of fixes for current -rc. Patches have been
> tested with Intel platforms I have around.
>
> cheers
>
> The following changes since commit 1a695a905c18548062509178b98bc91e67510864:
>
> Linux
On Wed, Jun 01, 2016 at 09:33:02PM +0200, Nathael Pajani wrote:
> Hi !
>
> On 01/06/2016 20:43, Greg KH wrote:
> > On Wed, Jun 01, 2016 at 08:35:50PM +0200, Nathael Pajani wrote:
> >> From: Nathael Pajani
> >> Date: Wed, 1 Jun 2016 20:35:50 +0200
> >> Subject: [PATCH 1/1] usb: Add SMSC/Microchip
I am looking for someone near
Golden Valley, Minneapolis, who can perform a small task for myself.
The issue involves:
* getting a 4 GB Micro SD Card
* copying a predefined image onto it using linux "dd" command
* this can easily be done with a USB SD Card writer
* delivering the SD card to my
Hi !
On 01/06/2016 20:43, Greg KH wrote:
> On Wed, Jun 01, 2016 at 08:35:50PM +0200, Nathael Pajani wrote:
>> From: Nathael Pajani
>> Date: Wed, 1 Jun 2016 20:35:50 +0200
>> Subject: [PATCH 1/1] usb: Add SMSC/Microchip USB2514 HUB support.
>
> Why is this here in the body of the email?
Because
Hi,
On 01-06-16 21:03, Greg Kroah-Hartman wrote:
On Wed, Jun 01, 2016 at 09:01:29PM +0200, Hans de Goede wrote:
I got one of these cards for testing uas with, it seems that with streams
it dma-s all over the place, corrupting memory. On my first tests it
managed to dma over the BIOS of the moth
On Wed, Jun 01, 2016 at 09:01:29PM +0200, Hans de Goede wrote:
> I got one of these cards for testing uas with, it seems that with streams
> it dma-s all over the place, corrupting memory. On my first tests it
> managed to dma over the BIOS of the motherboard somehow and completely
> bricked it.
O
I got one of these cards for testing uas with, it seems that with streams
it dma-s all over the place, corrupting memory. On my first tests it
managed to dma over the BIOS of the motherboard somehow and completely
bricked it.
Tests on another motherboard show that it does work with streams disable
On Wed, Jun 01, 2016 at 08:35:50PM +0200, Nathael Pajani wrote:
> +/*
> + * Driver for SMSC USB2514 USB 2.0 hub controller driver
> + *
> + * Copyright (c) 2012-2013 Dongjin Kim (tobet...@gmail.com)
> + * Copyright (c) 2016 Nathael Pajani (nathael.paj...@ed3l.fr)
> + *
> + * This program is free so
On Wed, Jun 01, 2016 at 08:35:50PM +0200, Nathael Pajani wrote:
> From: Nathael Pajani
> Date: Wed, 1 Jun 2016 20:35:50 +0200
> Subject: [PATCH 1/1] usb: Add SMSC/Microchip USB2514 HUB support.
Why is this here in the body of the email?
>
> Add SMSC/Microchip USB2514 HUB support.
> Hub configur
Hi Martin,
On Wed, Jun 01, 2016 at 02:55:03PM +0200, Martin Kepplinger wrote:
> This adds a driver for the Pegasus Notetaker Pen. When connected,
> this uses the Pen as an input tablet.
>
> This device was sold in various different brandings, for example
> "Pegasus Mobile Notetaker M210",
>
From: Nathael Pajani
Date: Wed, 1 Jun 2016 20:35:50 +0200
Subject: [PATCH 1/1] usb: Add SMSC/Microchip USB2514 HUB support.
Add SMSC/Microchip USB2514 HUB support.
Hub configuration made through I2C from host instead of external EEPROM.
Signed-off-by: Nathael Pajani
---
The following patch adds
Quoting Peter Chen (2016-06-01 05:05:20)
> On Wed, Jun 01, 2016 at 01:57:23AM -0700, Stephen Boyd wrote:
> > Quoting Krzysztof Kozlowski (2016-06-01 01:02:18)
> > > Parse usb-pwrseq property from Device Tree to get the phandle to pwrseq
> > > device. The pwrseq device will be used by USB hub to cy
On Wed, Jun 01, 2016 at 06:32:13PM +0200, Nathael Pajani wrote:
> Hi !
>
> Linked patch adds a driver for the USB2514 USB2.0 Hub from SMSC/Microchip :
>
> http://www.nathael.org/Data/Domotab/Cape_RCCar/commit-972ddd3
>
> I Tried to support this chip using usb3503 driver
> (drivers/usb/misc/usb3
On Tuesday 19 April 2016 10:26 PM, Alex Henrie wrote:
2016-04-19 10:44 GMT-06:00 Sudip Mukherjee :
On Tuesday 19 April 2016 06:52 AM, Greg KH wrote:
On Mon, Apr 18, 2016 at 06:11:51PM -0600, Alex Henrie wrote:
Hi,
I recently bought an MCS7715 USB-attached parallel port,[1] but there
seem to
Hi !
Linked patch adds a driver for the USB2514 USB2.0 Hub from SMSC/Microchip :
http://www.nathael.org/Data/Domotab/Cape_RCCar/commit-972ddd3
I Tried to support this chip using usb3503 driver (drivers/usb/misc/usb3503.c),
but I2C
communication is different and configuration fails.
Thus I crea
From: Thomas Petazzoni
On some platforms, the clocks might be registered by a platform
driver. When this is the case, the clock platform driver may very well
be probed after xhci-plat, in which case the first probe() invocation
of xhci-plat will receive -EPROBE_DEFER as the return value of
devm_c
From: Gabriel Krisman Bertazi
Under stress occasions some TI devices might not return early when
reading the status register during the quirk invocation of xhci_irq made
by usb_hcd_pci_remove. This means that instead of returning, we end up
handling this interruption in the middle of a shutdown.
If commands timeout we mark them for abortion, then stop the command
ring, and turn the commands to no-ops and finally restart the command
ring.
If the host is working properly the no-op commands will finish and
pending completions are called.
If we notice the host is failing, driver clears the co
Hi Greg
These xhci fixes solve a 4.7-rc1 regression in xhci platform driver
quirks, a couple of pending completion cases during driver unload/host
lockup, and a deferred probe case.
-Mathias
Gabriel Krisman Bertazi (1):
xhci: Cleanup only when releasing primary hcd
Mathias Nyman (2):
xhci:
commit b1c127ae990b ("usb: host: xhci: plat: make use of new methods in
xhci_plat_priv") sets xhci->quirks before calling xhci_gen_setup(), which
will overwrite them.
Don't overwite the quirks, just add the new ones
Fixes: b1c127ae990b ("usb: host: xhci: plat: make use of new methods in
xhci_pla
Add space after that ','.
Signed-off-by: Sandhya Bankar
---
drivers/usb/musb/musbhsdma.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/musb/musbhsdma.h b/drivers/usb/musb/musbhsdma.h
index f7b13fd2..46a2bb9 100644
--- a/drivers/usb/musb/musbhsdma.h
+++ b/drivers
Use sizeof(*qh)instead of sizeof *qh.
Signed-off-by: Sandhya Bankar
---
drivers/usb/musb/musb_host.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/musb/musb_host.c b/drivers/usb/musb/musb_host.c
index 2f8ad7f..72121fe 100644
--- a/drivers/usb/musb/musb_host.c
++
Hi Greg,
here's the first round of fixes for current -rc. Patches have been
tested with Intel platforms I have around.
cheers
The following changes since commit 1a695a905c18548062509178b98bc91e67510864:
Linux 4.7-rc1 (2016-05-29 09:29:24 -0700)
are available in the git repository at:
git
On 06/01/2016 02:04 AM, Oliver Neukum wrote:
On Wed, 2016-06-01 at 11:23 +0300, Heikki Krogerus wrote:
I think we can still add them later if they are still seen as
necessity later on, tough I seriously doubt it. It would not be
ideal, but adding an attribute should not really break anything,
ri
This adds a driver for the Pegasus Notetaker Pen. When connected,
this uses the Pen as an input tablet.
This device was sold in various different brandings, for example
"Pegasus Mobile Notetaker M210",
"Genie e-note The Notetaker",
"Staedtler Digital ballpoint pen 990 01",
On Wed, 2016-06-01 at 08:48 -0400, Sandhya Bankar wrote:
> Use "foo *bar" instead of "foo * bar".
>
> Signed-off-by: Sandhya Bankar
Acked-by: Oliver Neukum
> ---
> drivers/usb/image/microtek.h | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/usb/image/micr
Use "foo *bar" instead of "foo * bar".
Signed-off-by: Sandhya Bankar
---
drivers/usb/image/microtek.h | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/usb/image/microtek.h b/drivers/usb/image/microtek.h
index ccce318..7e32ae7 100644
--- a/drivers/usb/image/microt
On Wed, Jun 01, 2016 at 01:57:23AM -0700, Stephen Boyd wrote:
> Quoting Krzysztof Kozlowski (2016-06-01 01:02:18)
> > Parse usb-pwrseq property from Device Tree to get the phandle to pwrseq
> > device. The pwrseq device will be used by USB hub to cycle the power
> > before activating ports.
> >
>
On Wed, Jun 01, 2016 at 10:02:21AM +0200, Krzysztof Kozlowski wrote:
> On Odroid U3 (Exynos4412-based) board if USB was initialized by
> bootloader (in U-Boot "usb start" before tftpboot), the HUB (usb3503)
> and LAN (smsc95xx) after after successful probing were not visible in the
> system ("lsusb
Hi,
On Tue, 2016-05-31 at 14:07 +0300, Sergei Shtylyov wrote:
> Hello.
>
> On 5/31/2016 8:52 AM, Chunfeng Yun wrote:
>
> >
> > Signed-off-by: Chunfeng Yun
> > ---
> > .../devicetree/bindings/usb/mt8173-xhci.txt| 48
> >
> > 1 file changed, 48 insertions(+)
> >
>
isn't the following enough?
@@ -4886,7 +4886,7 @@ int xhci_gen_setup(struct usb_hcd *hcd, xhci_get_quirks_t
get_quirks)
xhci->hcc_params2 = readl(&xhci->cap_regs->hcc_params2);
xhci_print_registers(xhci);
- xhci->quirks = quirks;
+ xhci->quirks |= quirks;
On Thu, 2016-05-19 at 15:44 +0300, Heikki Krogerus wrote:
> Just noticed that the "active" file is for now read only, but it needs
> to be changed to writable. That file will of course provide means for
> the userspace to Exit and Enter modes. But please note that the
> responsibility of the depend
On Wed, 2016-06-01 at 11:23 +0300, Heikki Krogerus wrote:
> I think we can still add them later if they are still seen as
> necessity later on, tough I seriously doubt it. It would not be
> ideal, but adding an attribute should not really break anything,
> right? Removing would.
However, how do we
On 06/01/2016 10:57 AM, Stephen Boyd wrote:
> Quoting Krzysztof Kozlowski (2016-06-01 01:02:18)
>> Parse usb-pwrseq property from Device Tree to get the phandle to pwrseq
>> device. The pwrseq device will be used by USB hub to cycle the power
>> before activating ports.
>>
>> Signed-off-by: Krzysz
Dear Sergei,
On 05/27/2016 07:54 PM, Sergei Shtylyov wrote:
Hello.
On 5/27/2016 2:31 PM, William Wu wrote:
This patch documents the device tree documentation required for
Documents the documentation? :-)
Ah, my commit log seems a little weird. I'll corrcet it next patch.
Thanks.:-)
R
On Wed, 2016-06-01 at 11:23 +0300, Heikki Krogerus wrote:
> On Tue, May 31, 2016 at 10:20:34AM -0700, Guenter Roeck wrote:
> > On Tue, May 31, 2016 at 03:43:56PM +0300, Heikki Krogerus wrote:
> > > On Tue, May 31, 2016 at 03:09:01PM +0300, Heikki Krogerus wrote:
> > > > On Tue, May 31, 2016 at 10:4
Quoting Krzysztof Kozlowski (2016-06-01 01:02:18)
> Parse usb-pwrseq property from Device Tree to get the phandle to pwrseq
> device. The pwrseq device will be used by USB hub to cycle the power
> before activating ports.
>
> Signed-off-by: Krzysztof Kozlowski
Drive by review comment.
I was ho
On Tue, May 31, 2016 at 10:20:34AM -0700, Guenter Roeck wrote:
> On Tue, May 31, 2016 at 03:43:56PM +0300, Heikki Krogerus wrote:
> > On Tue, May 31, 2016 at 03:09:01PM +0300, Heikki Krogerus wrote:
> > > On Tue, May 31, 2016 at 10:48:29AM +0200, Oliver Neukum wrote:
> > > > On Tue, 2016-05-31 at 1
Before moving pwrseq drivers from drivers/mmc/core/ to drivers/power/,
they were maintained by Ulf Hansson.
Signed-off-by: Krzysztof Kozlowski
Reviewed-by: Javier Martinez Canillas
---
MAINTAINERS | 9 +
1 file changed, 9 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 4f2a7
The "mmc" prefix is no longer needed after moving the pwrseq core code
from mmc/ to power/.
Signed-off-by: Krzysztof Kozlowski
Reviewed-by: Javier Martinez Canillas
---
drivers/power/pwrseq/pwrseq.c| 18 +-
drivers/power/pwrseq/pwrseq_emmc.c | 8
drivers/powe
Hi,
My third approach for a USB power sequence which fixes usb3503+lan
on Odroid U3 board if it was initialized by bootloader
(e.g. for TFTP boot).
Changes since v2
1. Add Javier's reviewed-by tags. Address some comments.
2. Re-use existing properties for GPIOs etc by pwrseq-si
Allow build testing for power sequence drivers.
Signed-off-by: Krzysztof Kozlowski
Reviewed-by: Javier Martinez Canillas
---
drivers/power/pwrseq/Kconfig | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/power/pwrseq/Kconfig b/drivers/power/pwrseq/Kconfig
index 7ec
Hi Heiko,
On 05/31/2016 05:02 PM, Heiko Stübner wrote:
Hi Frank,
Am Dienstag, 31. Mai 2016, 14:40:10 schrieb Frank Wang:
Signed-off-by: Frank Wang
---
.../bindings/phy/phy-rockchip-inno-usb2.txt| 48
1 file changed, 48 insertions(+)
create mode 100644
Documen
Some devices need real hard-reset by cutting the power. During power
sequence turn off and on the regulator, if it is provided.
Additionally add support for instantiating the pwrseq-simple device on a
generic property 'power-sequence'. The device will attach itself to the
node containing the pro
The autodetection of attached USB device might not work on certain
boards where the power is delivered externally. These devices also might
require a hard reset. Use pwrseq for that in USB hub.
Signed-off-by: Krzysztof Kozlowski
---
drivers/usb/core/hub.c | 10 ++
1 file changed, 10 in
Hi,
Roger Quadros writes:
> Implementations might use different IRQs for
> host, gadget and OTG so use named interrupt resources
> to allow Device tree to specify the 3 interrupts.
>
> Following are the interrupt names
>
> Peripheral Interrupt - peripheral
> HOST Interrupt - host
> OTG Interrupt
The MMC power sequence drivers are useful also outside of MMC world: for
USB devices needed a hard-reset before probing. Before extending and
re-using pwrseq drivers, move them to a new place.
The commit does not introduce significant changes in the pwrseq drivers
code so still all the functions a
On Odroid U3 (Exynos4412-based) board if USB was initialized by
bootloader (in U-Boot "usb start" before tftpboot), the HUB (usb3503)
and LAN (smsc95xx) after after successful probing were not visible in the
system ("lsusb").
In such case the devices had to be fully reset before configuring.
Reset
Switch the control of buck8 to GPIO mode. It is faster than I2C/register
mode and it is the easiest way to disable it (regulator state is a
logical OR state of GPIO and register value).
Signed-off-by: Krzysztof Kozlowski
Reviewed-by: Javier Martinez Canillas
---
arch/arm/boot/dts/exynos4412-odr
Some USB devices on embedded boards have external power supply which has
to be reset in certain conditions. Add pwrseq interface for this.
Signed-off-by: Krzysztof Kozlowski
---
drivers/power/pwrseq/pwrseq.c | 47 ++-
include/linux/pwrseq.h| 11 +++
Add support for deferred probing to the usb hub. Currently EPROBE_DEFER
does not exist in usb hub path but future patches will add it on the
port level.
Signed-off-by: Krzysztof Kozlowski
Reviewed-by: Javier Martinez Canillas
---
drivers/usb/core/hub.c | 6 --
1 file changed, 4 insertions(
Parse usb-pwrseq property from Device Tree to get the phandle to pwrseq
device. The pwrseq device will be used by USB hub to cycle the power
before activating ports.
Signed-off-by: Krzysztof Kozlowski
---
drivers/usb/core/hub.h | 3 +++
drivers/usb/core/port.c | 15 +++
2 files ch
The power sequence hooks (mmc_pwrseq_pre_power_on(),
mmc_pwrseq_post_power_on() and mmc_pwrseq_power_off()) can be made more
generic to allow re-use in other subsystems. They do not need to take
pointer to struct mmc_host but instead the struct pwrseq should be
sufficient.
Remove the "mmc" prefix
Hi,
Yoshihiro Shimoda writes:
>> From: Felipe Balbi
>> Sent: Wednesday, June 01, 2016 4:01 PM
>>
>> Yoshihiro Shimoda writes:
>>
>> > I'm afraid but I found a regression of xhci-rcar in v4.7-rc1.
>> > This regression is caused by the following commit:
>> >
>> > commit b1c127ae990bccf0187d741c
Hi Felipe,
> From: Felipe Balbi
> Sent: Wednesday, June 01, 2016 4:01 PM
>
> Yoshihiro Shimoda writes:
>
> > I'm afraid but I found a regression of xhci-rcar in v4.7-rc1.
> > This regression is caused by the following commit:
> >
> > commit b1c127ae990bccf0187d741c1695a61e54de1943
> > Author: F
Implementations might use different IRQs for
host, gadget and OTG so use named interrupt resources
to allow Device tree to specify the 3 interrupts.
Following are the interrupt names
Peripheral Interrupt - peripheral
HOST Interrupt - host
OTG Interrupt - otg
We still maintain backward compatibil
On Fri, May 13, 2016 at 01:03:27PM +0300, Roger Quadros wrote:
> @@ -530,6 +683,8 @@ void usb_del_gadget_udc(struct usb_gadget *gadget)
> }
> mutex_unlock(&udc_lock);
>
> + mutex_unlock(&udc_lock);
> +
Here, you have one more mutex_unlock.
Peter
> kobject_uevent(&udc->dev.
The driver should clean up after itself by unpreparing the clock when it
is unbound.
Signed-off-by: Krzysztof Kozlowski
Reviewed-by: Javier Martinez Canillas
---
Changes since v1:
1. Add Javier's tag.
2. Follow Javier's suggestion - the 'hub' cannot be null now.
---
drivers/usb/misc/usb3503.c
Driver supports two paths of device instantiation: as platform and i2c
device. In the platform path it lacks of storing the driver specific
structure as drvdata.
Signed-off-by: Krzysztof Kozlowski
---
Changes since v1:
1. New patch.
---
drivers/usb/misc/usb3503.c | 1 +
1 file changed, 1 inser
Yoshihiro Shimoda writes:
> I'm afraid but I found a regression of xhci-rcar in v4.7-rc1.
> This regression is caused by the following commit:
>
> commit b1c127ae990bccf0187d741c1695a61e54de1943
> Author: Felipe Balbi
> Date: Fri Apr 22 13:17:16 2016 +0300
>
> usb: host: xhci: plat: make u
Alan Stern writes:
> On Tue, 31 May 2016, Felipe Balbi wrote:
>
>> I've sprinkled a few trace_printk() around in g_mass_storage and got
>> some extra info. So here's a good transfer:
>
> ...
>
>> And here's the bad case (with the last working WRITE_10):
>>
>> > irq/17-dwc3-1336 [000] d... 839
98 matches
Mail list logo
