From: Roger Quadros <hidden> Date: 2013-09-24 08:54:39
Hi,
Modelling the RESET line as a regulator supply wasn't a good idea
as it abuses the regulator framework and makes adaptation
code/data more complex.
Instead, manage the RESET gpio line directly in the driver.
This also makes us easy to migrate to a dedicated GPIO RESET controller
whenever it becomes available.
Apart from RESET line changes this series also adds USB host support
fro beagle-xm and fixes USB OTG port on beagle.
The full series is avilable at
git://github.com/rogerq/linux.git
in branch
phy-reset
*NOTE:* As there are changes to platform data, Patch 1 needs to be shared
between the arm-soc tree and usb tree.
Patch 1 is available at repo
git://github.com/rogerq/linux.git
in branch
phy-reset-common
Patch 2 contains the phy-nop driver changes
Patches 3 and 4 adapt legacy boot code to the phy-nop driver changes.
Patches 5, 6 and 7 adapt DT data to the binding changes.
Patch 8 is cleanup of omap3-beagle DT.
Patch 9 adds USB host support to omap3-beagle-xm using the new binding.
Patch 10 fixes USB OTG port on beagle.
Patches are based on v3.12-rc1
Tested leacy boot on omap3-beagle and omap3-beagle-xm
Tested DT boot on omap3-beagle, omap3-beagle-xm and omap4-panda-es
v3:
- Fix the Initial state of RESET line at probe time.
- Update hsusb3_reset line on omap5-uevm as well.
- Add patch 10 that fixes USB OTG port on beagle.
v2:
- Added RESET GPIO polarity feature
- Changed to gpio_set_value_cansleep()
cheers,
-roger
Roger Quadros (10):
usb: phy: generic: Add gpio_reset to platform data
usb: phy: generic: Don't use regulator framework for RESET line
ARM: OMAP2+: omap-usb-host: Get rid of platform_data from struct
usbhs_phy_data
ARM: OMAP2+: usb-host: Adapt to USB phy-nop RESET line changes
ARM: dts: omap3-beagle: Use reset-gpios for hsusb2_reset
ARM: dts: omap4-panda: Use reset-gpios for hsusb1_reset
ARM: dts: omap5-uevm: Use reset-gpios for hsusb2/3_reset
ARM: dts: omap3-beagle: Make USB host pin naming consistent
ARM: dts: omap3-beagle-xm: Add USB Host support
ARM: dts: omap3-beagle: Add USB OTG PHY details
.../devicetree/bindings/usb/usb-nop-xceiv.txt | 7 +-
arch/arm/boot/dts/omap3-beagle-xm.dts | 65 +++++++++++++--
arch/arm/boot/dts/omap3-beagle.dts | 44 +++++------
arch/arm/boot/dts/omap4-panda-common.dtsi | 18 +----
arch/arm/boot/dts/omap5-uevm.dts | 26 +------
arch/arm/mach-omap2/board-omap3beagle.c | 6 --
arch/arm/mach-omap2/usb-host.c | 18 ++--
arch/arm/mach-omap2/usb.h | 1 -
drivers/usb/phy/phy-am335x.c | 2 +-
drivers/usb/phy/phy-generic.c | 84 +++++++++++++-------
drivers/usb/phy/phy-generic.h | 6 +-
include/linux/usb/usb_phy_gen_xceiv.h | 3 +-
12 files changed, 153 insertions(+), 127 deletions(-)
--
1.7.4.1
From: Roger Quadros <hidden> Date: 2013-09-24 08:54:38
The GPIO number of the RESET line can be passed to the
driver using the gpio_reset member.
Signed-off-by: Roger Quadros <redacted>
---
include/linux/usb/usb_phy_gen_xceiv.h | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
@@ -9,7 +9,8 @@ struct usb_phy_gen_xceiv_platform_data {/* if set fails with -EPROBE_DEFER if can't get regulator */unsignedintneeds_vcc:1;-unsignedintneeds_reset:1;+unsignedintneeds_reset:1;/* deprecated */+intgpio_reset;};#if IS_ENABLED(CONFIG_NOP_USB_XCEIV)
From: Roger Quadros <hidden> Date: 2013-09-24 08:54:45
We no longer need to model the RESET line as a regulator since
the USB phy-nop driver accepts "reset-gpios" property.
Signed-off-by: Roger Quadros <redacted>
---
arch/arm/boot/dts/omap3-beagle.dts | 13 +------------
1 files changed, 1 insertions(+), 12 deletions(-)
@@ -44,17 +44,6 @@};};-/* HS USB Port 2 RESET */-hsusb2_reset:hsusb2_reset_reg{-compatible="regulator-fixed";-regulator-name="hsusb2_reset";-regulator-min-microvolt=<3300000>;-regulator-max-microvolt=<3300000>;-gpio=<&gpio5190>;/* gpio_147 */-startup-delay-us=<70000>;-enable-active-high;-};-/* HS USB Port 2 Power */hsusb2_power:hsusb2_power_reg{compatible="regulator-fixed";
@@ -68,7 +57,7 @@/* HS USB Host PHY on PORT 2 */hsusb2_phy:hsusb2_phy{compatible="usb-nop-xceiv";-reset-supply=<&hsusb2_reset>;+reset-gpios=<&gpio519GPIO_ACTIVE_LOW>;/* gpio_147 */vcc-supply=<&hsusb2_power>;};
From: Roger Quadros <hidden> Date: 2013-09-24 08:54:48
The USB phy-nop nop driver expects the RESET line information
to be sent as a GPIO number via platform data. Adapt to that.
Signed-off-by: Roger Quadros <redacted>
---
arch/arm/mach-omap2/usb-host.c | 11 +----------
1 files changed, 1 insertions(+), 10 deletions(-)
@@ -460,8 +460,7 @@ int usbhs_init_phys(struct usbhs_phy_data *phy, int num_phys)memset(&nop_pdata,0,sizeof(nop_pdata));if(gpio_is_valid(phy->vcc_gpio))nop_pdata.needs_vcc=true;-if(gpio_is_valid(phy->reset_gpio))-nop_pdata.needs_reset=true;+nop_pdata.gpio_reset=phy->reset_gpio;nop_pdata.type=USB_PHY_TYPE_USB2;/* create a NOP PHY device */
@@ -483,14 +482,6 @@ int usbhs_init_phys(struct usbhs_phy_data *phy, int num_phys)usb_bind_phy("ehci-omap.0",phy->port-1,phy_id);-/* Do we need RESET regulator ? */-if(gpio_is_valid(phy->reset_gpio)){-scnprintf(rail_name,MAX_STR,-"hsusb%d_reset",phy->port);-usbhs_add_regulator(rail_name,phy_id,"reset",-phy->reset_gpio,1);-}-/* Do we need VCC regulator ? */if(gpio_is_valid(phy->vcc_gpio)){scnprintf(rail_name,MAX_STR,"hsusb%d_vcc",phy->port);
From: Roger Quadros <hidden> Date: 2013-09-24 08:54:49
The platform data bits can be inferred from the other members of
struct usbhs_phy_data. So get rid of the platform_data member.
Build the platform data for the PHY device in usbhs_init_phys() instead.
Signed-off-by: Roger Quadros <redacted>
---
arch/arm/mach-omap2/board-omap3beagle.c | 6 ------
arch/arm/mach-omap2/usb-host.c | 11 ++++++++++-
arch/arm/mach-omap2/usb.h | 1 -
3 files changed, 10 insertions(+), 8 deletions(-)
@@ -289,18 +289,12 @@ static struct regulator_consumer_supply beagle_vsim_supply[] = {staticstructgpio_ledgpio_leds[];-/* PHY's VCC regulator might be added later, so flag that we need it */-staticstructusb_phy_gen_xceiv_platform_datahsusb2_phy_data={-.needs_vcc=true,-};-staticstructusbhs_phy_dataphy_data[]={{.port=2,.reset_gpio=147,.vcc_gpio=-1,/* updated in beagle_twl_gpio_setup */.vcc_polarity=1,/* updated in beagle_twl_gpio_setup */-.platform_data=&hsusb2_phy_data,},};
@@ -435,6 +435,7 @@ int usbhs_init_phys(struct usbhs_phy_data *phy, int num_phys)structplatform_device*pdev;char*phy_id;structplatform_device_infopdevinfo;+structusb_phy_gen_xceiv_platform_datanop_pdata;for(i=0;i<num_phys;i++){
@@ -455,11 +456,19 @@ int usbhs_init_phys(struct usbhs_phy_data *phy, int num_phys)return-ENOMEM;}+/* set platform data */+memset(&nop_pdata,0,sizeof(nop_pdata));+if(gpio_is_valid(phy->vcc_gpio))+nop_pdata.needs_vcc=true;+if(gpio_is_valid(phy->reset_gpio))+nop_pdata.needs_reset=true;+nop_pdata.type=USB_PHY_TYPE_USB2;+/* create a NOP PHY device */memset(&pdevinfo,0,sizeof(pdevinfo));pdevinfo.name=nop_name;pdevinfo.id=phy->port;-pdevinfo.data=phy->platform_data;+pdevinfo.data=&nop_pdata;pdevinfo.size_data=sizeof(structusb_phy_gen_xceiv_platform_data);scnprintf(phy_id,MAX_STR,"usb_phy_gen_xceiv.%d",
From: Roger Quadros <hidden> Date: 2013-09-24 08:54:57
Provide RESET GPIO and Power regulator for the USB PHY,
the USB Host port mode and the PHY device for the controller.
Also provide pin multiplexer information for USB host pins.
We also relocate omap3_pmx_core pin definations so that they
are close to omap3_pmx_wkup pin definations.
Signed-off-by: Roger Quadros <redacted>
---
arch/arm/boot/dts/omap3-beagle-xm.dts | 65 ++++++++++++++++++++++++++++-----
1 files changed, 56 insertions(+), 9 deletions(-)
@@ -69,6 +69,23 @@};};++/* HS USB Port 2 Power */+hsusb2_power:hsusb2_power_reg{+compatible="regulator-fixed";+regulator-name="hsusb2_vbus";+regulator-min-microvolt=<3300000>;+regulator-max-microvolt=<3300000>;+gpio=<&twl_gpio180>;/* GPIO LEDA */+startup-delay-us=<70000>;+};++/* HS USB Host PHY on PORT 2 */+hsusb2_phy:hsusb2_phy{+compatible="usb-nop-xceiv";+reset-gpios=<&gpio519GPIO_ACTIVE_LOW>;/* gpio_147 */+vcc-supply=<&hsusb2_power>;+};};&omap3_pmx_wkup{
From: Roger Quadros <hidden> Date: 2013-09-24 08:54:58
Add information about the USB OTG PHY. Without this
the OTG port on beagle will not work.
Signed-off-by: Roger Quadros <redacted>
---
arch/arm/boot/dts/omap3-beagle.dts | 7 +++++++
1 files changed, 7 insertions(+), 0 deletions(-)
From: Roger Quadros <hidden> Date: 2013-09-24 08:55:31
Use a common naming scheme "mode0name.modename flags" for the
USB host pins to be consistent.
Signed-off-by: Roger Quadros <redacted>
---
arch/arm/boot/dts/omap3-beagle.dts | 24 ++++++++++++------------
1 files changed, 12 insertions(+), 12 deletions(-)
From: Roger Quadros <hidden> Date: 2013-09-24 08:56:41
We no longer need to model the RESET line as a regulator since
the USB phy-nop driver accepts "reset-gpios" property.
Signed-off-by: Roger Quadros <redacted>
---
arch/arm/boot/dts/omap4-panda-common.dtsi | 18 +-----------------
1 files changed, 1 insertions(+), 17 deletions(-)
@@ -60,22 +60,6 @@"AFMR","Line In";};-/*-*Temphack:Needtobereplacedwiththepropergpio-controlled-*resetdriverassoonitwillbemerged.-*http://thread.gmane.org/gmane.linux.drivers.devicetree/36830-*/-/* HS USB Port 1 RESET */-hsusb1_reset:hsusb1_reset_reg{-compatible="regulator-fixed";-regulator-name="hsusb1_reset";-regulator-min-microvolt=<3300000>;-regulator-max-microvolt=<3300000>;-gpio=<&gpio2300>;/* gpio_62 */-startup-delay-us=<70000>;-enable-active-high;-};-/* HS USB Port 1 Power */hsusb1_power:hsusb1_power_reg{compatible="regulator-fixed";
@@ -97,7 +81,7 @@/* HS USB Host PHY on PORT 1 */hsusb1_phy:hsusb1_phy{compatible="usb-nop-xceiv";-reset-supply=<&hsusb1_reset>;+reset-gpios=<&gpio230GPIO_ACTIVE_LOW>;/* gpio_62 */vcc-supply=<&hsusb1_power>;/***FIXME:
From: Roger Quadros <hidden> Date: 2013-09-24 08:57:01
We no longer need to model the RESET line as a regulator since
the USB phy-nop driver accepts "reset-gpios" property.
Signed-off-by: Roger Quadros <redacted>
---
arch/arm/boot/dts/omap5-uevm.dts | 26 ++------------------------
1 files changed, 2 insertions(+), 24 deletions(-)
@@ -27,21 +27,10 @@regulator-max-microvolt=<3000000>;};-/* HS USB Port 2 RESET */-hsusb2_reset:hsusb2_reset_reg{-compatible="regulator-fixed";-regulator-name="hsusb2_reset";-regulator-min-microvolt=<3300000>;-regulator-max-microvolt=<3300000>;-gpio=<&gpio316GPIO_ACTIVE_HIGH>;/* gpio3_80 HUB_NRESET */-startup-delay-us=<70000>;-enable-active-high;-};-/* HS USB Host PHY on PORT 2 */hsusb2_phy:hsusb2_phy{compatible="usb-nop-xceiv";-reset-supply=<&hsusb2_reset>;+reset-gpios=<&gpio316GPIO_ACTIVE_LOW>;/* gpio3_80 HUB_NRESET *//***FIXME*Puttherightclockphandleherewhenavailable
@@ -51,21 +40,10 @@clock-frequency=<19200000>;};-/* HS USB Port 3 RESET */-hsusb3_reset:hsusb3_reset_reg{-compatible="regulator-fixed";-regulator-name="hsusb3_reset";-regulator-min-microvolt=<3300000>;-regulator-max-microvolt=<3300000>;-gpio=<&gpio315GPIO_ACTIVE_HIGH>;/* gpio3_79 ETH_NRESET */-startup-delay-us=<70000>;-enable-active-high;-};-/* HS USB Host PHY on PORT 3 */hsusb3_phy:hsusb3_phy{compatible="usb-nop-xceiv";-reset-supply=<&hsusb3_reset>;+reset-gpios=<&gpio315GPIO_ACTIVE_LOW>;/* gpio3_79 ETH_NRESET */};leds{
From: Roger Quadros <hidden> Date: 2013-09-24 08:57:41
Modelling the RESET line as a regulator supply wasn't a good idea
as it kind of abuses the regulator framework and also makes adaptation
code more complex.
Instead, manage the RESET gpio line directly in the driver. Update
the device tree binding information.
This also makes us easy to migrate to a dedicated GPIO RESET controller
whenever it becomes available.
Signed-off-by: Roger Quadros <redacted>
---
.../devicetree/bindings/usb/usb-nop-xceiv.txt | 7 +-
drivers/usb/phy/phy-am335x.c | 2 +-
drivers/usb/phy/phy-generic.c | 84 +++++++++++++-------
drivers/usb/phy/phy-generic.h | 6 +-
4 files changed, 63 insertions(+), 36 deletions(-)
@@ -15,7 +15,7 @@ Optional properties: - vcc-supply: phandle to the regulator that provides RESET to the PHY.-- reset-supply: phandle to the regulator that provides power to the PHY.+- reset-gpios: Should specify the GPIO for reset. Example:
@@ -25,10 +25,9 @@ Example: clocks = <&osc 0>; clock-names = "main_clk"; vcc-supply = <&hsusb1_vcc_regulator>;- reset-supply = <&hsusb1_reset_regulator>;+ reset-gpios = <&gpio1 7 GPIO_ACTIVE_LOW>; }; hsusb1_phy is a NOP USB PHY device that gets its clock from an oscillator and expects that clock to be configured to 19.2MHz by the NOP PHY driver.-hsusb1_vcc_regulator provides power to the PHY and hsusb1_reset_regulator-controls RESET.+hsusb1_vcc_regulator provides power to the PHY and GPIO 7 controls RESET.
From: Roger Quadros <hidden> Date: 2013-10-02 10:20:13
Hi Tony,
On 09/24/2013 11:53 AM, Roger Quadros wrote:
The platform data bits can be inferred from the other members of
struct usbhs_phy_data. So get rid of the platform_data member.
Build the platform data for the PHY device in usbhs_init_phys() instead.
Signed-off-by: Roger Quadros <redacted>
@@ -289,18 +289,12 @@ static struct regulator_consumer_supply beagle_vsim_supply[] = {staticstructgpio_ledgpio_leds[];-/* PHY's VCC regulator might be added later, so flag that we need it */-staticstructusb_phy_gen_xceiv_platform_datahsusb2_phy_data={-.needs_vcc=true,-};-staticstructusbhs_phy_dataphy_data[]={{.port=2,.reset_gpio=147,.vcc_gpio=-1,/* updated in beagle_twl_gpio_setup */.vcc_polarity=1,/* updated in beagle_twl_gpio_setup */-.platform_data=&hsusb2_phy_data,},};
@@ -435,6 +435,7 @@ int usbhs_init_phys(struct usbhs_phy_data *phy, int num_phys)structplatform_device*pdev;char*phy_id;structplatform_device_infopdevinfo;+structusb_phy_gen_xceiv_platform_datanop_pdata;for(i=0;i<num_phys;i++){
@@ -455,11 +456,19 @@ int usbhs_init_phys(struct usbhs_phy_data *phy, int num_phys)return-ENOMEM;}+/* set platform data */+memset(&nop_pdata,0,sizeof(nop_pdata));+if(gpio_is_valid(phy->vcc_gpio))+nop_pdata.needs_vcc=true;+if(gpio_is_valid(phy->reset_gpio))+nop_pdata.needs_reset=true;+nop_pdata.type=USB_PHY_TYPE_USB2;+/* create a NOP PHY device */memset(&pdevinfo,0,sizeof(pdevinfo));pdevinfo.name=nop_name;pdevinfo.id=phy->port;-pdevinfo.data=phy->platform_data;+pdevinfo.data=&nop_pdata;pdevinfo.size_data=sizeof(structusb_phy_gen_xceiv_platform_data);scnprintf(phy_id,MAX_STR,"usb_phy_gen_xceiv.%d",
From: Roger Quadros <hidden> Date: 2013-10-02 10:20:46
Hi Tony,
On 09/24/2013 11:53 AM, Roger Quadros wrote:
The USB phy-nop nop driver expects the RESET line information
to be sent as a GPIO number via platform data. Adapt to that.
Signed-off-by: Roger Quadros <redacted>
@@ -460,8 +460,7 @@ int usbhs_init_phys(struct usbhs_phy_data *phy, int num_phys)memset(&nop_pdata,0,sizeof(nop_pdata));if(gpio_is_valid(phy->vcc_gpio))nop_pdata.needs_vcc=true;-if(gpio_is_valid(phy->reset_gpio))-nop_pdata.needs_reset=true;+nop_pdata.gpio_reset=phy->reset_gpio;nop_pdata.type=USB_PHY_TYPE_USB2;/* create a NOP PHY device */
@@ -483,14 +482,6 @@ int usbhs_init_phys(struct usbhs_phy_data *phy, int num_phys)usb_bind_phy("ehci-omap.0",phy->port-1,phy_id);-/* Do we need RESET regulator ? */-if(gpio_is_valid(phy->reset_gpio)){-scnprintf(rail_name,MAX_STR,-"hsusb%d_reset",phy->port);-usbhs_add_regulator(rail_name,phy_id,"reset",-phy->reset_gpio,1);-}-/* Do we need VCC regulator ? */if(gpio_is_valid(phy->vcc_gpio)){scnprintf(rail_name,MAX_STR,"hsusb%d_vcc",phy->port);
From: Tony Lindgren <tony@atomide.com> Date: 2013-10-03 04:03:30
* Roger Quadros [off-list ref] [131002 03:27]:
Hi Tony,
On 09/24/2013 11:53 AM, Roger Quadros wrote:
quoted
The platform data bits can be inferred from the other members of
struct usbhs_phy_data. So get rid of the platform_data member.
Build the platform data for the PHY device in usbhs_init_phys() instead.
Signed-off-by: Roger Quadros <redacted>
Could you please Ack this if OK?
This should be OK for you guys to queue. You should coordinate
the .dts changes with Benoit though. It might be best to have
this branch as an immutable branch against -rc3 that we can
all merge in as needed.
For this patch:
Acked-by: Tony Lindgren <tony@atomide.com>
From: Tony Lindgren <tony@atomide.com> Date: 2013-10-03 04:03:58
* Roger Quadros [off-list ref] [131002 03:28]:
Hi Tony,
On 09/24/2013 11:53 AM, Roger Quadros wrote:
quoted
The USB phy-nop nop driver expects the RESET line information
to be sent as a GPIO number via platform data. Adapt to that.
Signed-off-by: Roger Quadros <redacted>
From: Roger Quadros <hidden> Date: 2013-10-03 10:32:48
Hi,
On 09/24/2013 11:53 AM, Roger Quadros wrote:
Hi,
Modelling the RESET line as a regulator supply wasn't a good idea
as it abuses the regulator framework and makes adaptation
code/data more complex.
Instead, manage the RESET gpio line directly in the driver.
This also makes us easy to migrate to a dedicated GPIO RESET controller
whenever it becomes available.
Apart from RESET line changes this series also adds USB host support
fro beagle-xm and fixes USB OTG port on beagle.
The full series is avilable at
git://github.com/rogerq/linux.git
in branch
phy-reset
The branch is now updated based on v3.12-rc3.
cheers,
-roger
*NOTE:* As there are changes to platform data, Patch 1 needs to be shared
between the arm-soc tree and usb tree.
Patch 1 is available at repo
git://github.com/rogerq/linux.git
in branch
phy-reset-common
Patch 2 contains the phy-nop driver changes
Patches 3 and 4 adapt legacy boot code to the phy-nop driver changes.
Patches 5, 6 and 7 adapt DT data to the binding changes.
Patch 8 is cleanup of omap3-beagle DT.
Patch 9 adds USB host support to omap3-beagle-xm using the new binding.
Patch 10 fixes USB OTG port on beagle.
Patches are based on v3.12-rc1
Tested leacy boot on omap3-beagle and omap3-beagle-xm
Tested DT boot on omap3-beagle, omap3-beagle-xm and omap4-panda-es
v3:
- Fix the Initial state of RESET line at probe time.
- Update hsusb3_reset line on omap5-uevm as well.
- Add patch 10 that fixes USB OTG port on beagle.
v2:
- Added RESET GPIO polarity feature
- Changed to gpio_set_value_cansleep()
cheers,
-roger
Roger Quadros (10):
usb: phy: generic: Add gpio_reset to platform data
usb: phy: generic: Don't use regulator framework for RESET line
ARM: OMAP2+: omap-usb-host: Get rid of platform_data from struct
usbhs_phy_data
ARM: OMAP2+: usb-host: Adapt to USB phy-nop RESET line changes
ARM: dts: omap3-beagle: Use reset-gpios for hsusb2_reset
ARM: dts: omap4-panda: Use reset-gpios for hsusb1_reset
ARM: dts: omap5-uevm: Use reset-gpios for hsusb2/3_reset
ARM: dts: omap3-beagle: Make USB host pin naming consistent
ARM: dts: omap3-beagle-xm: Add USB Host support
ARM: dts: omap3-beagle: Add USB OTG PHY details
.../devicetree/bindings/usb/usb-nop-xceiv.txt | 7 +-
arch/arm/boot/dts/omap3-beagle-xm.dts | 65 +++++++++++++--
arch/arm/boot/dts/omap3-beagle.dts | 44 +++++------
arch/arm/boot/dts/omap4-panda-common.dtsi | 18 +----
arch/arm/boot/dts/omap5-uevm.dts | 26 +------
arch/arm/mach-omap2/board-omap3beagle.c | 6 --
arch/arm/mach-omap2/usb-host.c | 18 ++--
arch/arm/mach-omap2/usb.h | 1 -
drivers/usb/phy/phy-am335x.c | 2 +-
drivers/usb/phy/phy-generic.c | 84 +++++++++++++-------
drivers/usb/phy/phy-generic.h | 6 +-
include/linux/usb/usb_phy_gen_xceiv.h | 3 +-
12 files changed, 153 insertions(+), 127 deletions(-)
From: Roger Quadros <hidden> Date: 2013-10-03 10:35:18
Hi Benoit,
Could you please take the device tree related patches [5 to 10] in this series?
Thanks.
cheers,
-roger
On 09/24/2013 11:53 AM, Roger Quadros wrote:
quoted hunk
We no longer need to model the RESET line as a regulator since
the USB phy-nop driver accepts "reset-gpios" property.
Signed-off-by: Roger Quadros <redacted>
---
arch/arm/boot/dts/omap3-beagle.dts | 13 +------------
1 files changed, 1 insertions(+), 12 deletions(-)
@@ -44,17 +44,6 @@};};-/* HS USB Port 2 RESET */-hsusb2_reset:hsusb2_reset_reg{-compatible="regulator-fixed";-regulator-name="hsusb2_reset";-regulator-min-microvolt=<3300000>;-regulator-max-microvolt=<3300000>;-gpio=<&gpio5190>;/* gpio_147 */-startup-delay-us=<70000>;-enable-active-high;-};-/* HS USB Port 2 Power */hsusb2_power:hsusb2_power_reg{compatible="regulator-fixed";
@@ -68,7 +57,7 @@/* HS USB Host PHY on PORT 2 */hsusb2_phy:hsusb2_phy{compatible="usb-nop-xceiv";-reset-supply=<&hsusb2_reset>;+reset-gpios=<&gpio519GPIO_ACTIVE_LOW>;/* gpio_147 */vcc-supply=<&hsusb2_power>;};
Hi Roger,
Yes, I will. I've been waiting for these ones for so long :-)
Thanks,
Benoit
On 03/10/2013 12:34, Roger Quadros wrote:
Hi Benoit,
Could you please take the device tree related patches [5 to 10] in this series?
Thanks.
cheers,
-roger
On 09/24/2013 11:53 AM, Roger Quadros wrote:
quoted
We no longer need to model the RESET line as a regulator since
the USB phy-nop driver accepts "reset-gpios" property.
Signed-off-by: Roger Quadros <redacted>
---
arch/arm/boot/dts/omap3-beagle.dts | 13 +------------
1 files changed, 1 insertions(+), 12 deletions(-)
@@ -44,17 +44,6 @@};};-/* HS USB Port 2 RESET */-hsusb2_reset:hsusb2_reset_reg{-compatible="regulator-fixed";-regulator-name="hsusb2_reset";-regulator-min-microvolt=<3300000>;-regulator-max-microvolt=<3300000>;-gpio=<&gpio5190>;/* gpio_147 */-startup-delay-us=<70000>;-enable-active-high;-};-/* HS USB Port 2 Power */hsusb2_power:hsusb2_power_reg{compatible="regulator-fixed";
@@ -68,7 +57,7 @@/* HS USB Host PHY on PORT 2 */hsusb2_phy:hsusb2_phy{compatible="usb-nop-xceiv";-reset-supply=<&hsusb2_reset>;+reset-gpios=<&gpio519GPIO_ACTIVE_LOW>;/* gpio_147 */vcc-supply=<&hsusb2_power>;};
Hi Roger,
Yes, I will. I've been waiting for these ones for so long :-)
In fact it does not apply correctly on my for_3.13/dts branch :-(
error: arch/arm/boot/dts/omap3-beagle.dts: patch does not apply
Patch failed at 0004 ARM: dts: omap3-beagle: Make USB host pin naming
consistent
Could you rebase it?
Thanks,
Benoit
Thanks,
Benoit
On 03/10/2013 12:34, Roger Quadros wrote:
quoted
Hi Benoit,
Could you please take the device tree related patches [5 to 10] in
this series?
Thanks.
cheers,
-roger
On 09/24/2013 11:53 AM, Roger Quadros wrote:
quoted
We no longer need to model the RESET line as a regulator since
the USB phy-nop driver accepts "reset-gpios" property.
Signed-off-by: Roger Quadros <redacted>
---
arch/arm/boot/dts/omap3-beagle.dts | 13 +------------
1 files changed, 1 insertions(+), 12 deletions(-)
diff --git a/arch/arm/boot/dts/omap3-beagle.dts
b/arch/arm/boot/dts/omap3-beagle.dts
index dfd8310..71bde47 100644
@@ -44,17 +44,6 @@};};-/* HS USB Port 2 RESET */-hsusb2_reset:hsusb2_reset_reg{-compatible="regulator-fixed";-regulator-name="hsusb2_reset";-regulator-min-microvolt=<3300000>;-regulator-max-microvolt=<3300000>;-gpio=<&gpio5190>;/* gpio_147 */-startup-delay-us=<70000>;-enable-active-high;-};-/* HS USB Port 2 Power */hsusb2_power:hsusb2_power_reg{compatible="regulator-fixed";
@@ -68,7 +57,7 @@/* HS USB Host PHY on PORT 2 */hsusb2_phy:hsusb2_phy{compatible="usb-nop-xceiv";-reset-supply=<&hsusb2_reset>;+reset-gpios=<&gpio519GPIO_ACTIVE_LOW>;/* gpio_147 */vcc-supply=<&hsusb2_power>;};
From: Roger Quadros <hidden> Date: 2013-10-03 13:59:24
Hi Benoit,
On 10/03/2013 04:44 PM, Benoit Cousson wrote:
On 03/10/2013 14:05, Benoit Cousson wrote:
quoted
Hi Roger,
Yes, I will. I've been waiting for these ones for so long :-)
In fact it does not apply correctly on my for_3.13/dts branch :-(
error: arch/arm/boot/dts/omap3-beagle.dts: patch does not apply
Patch failed at 0004 ARM: dts: omap3-beagle: Make USB host pin naming consistent
Could you rebase it?
Looks like it was already applied before. Could you please skip that and use the rest?
I've checked that the remaining patches apply fine on top of your for_3.13/dts
branch.
cheers,
-roger
quoted
On 03/10/2013 12:34, Roger Quadros wrote:
quoted
Hi Benoit,
Could you please take the device tree related patches [5 to 10] in
this series?
Thanks.
cheers,
-roger
On 09/24/2013 11:53 AM, Roger Quadros wrote:
quoted
We no longer need to model the RESET line as a regulator since
the USB phy-nop driver accepts "reset-gpios" property.
Signed-off-by: Roger Quadros <redacted>
---
arch/arm/boot/dts/omap3-beagle.dts | 13 +------------
1 files changed, 1 insertions(+), 12 deletions(-)
diff --git a/arch/arm/boot/dts/omap3-beagle.dts
b/arch/arm/boot/dts/omap3-beagle.dts
index dfd8310..71bde47 100644
@@ -44,17 +44,6 @@};};-/* HS USB Port 2 RESET */-hsusb2_reset:hsusb2_reset_reg{-compatible="regulator-fixed";-regulator-name="hsusb2_reset";-regulator-min-microvolt=<3300000>;-regulator-max-microvolt=<3300000>;-gpio=<&gpio5190>;/* gpio_147 */-startup-delay-us=<70000>;-enable-active-high;-};-/* HS USB Port 2 Power */hsusb2_power:hsusb2_power_reg{compatible="regulator-fixed";
@@ -68,7 +57,7 @@/* HS USB Host PHY on PORT 2 */hsusb2_phy:hsusb2_phy{compatible="usb-nop-xceiv";-reset-supply=<&hsusb2_reset>;+reset-gpios=<&gpio519GPIO_ACTIVE_LOW>;/* gpio_147 */vcc-supply=<&hsusb2_power>;};
Hi Benoit,
On 10/03/2013 04:44 PM, Benoit Cousson wrote:
quoted
On 03/10/2013 14:05, Benoit Cousson wrote:
quoted
Hi Roger,
Yes, I will. I've been waiting for these ones for so long :-)
In fact it does not apply correctly on my for_3.13/dts branch :-(
error: arch/arm/boot/dts/omap3-beagle.dts: patch does not apply
Patch failed at 0004 ARM: dts: omap3-beagle: Make USB host pin naming consistent
Could you rebase it?
Looks like it was already applied before. Could you please skip that and use the rest?
I've checked that the remaining patches apply fine on top of your for_3.13/dts
branch.
Indeed, it was already there :-)
Sorry for the noise.
Benoit
cheers,
-roger
quoted
quoted
On 03/10/2013 12:34, Roger Quadros wrote:
quoted
Hi Benoit,
Could you please take the device tree related patches [5 to 10] in
this series?
Thanks.
cheers,
-roger
On 09/24/2013 11:53 AM, Roger Quadros wrote:
quoted
We no longer need to model the RESET line as a regulator since
the USB phy-nop driver accepts "reset-gpios" property.
Signed-off-by: Roger Quadros <redacted>
---
arch/arm/boot/dts/omap3-beagle.dts | 13 +------------
1 files changed, 1 insertions(+), 12 deletions(-)
diff --git a/arch/arm/boot/dts/omap3-beagle.dts
b/arch/arm/boot/dts/omap3-beagle.dts
index dfd8310..71bde47 100644
@@ -44,17 +44,6 @@};};-/* HS USB Port 2 RESET */-hsusb2_reset:hsusb2_reset_reg{-compatible="regulator-fixed";-regulator-name="hsusb2_reset";-regulator-min-microvolt=<3300000>;-regulator-max-microvolt=<3300000>;-gpio=<&gpio5190>;/* gpio_147 */-startup-delay-us=<70000>;-enable-active-high;-};-/* HS USB Port 2 Power */hsusb2_power:hsusb2_power_reg{compatible="regulator-fixed";
@@ -68,7 +57,7 @@/* HS USB Host PHY on PORT 2 */hsusb2_phy:hsusb2_phy{compatible="usb-nop-xceiv";-reset-supply=<&hsusb2_reset>;+reset-gpios=<&gpio519GPIO_ACTIVE_LOW>;/* gpio_147 */vcc-supply=<&hsusb2_power>;};
Provide RESET GPIO and Power regulator for the USB PHY,
the USB Host port mode and the PHY device for the controller.
Also provide pin multiplexer information for USB host pins.
We also relocate omap3_pmx_core pin definations so that they
are close to omap3_pmx_wkup pin definations.
Signed-off-by: Roger Quadros <redacted>
---
just using this thread, but a question ->
I am kernel * master dec8e46 Merge
tag 'arc-v3.13-rc1-part2' of
git://git.kernel.org/pub/scm/linux/kernel/git/vgupta/arc
and I see that VAUX2 which supplies USB_1V8[1] is not enabled -> I did
a quick patch and it did seem to work (Usb keyboard, networking, mouse
etc on my ehci ports seems to come up good) - any suggestions how we'd
like to handle this?
@@ -69,6 +69,23 @@};};++/* HS USB Port 2 Power */+hsusb2_power:hsusb2_power_reg{+compatible="regulator-fixed";+regulator-name="hsusb2_vbus";+regulator-min-microvolt=<3300000>;+regulator-max-microvolt=<3300000>;+gpio=<&twl_gpio180>;/* GPIO LEDA */+startup-delay-us=<70000>;+};++/* HS USB Host PHY on PORT 2 */+hsusb2_phy:hsusb2_phy{+compatible="usb-nop-xceiv";+reset-gpios=<&gpio519GPIO_ACTIVE_LOW>;/* gpio_147 */+vcc-supply=<&hsusb2_power>;+};};&omap3_pmx_wkup{
From: Roger Quadros <hidden> Date: 2013-11-20 10:33:08
Nishant,
On 11/19/2013 11:05 PM, Nishanth Menon wrote:
On 09/24/2013 03:53 AM, Roger Quadros wrote:
quoted
Provide RESET GPIO and Power regulator for the USB PHY,
the USB Host port mode and the PHY device for the controller.
Also provide pin multiplexer information for USB host pins.
We also relocate omap3_pmx_core pin definations so that they
are close to omap3_pmx_wkup pin definations.
Signed-off-by: Roger Quadros <redacted>
---
just using this thread, but a question ->
I am kernel * master dec8e46 Merge
tag 'arc-v3.13-rc1-part2' of
git://git.kernel.org/pub/scm/linux/kernel/git/vgupta/arc
and I see that VAUX2 which supplies USB_1V8[1] is not enabled -> I did
a quick patch and it did seem to work (Usb keyboard, networking, mouse
etc on my ehci ports seems to come up good) - any suggestions how we'd
like to handle this?
It worked for me without your patch. It could be that u-boot is enabling
that regulator for me. I'm on u-boot-v2013.10.
In any case, your patch seems the right thing to do. We should take it in
the rc cycle.
@@ -69,6 +69,23 @@};};++/* HS USB Port 2 Power */+hsusb2_power:hsusb2_power_reg{+compatible="regulator-fixed";+regulator-name="hsusb2_vbus";+regulator-min-microvolt=<3300000>;+regulator-max-microvolt=<3300000>;+gpio=<&twl_gpio180>;/* GPIO LEDA */+startup-delay-us=<70000>;+};++/* HS USB Host PHY on PORT 2 */+hsusb2_phy:hsusb2_phy{+compatible="usb-nop-xceiv";+reset-gpios=<&gpio519GPIO_ACTIVE_LOW>;/* gpio_147 */+vcc-supply=<&hsusb2_power>;+};};&omap3_pmx_wkup{
From: Tony Lindgren <tony@atomide.com> Date: 2013-11-26 21:05:12
* Roger Quadros [off-list ref] [131120 02:33]:
Nishant,
On 11/19/2013 11:05 PM, Nishanth Menon wrote:
quoted
On 09/24/2013 03:53 AM, Roger Quadros wrote:
quoted
Provide RESET GPIO and Power regulator for the USB PHY,
the USB Host port mode and the PHY device for the controller.
Also provide pin multiplexer information for USB host pins.
We also relocate omap3_pmx_core pin definations so that they
are close to omap3_pmx_wkup pin definations.
Signed-off-by: Roger Quadros <redacted>
---
just using this thread, but a question ->
I am kernel * master dec8e46 Merge
tag 'arc-v3.13-rc1-part2' of
git://git.kernel.org/pub/scm/linux/kernel/git/vgupta/arc
and I see that VAUX2 which supplies USB_1V8[1] is not enabled -> I did
a quick patch and it did seem to work (Usb keyboard, networking, mouse
etc on my ehci ports seems to come up good) - any suggestions how we'd
like to handle this?
It worked for me without your patch. It could be that u-boot is enabling
that regulator for me. I'm on u-boot-v2013.10.
In any case, your patch seems the right thing to do. We should take it in
the rc cycle.
Can you guys post a proper fix for this? Meanwhile, I'll mark this
thread as read to shrink my inbox a bit.
Regards,
Tony
On Tue, Nov 26, 2013 at 3:04 PM, Tony Lindgren [off-list ref] wrote:
* Roger Quadros [off-list ref] [131120 02:33]:
quoted
Nishant,
On 11/19/2013 11:05 PM, Nishanth Menon wrote:
quoted
On 09/24/2013 03:53 AM, Roger Quadros wrote:
quoted
Provide RESET GPIO and Power regulator for the USB PHY,
the USB Host port mode and the PHY device for the controller.
Also provide pin multiplexer information for USB host pins.
We also relocate omap3_pmx_core pin definations so that they
are close to omap3_pmx_wkup pin definations.
Signed-off-by: Roger Quadros <redacted>
---
just using this thread, but a question ->
I am kernel * master dec8e46 Merge
tag 'arc-v3.13-rc1-part2' of
git://git.kernel.org/pub/scm/linux/kernel/git/vgupta/arc
and I see that VAUX2 which supplies USB_1V8[1] is not enabled -> I did
a quick patch and it did seem to work (Usb keyboard, networking, mouse
etc on my ehci ports seems to come up good) - any suggestions how we'd
like to handle this?
It worked for me without your patch. It could be that u-boot is enabling
that regulator for me. I'm on u-boot-v2013.10.
In any case, your patch seems the right thing to do. We should take it in
the rc cycle.
Can you guys post a proper fix for this? Meanwhile, I'll mark this
thread as read to shrink my inbox a bit.