Re: [PATCH 01/17] phy: ti-pipe3: use ti_pipe3_power_off to power off the PHY during probe

On Tue, 23 Jun 2015 17:28:46 +0530 Kishon Vijay Abraham I kis...@ti.com wrote: No functional change. Previously omap_control_phy_power() was used to power off the PHY during probe. But once PIPE3 driver is adapted to use syscon, omap_control_phy_power() cannot be used. Hence used

[PATCH v2] usb: dwc3: pci: make better use of gpiod API

Since 39b2bbe3d715 (gpio: add flags argument to gpiod_get*() functions) which appeared in v3.17-rc1, the gpiod_get* functions take an additional parameter that allows to specify direction and initial value for output. Use this additional parameter and the _optional variant to simplify the driver

Re: [PATCH 02/17] phy: ti-pipe3: use *syscon* framework to power on/off the PHY

Hi Kishon, On Tue, 23 Jun 2015 17:28:47 +0530 Kishon Vijay Abraham I kis...@ti.com wrote: Deprecate using phy-omap-control driver to power on/off the PHY and use *syscon* framework to do the same. Signed-off-by: Kishon Vijay Abraham I kis...@ti.com ---

[PATCH V2 0/5] drivers/rtc/rtc-ds1307.c: Basic cleanups and support for wakeupirq

]. Series is based on next-20150623 Test log: http://pastebin.ubuntu.com/11763002/ NOTE1: I have only tested in mcp79410 device, and not on other ds1307-rtc driver compatbile devices as I dont have any other. additional testing might be nice to have. NOTE2: there are additional fixes that linux-next

[PATCH V2 3/5] drivers/rtc/rtc-ds1307.c: Sort the headers

It is always a good practice to keep the #includes sorted Signed-off-by: Nishanth Menon n...@ti.com --- drivers/rtc/rtc-ds1307.c | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/drivers/rtc/rtc-ds1307.c b/drivers/rtc/rtc-ds1307.c index 0a98d8a52791..b03880fc32b5

[PATCH V2 2/5] drivers/rtc/rtc-ds1307.c: Switch to managed irq allocation

Since we are not doing anything fancy in remove function that requires us to sequence IRQ free operation, we might as well switch over to devm_ equivalent of managed IRQ allocation and remove the explicit free_irq since it'd be done automatically at remove. Signed-off-by: Nishanth Menon

Re: [PATCH] Show proper respect for Heinrich Hertz by using the correct unit for frequency

Hi! The SI unit of frequency is Hertz, named after Heinrich Hertz, and is given the symbol Hz to denote this. hz is not the unit of frequency, and is in fact meaningless. Fix arch/arm to correctly use Hz, thereby acknowledging Heinrich Hertz contribution to the modern world. ---

[TMP PATCH V2 5/5] ARM: dts: am57xx-beagle-x15: Add wakeup irq for mcp79410

With the support in the generic PM framework for wakeirq and capability added to the rtc-ds1307 driver to support this, we can now define the optional wakeup irq to allow the RTC to wakeup the system from low power modes as part of suspend. Signed-off-by: Nishanth Menon n...@ti.com --- Please do

[PATCH V2 4/5] drivers/rtc/rtc-ds1307.c: Support optional wakeup interrupt source

With the recent pinctrl-single changes, SoCs such as Texas Instrument's OMAP processors can treat wake-up events from deeper idle states as interrupts. Let's add support for the optional second interrupt for wake-up using the generic wakeirq support added in commit 4990d4fe327b (PM / Wakeirq: Add

[PATCH V2 1/5] drivers/rtc/rtc-ds1307.c: Convert to threaded IRQ

From: Felipe Balbi ba...@ti.com The driver currently emulates the concept of threaded IRQ using a workqueue, which it really does not need to. Instead, switch over to threaded_irq handlers which is meant precisely for the same purpose. Signed-off-by: Felipe Balbi ba...@ti.com Signed-off-by:

[PATCH 05/17] phy: omap-usb2: Add a new compatible string for USB2 PHY2

The USB2 PHY2 has a different register map compared to USB2 PHY1 to power on/off the PHY. In order to handle it, add a new compatible string. Signed-off-by: Kishon Vijay Abraham I kis...@ti.com --- Documentation/devicetree/bindings/phy/ti-phy.txt |2 ++ drivers/phy/phy-omap-usb2.c

[PATCH 09/17] ARM: dts: dra7: Use syscon-phy-power instead of ctrl-module in SATA PHY node

Add syscon-phy-power property and remove the deprecated ctrl-module property from SATA PHY node. Since omap_control_sata note is no longer used, remove it. Signed-off-by: Kishon Vijay Abraham I kis...@ti.com --- arch/arm/boot/dts/dra7.dtsi | 10 +- 1 file changed, 1 insertion(+), 9

[PATCH 16/17] ARM: dts: omap4: Use syscon-phy-power instead of ctrl-module in USB PHY node

Add syscon-phy-power property and remove the deprecated ctrl-module property from USB PHY dt node. Since omap_control_usb2phy devicetree node is no longer used, remove it. Signed-off-by: Kishon Vijay Abraham I kis...@ti.com --- arch/arm/boot/dts/omap4.dtsi |8 +--- 1 file changed, 1

[PATCH 13/17] ARM: dts: am4372: Use syscon-phy-power instead of ctrl-module in USB PHY node

Add syscon-phy-power property and remove the deprecated ctrl-module property from USB PHY device tree node. Since am43xx_control_usb2phy1 and am43xx_control_usb2phy2 devicetree nodes are no longer used, remove it. Signed-off-by: Kishon Vijay Abraham I kis...@ti.com ---

[PATCH 17/17] ARM: dts: omap4: Use syscon-otghs instead of ctrl-module in USB node

Add syscon-otghs property and remove the deprecated ctrl-module property from MUSB devicetree node. Since omap_control_usbotg devicetree node is no longer used, remove it. Signed-off-by: Kishon Vijay Abraham I kis...@ti.com --- arch/arm/boot/dts/omap4.dtsi |8 +--- 1 file changed, 1

[PATCH 12/17] ARM: dts: dra7: Use syscon-phy-power instead of ctrl-module in USB PHY node

Add syscon-phy-power property and remove the deprecated ctrl-module property from USB PHY devicetree nodes. Since omap_control_usb2phy1, omap_control_usb3phy1 and omap_control_usb2phy2 devicetree nodes are no longer used, remove it. Signed-off-by: Kishon Vijay Abraham I kis...@ti.com ---

[PATCH 15/17] ARM: dts: OMAP5: Use syscon-phy-power instead of ctrl-module in SATA PHY node

Add syscon-phy-power property and remove the deprecated ctrl-module property from SATA PHY node. Since omap_control_sata devicetree node is no longer used, remove it. Signed-off-by: Kishon Vijay Abraham I kis...@ti.com --- arch/arm/boot/dts/omap5.dtsi | 10 +- 1 file changed, 1

[PATCH 08/17] ARM: dts: dra7: Add dt node for the sycon pcie

Add new device tree node for the control module register space where PCIe registers are present. Signed-off-by: Kishon Vijay Abraham I kis...@ti.com --- arch/arm/boot/dts/dra7.dtsi |5 + 1 file changed, 5 insertions(+) diff --git a/arch/arm/boot/dts/dra7.dtsi

[PATCH 14/17] ARM: dts: OMAP5: Use syscon-phy-power instead of ctrl-module in USB PHY node

Add syscon-phy-power property and remove the deprecated ctrl-module property from USB PHY devicetree node. Since omap_control_usb2phy and omap_control_usb3phy devicetree nodes are no longer used, remove it. Signed-off-by: Kishon Vijay Abraham I kis...@ti.com --- arch/arm/boot/dts/omap5.dtsi |

[PATCH 06/17] phy: omap-usb2: use *syscon* framework to power on/off the PHY

Deprecate using phy-omap-control driver to power on/off the PHY, and use *syscon* framework to do the same. This handles powering on/off the PHY for the USB2 PHYs used in various TI SoCs. Signed-off-by: Kishon Vijay Abraham I kis...@ti.com --- Documentation/devicetree/bindings/phy/ti-phy.txt |

[PATCH 02/17] phy: ti-pipe3: use *syscon* framework to power on/off the PHY

Deprecate using phy-omap-control driver to power on/off the PHY and use *syscon* framework to do the same. Signed-off-by: Kishon Vijay Abraham I kis...@ti.com --- Documentation/devicetree/bindings/phy/ti-phy.txt | 10 ++- drivers/phy/phy-ti-pipe3.c | 91

[PATCH 00/17] Deprecate phy-omap-control and use SYSCON

phy-omap-control driver was added when there was no proper infrastructure for doing control module initializations. Now with SYSCON framework being added to the kernel, phy-omap-control shouldn't be needed. This series is about adapting phy-omap-usb2, phy-ti-pipe3 and omap2430 to use SYSCON

[PATCH 11/17] ARM: dts: dra7: Use ti,dra7x-usb2-phy2 compatible string for USB2 PHY2

The USB2 PHY2 has a different register map compared to USB2 PHY1 to power on/off the PHY. In order to handle it, use the new compatible string ti,dra7x-usb2-phy2 for the second instance of USB2 PHY. Signed-off-by: Kishon Vijay Abraham I kis...@ti.com --- arch/arm/boot/dts/dra7.dtsi |2 +- 1

[PATCH 04/17] phy: omap-usb2: use omap_usb_power_off to power off the PHY during probe

No functional change. Previously omap_control_phy_power() was used to power off the PHY during probe. But once phy-omap-usb2 driver is adapted to use syscon, omap_control_phy_power() cannot be used. Hence used omap_usb_power_off to power off the PHY. Signed-off-by: Kishon Vijay Abraham I

[PATCH 10/17] ARM: dts: dra7: Use syscon-phy-power and syscon-pcs in PCIe PHY node

Add syscon-phy-power property and syscon-pcs property which can be used to perform the control module initializations and remove the deprecated ctrl-module property from PCIe PHY dt nodes. Phandle to sysclk clock node is also added to the PCIe PHY node since some of the syscon initializations is

[PATCH 07/17] usb: musb: omap2430: use *syscon* framework to write to mailbox register

Deprecate using phy-omap-control driver to write to the mailbox register and start using *syscon* framework to do the same. Signed-off-by: Kishon Vijay Abraham I kis...@ti.com --- Documentation/devicetree/bindings/usb/omap-usb.txt |7 +- drivers/usb/musb/omap2430.c|

[PATCH 03/17] phy: ti-pipe3: use *syscon* framework to set PCS value of the PHY

Deprecate using phy-omap-control driver to set PCS value of the PHY and start using *syscon* framework to do the same. Signed-off-by: Kishon Vijay Abraham I kis...@ti.com --- Documentation/devicetree/bindings/phy/ti-phy.txt |2 ++ drivers/phy/phy-ti-pipe3.c | 32

[PATCH 01/17] phy: ti-pipe3: use ti_pipe3_power_off to power off the PHY during probe

No functional change. Previously omap_control_phy_power() was used to power off the PHY during probe. But once PIPE3 driver is adapted to use syscon, omap_control_phy_power() cannot be used. Hence used ti_pipe3_power_off to power off the PHY. Signed-off-by: Kishon Vijay Abraham I kis...@ti.com

[PATCH 3/3] ARM: DRA7: hwmod: Fix DCAN1 stuck in transition

Add HWMOD_CLKDM_NOAUTO flag to DCAN1 module. Without this DCAN1 module remains stuck in transition after the CAN interface is brought down. Signed-off-by: Roger Quadros rog...@ti.com --- arch/arm/mach-omap2/omap_hwmod_7xx_data.c | 1 + 1 file changed, 1 insertion(+) diff --git

[PATCH 2/3] ARM: OMAP2+ hwmod: Allow modules to disable HW_AUTO

Introduce HWMOD_CLKDM_NOAUTO flag that allows the hwmod's clockdomain to be prevented from HW_AUTO while the hwmod is active. This is needed to workaround some modules which don't function correctly with HW_AUTO. e.g. DCAN on DRA7. Signed-off-by: Roger Quadros rog...@ti.com ---

[PATCH 1/3] ARM: OMAP2+: clockdomain: Add mechanism for disabling HW_AUTO

For some hwmods (e.g. DCAN on DRA7) we need the possibility to disable HW_AUTO for the clockdomain while the module is active. To achieve this there needs to be a refcounting mechanism to indicate whether any module in the clockdomain has requested to disable HW_AUTO. We keep track of this in

[PATCH 0/3] ARM: OMAP2+: dra7: Fix DCAN1 stuck-in-transition

Hi, On DRA7 platform, DCAN1 module has an issue when it's clockdomain (WKUPAON) is configured in HW_AUTO. After DCAN1 is enabled and disabled the module remains stuck in transition. Suggested workaround by Silicon team is to disable HW_AUTO for WKUPAON clockdomain when DCAN1 module is active.

Re: [Gta04-owner] [PATCH 5/6] phy: twl4030-usb: add support for reading resistor on ID pin.

Hi Neil, Am 01.06.2015 um 23:37 schrieb NeilBrown ne...@suse.de: On Mon, 1 Jun 2015 19:06:52 +0530 Kishon Vijay Abraham I kis...@ti.com wrote: Hi, On Thursday 16 April 2015 01:33 PM, NeilBrown wrote: From: NeilBrown ne...@suse.de The twl4030 phy can measure, with low precision, the

Re: [PATCH] usb: dwc3: pci: make better use of gpiod API

On Fri, Jun 12, 2015 at 09:10:19AM +0200, Uwe Kleine-König wrote: Since 39b2bbe3d715 (gpio: add flags argument to gpiod_get*() functions) which appeared in v3.17-rc1, the gpiod_get* functions take an additional parameter that allows to specify direction and initial value for output.