[PATCH v2 01/10] phy: qcom-ufs: remove failure when rx/tx_iface_clk are absent

From: Yaniv Gardi <yga...@codeaurora.org> Since in future UFS Phy's the tx_iface_clk and rx_iface_clk are no longer exist, we should not fail when their initialization fail, but rather just report with debug message. Signed-off-by: Yaniv Gardi <yga...@codeaurora.org> Signed-off-by:

[PATCH v2 01/10] phy: qcom-ufs: remove failure when rx/tx_iface_clk are absent

From: Yaniv Gardi Since in future UFS Phy's the tx_iface_clk and rx_iface_clk are no longer exist, we should not fail when their initialization fail, but rather just report with debug message. Signed-off-by: Yaniv Gardi Signed-off-by: Vivek Gautam --- No change since v1. drivers/phy/phy

[PATCH v2 00/10] ufs-qcom: phy/hcd: Clean up qcom-ufs phy and ufs-qcom hcd

ufs_qcom_phy_exit() from 'phy-qcom-ufs' driver, since this api just powers off the phy. [1] https://git.linaro.org/landing-teams/working/qualcomm/kernel.git [2] ufs-qcom: phy/hcd: Refactoring phy clock handling Vivek Gautam (9): phy: qcom-ufs: Remove unnecessary BUG_ON phy: qcom-ufs: Use devm

[PATCH v2 00/10] ufs-qcom: phy/hcd: Clean up qcom-ufs phy and ufs-qcom hcd

ufs_qcom_phy_exit() from 'phy-qcom-ufs' driver, since this api just powers off the phy. [1] https://git.linaro.org/landing-teams/working/qualcomm/kernel.git [2] ufs-qcom: phy/hcd: Refactoring phy clock handling Vivek Gautam (9): phy: qcom-ufs: Remove unnecessary BUG_ON phy: qcom-ufs: Use devm

[PATCH v2 06/10] phy: qcom-ufs: Remove unnecessary function declarations

Move the functions' definitions to remove unnecessary declarations. Signed-off-by: Vivek Gautam <vivek.gau...@codeaurora.org> --- New patch added in v2 series. drivers/phy/phy-qcom-ufs.c | 133 + 1 file changed, 63 insertions(+), 70 del

[PATCH v2 06/10] phy: qcom-ufs: Remove unnecessary function declarations

Move the functions' definitions to remove unnecessary declarations. Signed-off-by: Vivek Gautam --- New patch added in v2 series. drivers/phy/phy-qcom-ufs.c | 133 + 1 file changed, 63 insertions(+), 70 deletions(-) diff --git a/drivers/phy/phy

[PATCH 7/7] ufs-qcom: phy/hcd: Refactoring phy clock handling

Add phy clock enable code to phy_power_on/off callbacks, and remove explicit calls to enable these phy clocks from the ufs-qcom hcd driver. Signed-off-by: Vivek Gautam <vivek.gau...@codeaurora.org> Reviewed-by: Subhash Jadavani <subha...@codeaurora.org> --- drivers/phy/phy-qcom

[PATCH 7/7] ufs-qcom: phy/hcd: Refactoring phy clock handling

Add phy clock enable code to phy_power_on/off callbacks, and remove explicit calls to enable these phy clocks from the ufs-qcom hcd driver. Signed-off-by: Vivek Gautam Reviewed-by: Subhash Jadavani --- drivers/phy/phy-qcom-ufs.c | 12 +++- drivers/scsi/ufs/ufs-qcom.c | 15

[PATCH 6/7] phy: qcom-ufs-qmp-xx: Move clock and regulator init out of phy init

The phy init is meant to do phy initialization rather than just getting the clock and regulator. Move these clock and regulator get to probe(), to make room for actual phy initialization sequence. Signed-off-by: Vivek Gautam <vivek.gau...@codeaurora.org> Reviewed-by: Subhash Jadavani

[PATCH 4/7] phy: qcom-ufs-qmp-xx: Discard remove callback for drivers.

remove() callback does a phy_exit() only and nothing else now. The phy_exit() over the generic phy is called from the phy consumer, and phy provider driver should not explicitly need to call any phy_exit(). So discard the remove callback for qcom-ufs phy platform drivers. Signed-off-by: Vivek

[PATCH 6/7] phy: qcom-ufs-qmp-xx: Move clock and regulator init out of phy init

The phy init is meant to do phy initialization rather than just getting the clock and regulator. Move these clock and regulator get to probe(), to make room for actual phy initialization sequence. Signed-off-by: Vivek Gautam Reviewed-by: Subhash Jadavani --- drivers/phy/phy-qcom-ufs-qmp-14nm.c

[PATCH 4/7] phy: qcom-ufs-qmp-xx: Discard remove callback for drivers.

remove() callback does a phy_exit() only and nothing else now. The phy_exit() over the generic phy is called from the phy consumer, and phy provider driver should not explicitly need to call any phy_exit(). So discard the remove callback for qcom-ufs phy platform drivers. Signed-off-by: Vivek

[PATCH 5/7] phy: qcom-ufs: Cleanup clock and regulator initialization

Different methods pass around generic phy pointer to extract device pointer. Instead, pass the device pointer directly between function calls. Signed-off-by: Vivek Gautam <vivek.gau...@codeaurora.org> Reviewed-by: Subhash Jadavani <subha...@codeaurora.org> --- drivers/phy/phy-

[PATCH 2/7] phy: qcom-ufs: Remove unnecessary BUG_ON

BUG_ON() are not preferred in the driver, plus the variable on which BUG_ON is asserted is already checked in the code before passing. Signed-off-by: Vivek Gautam <vivek.gau...@codeaurora.org> Reviewed-by: Subhash Jadavani <subha...@codeaurora.org> --- drivers/phy/phy-qcom-ufs.c |

[PATCH 3/7] phy: qcom-ufs: Use devm sibling of kstrdup for regulator names

This helps us in avoiding any requirement for kfree() operation to be called exclusively over the allocated string pointer. Signed-off-by: Vivek Gautam <vivek.gau...@codeaurora.org> Reviewed-by: Subhash Jadavani <subha...@codeaurora.org> --- drivers/phy/phy-qcom-ufs.c | 5 + 1

[PATCH 2/7] phy: qcom-ufs: Remove unnecessary BUG_ON

BUG_ON() are not preferred in the driver, plus the variable on which BUG_ON is asserted is already checked in the code before passing. Signed-off-by: Vivek Gautam Reviewed-by: Subhash Jadavani --- drivers/phy/phy-qcom-ufs.c | 2 -- 1 file changed, 2 deletions(-) diff --git a/drivers/phy/phy

[PATCH 3/7] phy: qcom-ufs: Use devm sibling of kstrdup for regulator names

This helps us in avoiding any requirement for kfree() operation to be called exclusively over the allocated string pointer. Signed-off-by: Vivek Gautam Reviewed-by: Subhash Jadavani --- drivers/phy/phy-qcom-ufs.c | 5 + 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/drivers

[PATCH 5/7] phy: qcom-ufs: Cleanup clock and regulator initialization

Different methods pass around generic phy pointer to extract device pointer. Instead, pass the device pointer directly between function calls. Signed-off-by: Vivek Gautam Reviewed-by: Subhash Jadavani --- drivers/phy/phy-qcom-ufs-i.h| 6 +-- drivers/phy/phy-qcom-ufs-qmp-14nm.c | 4

[PATCH 1/7] phy: qcom-ufs: remove failure when rx/tx_iface_clk are absent

From: Yaniv Gardi <yga...@codeaurora.org> Since in future UFS Phy's the tx_iface_clk and rx_iface_clk are no longer exist, we should not fail when their initialization fail, but rather just report with debug message. Signed-off-by: Yaniv Gardi <yga...@codeaurora.org> Signed-off-by:

[PATCH 1/7] phy: qcom-ufs: remove failure when rx/tx_iface_clk are absent

From: Yaniv Gardi Since in future UFS Phy's the tx_iface_clk and rx_iface_clk are no longer exist, we should not fail when their initialization fail, but rather just report with debug message. Signed-off-by: Yaniv Gardi Signed-off-by: Vivek Gautam --- drivers/phy/phy-qcom-ufs.c | 15

[PATCH 0/7] ufs-qcom: phy/hcd: Clean up qcom-ufs phy and ufs-qcom hcd

, and have been tested with on db820c hardware with integration branch - 'integration-linux-qcomlt' of qualcomm linaro lt tree [1]. [1] https://git.linaro.org/landing-teams/working/qualcomm/kernel.git Vivek Gautam (6): phy: qcom-ufs: Remove unnecessary BUG_ON phy: qcom-ufs: Use devm sibling

[PATCH 0/7] ufs-qcom: phy/hcd: Clean up qcom-ufs phy and ufs-qcom hcd

, and have been tested with on db820c hardware with integration branch - 'integration-linux-qcomlt' of qualcomm linaro lt tree [1]. [1] https://git.linaro.org/landing-teams/working/qualcomm/kernel.git Vivek Gautam (6): phy: qcom-ufs: Remove unnecessary BUG_ON phy: qcom-ufs: Use devm sibling

Re: PROBLEM: DWC3 USB 3.0 not working on Odroid-XU4 with Exynos 5422

On 10/17/2016 01:38 PM, Felipe Balbi wrote: Hi, Michael Niewöhner writes: Hi Felipe, On Fri, 2016-10-07 at 22:26 +0200, Michael Niewöhner wrote: Hi Felipe, On Fr, 2016-10-07 at 10:42 +0300, Felipe Balbi wrote: Hi, Michael Niewöhner writes:

Re: PROBLEM: DWC3 USB 3.0 not working on Odroid-XU4 with Exynos 5422

On 10/17/2016 01:38 PM, Felipe Balbi wrote: Hi, Michael Niewöhner writes: Hi Felipe, On Fri, 2016-10-07 at 22:26 +0200, Michael Niewöhner wrote: Hi Felipe, On Fr, 2016-10-07 at 10:42 +0300, Felipe Balbi wrote: Hi, Michael Niewöhner writes: The clocks are same across

Re: [PATCH v3 1/2] phy: Add a driver for simple phy

On 10/13/2016 03:47 AM, Alban wrote: On Fri, 7 Oct 2016 13:57:08 +0530 Vivek Gautam <vivek.gau...@codeaurora.org> wrote: Hi Alban, On Wed, Feb 17, 2016 at 7:51 PM, Alban <al...@free.fr> wrote: On Mon, 1 Feb 2016 17:12:42 +0530 Kishon Vijay Abraham I <kis...@ti.com> wrote

Re: [PATCH v3 1/2] phy: Add a driver for simple phy

On 10/13/2016 03:47 AM, Alban wrote: On Fri, 7 Oct 2016 13:57:08 +0530 Vivek Gautam wrote: Hi Alban, On Wed, Feb 17, 2016 at 7:51 PM, Alban wrote: On Mon, 1 Feb 2016 17:12:42 +0530 Kishon Vijay Abraham I wrote: Hi, On Friday 29 January 2016 01:22 AM, Alban Bedel wrote: This driver

Re: [PATCH v3 1/2] phy: Add a driver for simple phy

Hi Alban, On Wed, Feb 17, 2016 at 7:51 PM, Alban wrote: > On Mon, 1 Feb 2016 17:12:42 +0530 > Kishon Vijay Abraham I wrote: > >> Hi, >> >> On Friday 29 January 2016 01:22 AM, Alban Bedel wrote: >> > This driver is meant to take care of all trivial phys that don't

Re: [PATCH v3 1/2] phy: Add a driver for simple phy

Hi Alban, On Wed, Feb 17, 2016 at 7:51 PM, Alban wrote: > On Mon, 1 Feb 2016 17:12:42 +0530 > Kishon Vijay Abraham I wrote: > >> Hi, >> >> On Friday 29 January 2016 01:22 AM, Alban Bedel wrote: >> > This driver is meant to take care of all trivial phys that don't need >> > any special

Re: [PATCH] phy: nop: Add a new phy driver for No-Op transceiver

Hi Kishon, On 10/05/2016 05:41 PM, Kishon Vijay Abraham I wrote: Hi, On Tuesday 04 October 2016 04:13 PM, Vivek Gautam wrote: No-Op phy transceiver can be used on platforms that have controllers which themselves provide PHY functionality and there's no separate PHY controller available

Re: [PATCH] phy: nop: Add a new phy driver for No-Op transceiver

Hi Kishon, On 10/05/2016 05:41 PM, Kishon Vijay Abraham I wrote: Hi, On Tuesday 04 October 2016 04:13 PM, Vivek Gautam wrote: No-Op phy transceiver can be used on platforms that have controllers which themselves provide PHY functionality and there's no separate PHY controller available

Re: PROBLEM: DWC3 USB 3.0 not working on Odroid-XU4 with Exynos 5422

Hi Anand, On Tue, Oct 4, 2016 at 8:39 PM, Anand Moon wrote: > Hi Vivek, > [snip] > > What I feel is that their need to be some reset of usb phy so that > device are assigned to respective bus ports. The phy resets are what we do in the phy-exynos5-usbdrd driver. In

Re: PROBLEM: DWC3 USB 3.0 not working on Odroid-XU4 with Exynos 5422

Hi Anand, On Tue, Oct 4, 2016 at 8:39 PM, Anand Moon wrote: > Hi Vivek, > [snip] > > What I feel is that their need to be some reset of usb phy so that > device are assigned to respective bus ports. The phy resets are what we do in the phy-exynos5-usbdrd driver. In addition to what we have

Re: PROBLEM: DWC3 USB 3.0 not working on Odroid-XU4 with Exynos 5422

Hi Michael, On Tue, Oct 4, 2016 at 4:28 PM, Michael Niewöhner wrote: > > > > > > [1.] One line summary of the problem: > > > > > > DWC3 USB 3.0 not working on Odroid-XU4 with Exynos 5422 > > > > > > > > > > > > [2.] Full description of the problem/report: > > > > > > No

Re: PROBLEM: DWC3 USB 3.0 not working on Odroid-XU4 with Exynos 5422

Hi Michael, On Tue, Oct 4, 2016 at 4:28 PM, Michael Niewöhner wrote: > > > > > > [1.] One line summary of the problem: > > > > > > DWC3 USB 3.0 not working on Odroid-XU4 with Exynos 5422 > > > > > > > > > > > > [2.] Full description of the problem/report: > > > > > > No usb 3.0 devices are

[PATCH] phy: nop: Add a new phy driver for No-Op transceiver

-generic driver in drivers/usb/phy. Signed-off-by: Vivek Gautam <vivek.gau...@codeaurora.org> Cc: Kishon Vijay Abraham I <kis...@ti.com> Cc: Felipe Balbi <ba...@kernel.org> --- Hi Kishon, Felipe, This patch has been lying in my tree for sometime. This introduces a skeletal no

[PATCH] phy: nop: Add a new phy driver for No-Op transceiver

-generic driver in drivers/usb/phy. Signed-off-by: Vivek Gautam Cc: Kishon Vijay Abraham I Cc: Felipe Balbi --- Hi Kishon, Felipe, This patch has been lying in my tree for sometime. This introduces a skeletal nop-phy driver based on generic phy framework. I mainly use this driver when I have only

Re: PROBLEM: DWC3 USB 3.0 not working on Odroid-XU4 with Exynos 5422

Hi Michael, On Tue, Aug 30, 2016 at 10:32 AM, Anand Moon <linux.am...@gmail.com> wrote: > Hi All > > Adding Vivek Gautam. Sorry for missing out this conversation. I am no longer part of Samsung. > > On 29 August 2016 at 16:35, Michael Niewöhner <li...@mniewoehner.

Re: PROBLEM: DWC3 USB 3.0 not working on Odroid-XU4 with Exynos 5422

Hi Michael, On Tue, Aug 30, 2016 at 10:32 AM, Anand Moon wrote: > Hi All > > Adding Vivek Gautam. Sorry for missing out this conversation. I am no longer part of Samsung. > > On 29 August 2016 at 16:35, Michael Niewöhner wrote: >> Hi Mathias, >> On Mo, 2016-08

Re: [PATCH] clk: Add USB3 PHY reset lines

On Thu, Sep 15, 2016 at 10:15 AM, <vivek.gau...@codeaurora.org> wrote: > From: Vivek Gautam <vivek.gau...@codeaurora.org> a stale "--from " flag in my command added this line. Will take care of it from next time. > > Adding missing reset lines for USB 3.0 PHY.

Re: [PATCH] clk: Add USB3 PHY reset lines

On Thu, Sep 15, 2016 at 10:15 AM, wrote: > From: Vivek Gautam a stale "--from " flag in my command added this line. Will take care of it from next time. > > Adding missing reset lines for USB 3.0 PHY. > > Signed-off-by: Vivek Gautam > --- [snip] -- Qua

[PATCH] clk: Add USB3 PHY reset lines

From: Vivek Gautam <vivek.gau...@codeaurora.org> Adding missing reset lines for USB 3.0 PHY. Signed-off-by: Vivek Gautam <vivek.gau...@codeaurora.org> --- - Build tested on clk-next branch. - Tested with my wip branch for usbphy that is available @[1]. [1]https://github.com/

[PATCH] clk: Add USB3 PHY reset lines

From: Vivek Gautam Adding missing reset lines for USB 3.0 PHY. Signed-off-by: Vivek Gautam --- - Build tested on clk-next branch. - Tested with my wip branch for usbphy that is available @[1]. [1]https://github.com/vivekgautam1/linux/tree/linaro/integration-linux-qcomlt-usbphy-wip

Re: [PATCH v3 21/22] phy: Add support for Qualcomm's USB HSIC phy

On 2016-09-02 03:30, Stephen Boyd wrote: (Please trim replies) sorry, will take care from next time. Quoting Vivek Gautam (2016-08-31 23:17:55) On Thu, Sep 1, 2016 at 6:10 AM, Stephen Boyd <stephen.b...@linaro.org> wrote: > + > + uphy->cal_sleep_clk = clk = de

Re: [PATCH v3 21/22] phy: Add support for Qualcomm's USB HSIC phy

On 2016-09-02 03:30, Stephen Boyd wrote: (Please trim replies) sorry, will take care from next time. Quoting Vivek Gautam (2016-08-31 23:17:55) On Thu, Sep 1, 2016 at 6:10 AM, Stephen Boyd wrote: > + > + uphy->cal_sleep_clk = clk = devm_clk_get(>dev

Re: [PATCH v3 21/22] phy: Add support for Qualcomm's USB HSIC phy

Hi Stephen, On Thu, Sep 1, 2016 at 6:10 AM, Stephen Boyd wrote: > The HSIC USB controller on qcom SoCs has an integrated all > digital phy controlled via the ULPI viewport. > > Cc: Kishon Vijay Abraham I > Cc: >

Re: [PATCH v3 21/22] phy: Add support for Qualcomm's USB HSIC phy

Hi Stephen, On Thu, Sep 1, 2016 at 6:10 AM, Stephen Boyd wrote: > The HSIC USB controller on qcom SoCs has an integrated all > digital phy controlled via the ULPI viewport. > > Cc: Kishon Vijay Abraham I > Cc: > Signed-off-by: Stephen Boyd > --- >

Re: [PATCH v2 2/2] phy: Group vendor specific phy drivers

Hi Kishon, On Thu, Apr 28, 2016 at 10:28 AM, Kishon Vijay Abraham I <kis...@ti.com> wrote: > Hi, > > On Tuesday 26 April 2016 11:36 AM, Vivek Gautam wrote: >> Hi Kishon, >> >> >> On Wed, Apr 6, 2016 at 7:37 PM, Vivek Gautam <gautam.vi...@samsung.

Re: [PATCH v2 2/2] phy: Group vendor specific phy drivers

Hi Kishon, On Thu, Apr 28, 2016 at 10:28 AM, Kishon Vijay Abraham I wrote: > Hi, > > On Tuesday 26 April 2016 11:36 AM, Vivek Gautam wrote: >> Hi Kishon, >> >> >> On Wed, Apr 6, 2016 at 7:37 PM, Vivek Gautam >> wrote: >>> Adding vendor spec

Re: [PATCH v2 2/2] phy: Group vendor specific phy drivers

Hi Kishon, On Wed, Apr 6, 2016 at 7:37 PM, Vivek Gautam <gautam.vi...@samsung.com> wrote: > Adding vendor specific directories in phy to group > phy drivers under their respective vendor umbrella. > > Also updated the MAINTAINERS file to reflect the correct > directory stru

Re: [PATCH v2 2/2] phy: Group vendor specific phy drivers

Hi Kishon, On Wed, Apr 6, 2016 at 7:37 PM, Vivek Gautam wrote: > Adding vendor specific directories in phy to group > phy drivers under their respective vendor umbrella. > > Also updated the MAINTAINERS file to reflect the correct > directory structure for phy drivers. > >

[PATCH v2 2/2] phy: Group vendor specific phy drivers

Adding vendor specific directories in phy to group phy drivers under their respective vendor umbrella. Also updated the MAINTAINERS file to reflect the correct directory structure for phy drivers. Signed-off-by: Vivek Gautam <gautam.vi...@samsung.com> Acked-by: Heiko Stuebner <he...@

[PATCH v2 2/2] phy: Group vendor specific phy drivers

Adding vendor specific directories in phy to group phy drivers under their respective vendor umbrella. Also updated the MAINTAINERS file to reflect the correct directory structure for phy drivers. Signed-off-by: Vivek Gautam Acked-by: Heiko Stuebner Acked-by: Viresh Kumar --- Changes from v1

[PATCH 1/2] phy: Move ULPI phy header out of driver to includes path

Although ULPI phy is currently being used by tusb1210, there can be other consumers too in future. So move this to the includes path for phy. Signed-off-by: Vivek Gautam <gautam.vi...@samsung.com> --- {drivers => include/linux}/phy/ulpi_phy.h | 0 1 file changed, 0 insertions(+), 0

[PATCH 1/2] phy: Move ULPI phy header out of driver to includes path

Although ULPI phy is currently being used by tusb1210, there can be other consumers too in future. So move this to the includes path for phy. Signed-off-by: Vivek Gautam --- {drivers => include/linux}/phy/ulpi_phy.h | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename {driv

Re: [PATCH 1/2] phy: Group vendor specific phy drivers

Hi Kishon, On Wed, Apr 6, 2016 at 5:51 AM, Kishon Vijay Abraham I <kis...@ti.com> wrote: > Hi, > > On Friday 01 April 2016 07:05 PM, Vivek Gautam wrote: >> Hi, >> >> >> On Fri, Apr 1, 2016 at 6:05 AM, Kishon Vijay Abraham I <kis...@ti.com> wrote: >

Re: [PATCH 1/2] phy: Group vendor specific phy drivers

Hi Kishon, On Wed, Apr 6, 2016 at 5:51 AM, Kishon Vijay Abraham I wrote: > Hi, > > On Friday 01 April 2016 07:05 PM, Vivek Gautam wrote: >> Hi, >> >> >> On Fri, Apr 1, 2016 at 6:05 AM, Kishon Vijay Abraham I wrote: >>> Hi, >>> >&

Re: [PATCH 1/2] phy: Group vendor specific phy drivers

elp improving the system] > > url: > https://github.com/0day-ci/linux/commits/Vivek-Gautam/phy-Group-vendor-specific-phy-drivers/20160401-192920 > base: > https://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git > for-next > config: arm-allyesconfig (att

Re: [PATCH 1/2] phy: Group vendor specific phy drivers

t; > url: > https://github.com/0day-ci/linux/commits/Vivek-Gautam/phy-Group-vendor-specific-phy-drivers/20160401-192920 > base: > https://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git > for-next > config: arm-allyesconfig (attached as .confi

Re: [PATCH 1/2] phy: Group vendor specific phy drivers

Hi Krzysztof, On Sat, Apr 2, 2016 at 11:05 PM, Krzysztof Kozlowski <k.kozlow...@samsung.com> wrote: > On Fri, Apr 01, 2016 at 04:59:15PM +0530, Vivek Gautam wrote: >> Adding vendor specific directories in phy to group >> phy drivers under their respective vendor umbre

Re: [PATCH 1/2] phy: Group vendor specific phy drivers

Hi Krzysztof, On Sat, Apr 2, 2016 at 11:05 PM, Krzysztof Kozlowski wrote: > On Fri, Apr 01, 2016 at 04:59:15PM +0530, Vivek Gautam wrote: >> Adding vendor specific directories in phy to group >> phy drivers under their respective vendor umbrella. >> >>

Re: [PATCH 1/2] phy: Group vendor specific phy drivers

Hi, On Fri, Apr 1, 2016 at 6:05 AM, Kishon Vijay Abraham I <kis...@ti.com> wrote: > Hi, > > On Friday 01 April 2016 04:59 PM, Vivek Gautam wrote: >> Adding vendor specific directories in phy to group >> phy drivers under their respective vendor umbrella. >&g

Re: [PATCH 1/2] phy: Group vendor specific phy drivers

Hi, On Fri, Apr 1, 2016 at 6:05 AM, Kishon Vijay Abraham I wrote: > Hi, > > On Friday 01 April 2016 04:59 PM, Vivek Gautam wrote: >> Adding vendor specific directories in phy to group >> phy drivers under their respective vendor umbrella. >> >

Re: [PATCH 1/2] phy: Group vendor specific phy drivers

On Fri, Apr 1, 2016 at 4:39 AM, Viresh Kumar <viresh.ku...@linaro.org> wrote: > On 01-04-16, 16:59, Vivek Gautam wrote: >> Adding vendor specific directories in phy to group >> phy drivers under their respective vendor umbrella. >> >> Signed-off-by: Vivek

Re: [PATCH 1/2] phy: Group vendor specific phy drivers

On Fri, Apr 1, 2016 at 4:39 AM, Viresh Kumar wrote: > On 01-04-16, 16:59, Vivek Gautam wrote: >> Adding vendor specific directories in phy to group >> phy drivers under their respective vendor umbrella. >> >> Signed-off-by: Vivek Gautam >> --- >> dri

Re: [PATCH 1/2] phy: Group vendor specific phy drivers

Hi, On Fri, Apr 1, 2016 at 4:42 AM, Maxime Ripard <maxime.rip...@free-electrons.com> wrote: > Hi, > > On Fri, Apr 01, 2016 at 04:59:15PM +0530, Vivek Gautam wrote: >> create mode 100644 drivers/phy/sunxi/Kconfig >> create mode 100644 drivers/phy/sunxi/Makefile >&g

Re: [PATCH 1/2] phy: Group vendor specific phy drivers

Hi, On Fri, Apr 1, 2016 at 4:42 AM, Maxime Ripard wrote: > Hi, > > On Fri, Apr 01, 2016 at 04:59:15PM +0530, Vivek Gautam wrote: >> create mode 100644 drivers/phy/sunxi/Kconfig >> create mode 100644 drivers/phy/sunxi/Makefile >> rename drivers/phy/{ =&g

[PATCH 1/2] phy: Group vendor specific phy drivers

Adding vendor specific directories in phy to group phy drivers under their respective vendor umbrella. Signed-off-by: Vivek Gautam <gautam.vi...@samsung.com> --- With growing number of phy drivers, it makes sense to group these drivers under their respective vendor/platform umbrella dir

[PATCH 1/2] phy: Group vendor specific phy drivers

Adding vendor specific directories in phy to group phy drivers under their respective vendor umbrella. Signed-off-by: Vivek Gautam --- With growing number of phy drivers, it makes sense to group these drivers under their respective vendor/platform umbrella directory. Build-tested

[PATCH 2/2] arm: mach-spear: Enable PHY_PLAT to meet dependency

mach-spear enables PHY_ST_SPEAR1310_MIPHY and PHY_ST_SPEAR1340_MIPHY, which now fall under PHY_PLAT config. So select CONFIG_PHY_PLAT as well to resolve dependencies. Signed-off-by: Vivek Gautam <gautam.vi...@samsung.com> Cc: Shiraz Hashim <shiraz.linux.ker...@gmail.com> --- arch/ar

[PATCH 2/2] arm: mach-spear: Enable PHY_PLAT to meet dependency

mach-spear enables PHY_ST_SPEAR1310_MIPHY and PHY_ST_SPEAR1340_MIPHY, which now fall under PHY_PLAT config. So select CONFIG_PHY_PLAT as well to resolve dependencies. Signed-off-by: Vivek Gautam Cc: Shiraz Hashim --- arch/arm/mach-spear/Kconfig | 2 ++ 1 file changed, 2 insertions(+) diff

Re: [PATCH v4 1/2] usb: ehci-exynos: Make provision for vdd regulators

Hi, On Mon, Jun 8, 2015 at 8:47 PM, Alan Stern wrote: > On Mon, 8 Jun 2015, Vivek Gautam wrote: > >> Facilitate getting required 3.3V and 1.0V VDD supply for >> EHCI controller on Exynos. >> >> For example, patches for regulators' nodes: >> c8c253f ARM: dt

Re: [PATCH v4 1/2] usb: ehci-exynos: Make provision for vdd regulators

Hi, On Mon, Jun 8, 2015 at 8:47 PM, Alan Stern st...@rowland.harvard.edu wrote: On Mon, 8 Jun 2015, Vivek Gautam wrote: Facilitate getting required 3.3V and 1.0V VDD supply for EHCI controller on Exynos. For example, patches for regulators' nodes: c8c253f ARM: dts: Add regulator entries

[PATCH v4 2/2] usb: ohci-exynos: Make provision for vdd regulators

ensuring now that the controller driver requests the necessary VDD regulators (if available, unless there are direct VDD rails), and enable them so as to make them working on exynos systems. Signed-off-by: Vivek Gautam Cc: Jingoo Han Cc: Krzysztof Kozlowski Cc: Alan Stern --- Changes since v3

[PATCH v4 1/2] usb: ehci-exynos: Make provision for vdd regulators

ensuring now that the controller driver requests the necessary VDD regulators (if available, unless there are direct VDD rails), and enable them so as to make them working on exynos systems. Signed-off-by: Vivek Gautam Cc: Jingoo Han Cc: Krzysztof Kozlowski Cc: Alan Stern --- These patches had

Re: [RESEND 1/2] usb: ehci-exynos: Make provision for vdd regulators

Hi, On Monday, June 08, 2015 3:50 PM, "Anand Moon" On 8 June 2015 at 10:58, Vivek Gautam wrote: Hi, On Monday, June 08, 2015 10:44 AM, "Krzysztof Kozlowski" wrote: my apologies for being late in replying to this thread. 2015-06-08 13:21 GMT+09:00 Anand Moon :

Re: [RESEND 1/2] usb: ehci-exynos: Make provision for vdd regulators

-- From: "Krzysztof Kozlowski" Sent: Monday, June 08, 2015 7:40 AM To: "Anand Moon" ; "Rob Herring" ; "Pawel Moll" ; "Mark Rutland" ; "Ian Campbell" ; "Kumar Gala"

Re: [RESEND 1/2] usb: ehci-exynos: Make provision for vdd regulators

o ensuring now that the controller driver requests the necessary VDD regulators (if available, unless there are direct VDD rails), and enable them so as to make them working. Signed-off-by: Vivek Gautam Signed-off-by: Anand Moon Cc: Jingoo Han Cc: Alan Stern --- Initial version of this patc

Re: [RESEND 1/2] usb: ehci-exynos: Make provision for vdd regulators

Hi, On Monday, June 08, 2015 3:50 PM, Anand Moon linux.am...@gmail.com On 8 June 2015 at 10:58, Vivek Gautam gautam.vi...@samsung.com wrote: Hi, On Monday, June 08, 2015 10:44 AM, Krzysztof Kozlowski k.kozlow...@samsung.com wrote: my apologies for being late in replying to this thread

[PATCH v4 1/2] usb: ehci-exynos: Make provision for vdd regulators

ensuring now that the controller driver requests the necessary VDD regulators (if available, unless there are direct VDD rails), and enable them so as to make them working on exynos systems. Signed-off-by: Vivek Gautam gautam.vi...@samsung.com Cc: Jingoo Han jg1@samsung.com Cc: Krzysztof Kozlowski

[PATCH v4 2/2] usb: ohci-exynos: Make provision for vdd regulators

ensuring now that the controller driver requests the necessary VDD regulators (if available, unless there are direct VDD rails), and enable them so as to make them working on exynos systems. Signed-off-by: Vivek Gautam gautam.vi...@samsung.com Cc: Jingoo Han jg1@samsung.com Cc: Krzysztof Kozlowski

Re: [RESEND 1/2] usb: ehci-exynos: Make provision for vdd regulators

. This was rather bad about these controller drivers. So ensuring now that the controller driver requests the necessary VDD regulators (if available, unless there are direct VDD rails), and enable them so as to make them working. Signed-off-by: Vivek Gautam gautam.vi...@samsung.com Signed-off

Re: [RESEND 1/2] usb: ehci-exynos: Make provision for vdd regulators

+devicet...@hellion.org.uk; Kumar Gala ga...@codeaurora.org; Kukjin Kim kg...@kernel.org; Alan Stern st...@rowland.harvard.edu; Greg Kroah-Hartman gre...@linuxfoundation.org; Vivek Gautam gautam.vi...@samsung.com; Felipe Balbi ba...@ti.com Cc: devicet...@vger.kernel.org; linux-arm-ker

Re: [PATCH v2] Revert "usb: host: ehci-msm: Use devm_ioremap_resource instead of devm_ioremap"

Hi, -- From: "Alan Stern" Sent: Monday, April 27, 2015 8:14 PM To: "Ivan T. Ivanov" Cc: "Greg Kroah-Hartman" ; ; ; ; "Vivek Gautam" Subject: Re: [PATCH v2] Revert "usb: host: ehci-msm: Use

Re: [PATCH v2] Revert usb: host: ehci-msm: Use devm_ioremap_resource instead of devm_ioremap

-...@vger.kernel.org; Vivek Gautam gautam.vi...@samsung.com Subject: Re: [PATCH v2] Revert usb: host: ehci-msm: Use devm_ioremap_resource instead of devm_ioremap On Mon, 27 Apr 2015, Ivan T. Ivanov wrote: This reverts commit 70843f623b58 (usb: host: ehci-msm: Use devm_ioremap_resource instead

Re: [PATCH] Revert "usb: host: ehci-msm: Use devm_ioremap_resource instead of devm_ioremap"

egisters. Cc: Vivek Gautam Since ehci-msm and msm_otg both want to control few USB registers, it makes sense to request ioremap'ed region in both drivers. Acked-by: Vivek Gautam I can see a patch in mailing list for adding both ehci-host and otg on msm [1]. But I think it has not yet made i

Re: [PATCH] Revert usb: host: ehci-msm: Use devm_ioremap_resource instead of devm_ioremap

registers. Cc: Vivek Gautam gautam.vi...@samsung.com Since ehci-msm and msm_otg both want to control few USB registers, it makes sense to request ioremap'ed region in both drivers. Acked-by: Vivek Gautam gautam.vi...@samsung.com I can see a patch in mailing list for adding both ehci-host and otg

Re: [PATCH] usb: ehci-msm: Don't ioremap configuration space exclusively

t;> >> /* >>* OTG driver takes care of PHY initialization, clock management, >> -- >> 1.9.1 >> >> >> > > -- > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to

Re: [PATCH] usb: ehci-msm: Don't ioremap configuration space exclusively

-info.html Please read the FAQ at http://www.tux.org/lkml/ -- Best Regards Vivek Gautam Samsung RD Institute, Bangalore India -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http

Re: [PATCH RESEND] phy: exynos5-usbdrd: Add to support for Exynos5433 SoC

t; > Signed-off-by: Jaewon Kim > Tested-by: Chanwoo Choi > --- Patch looks good to me. Reviewed-by: Vivek Gautam > .../devicetree/bindings/phy/samsung-phy.txt|3 ++- > drivers/phy/phy-exynos5-usbdrd.c | 10 ++ > include/linux/mfd/syscon/exynos5-

Re: [PATCH RESEND] phy: exynos5-usbdrd: Add to support for Exynos5433 SoC

. Signed-off-by: Jaewon Kim jaewon02@samsung.com Tested-by: Chanwoo Choi cw00.c...@samsung.com --- Patch looks good to me. Reviewed-by: Vivek Gautam gautam.vi...@samsung.com .../devicetree/bindings/phy/samsung-phy.txt|3 ++- drivers/phy/phy-exynos5-usbdrd.c

Re: [PATCH] ARM: dts: remove usb2-phy on Exynos5 series SoC

>; > - phy-names = "usb2-phy", "usb3-phy"; > + phys = <_phy1 1>; > + phy-names = "usb3-phy"; > }; > }; > > -- > 1.7.9.5 > > -- > To unsubscribe from

Re: [PATCH] ARM: dts: remove usb2-phy on Exynos5 series SoC

...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- Best Regards Vivek Gautam Samsung RD Institute, Bangalore India -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo

Re: [PATCH] phy: exynos5-usbdrd: Fix off-by-one valid value checking for args->args[0]

Hi, On Friday, February 27, 2015 9:14 PM "Axel Lin" wrote: Current code uses args->args[0] as array subscript of phy_drd->phys[]. So the valid value range for args->args[0] is 0 ... EXYNOS5_DRDPHYS_NUM - 1. Signed-off-by: Axel Lin Reviewed by: Vivek Gautam --- driv

Re: [PATCH] phy: exynos5-usbdrd: Fix off-by-one valid value checking for args-args[0]

Hi, On Friday, February 27, 2015 9:14 PM Axel Lin axel@ingics.com wrote: Current code uses args-args[0] as array subscript of phy_drd-phys[]. So the valid value range for args-args[0] is 0 ... EXYNOS5_DRDPHYS_NUM - 1. Signed-off-by: Axel Lin axel@ingics.com Reviewed by: Vivek

[PATCH V7 RESEND 2/2] phy: exynos5-usbdrd: Calibrate LOS levels for exynos5420/5800

extra lines in the register macro definitions] Signed-off-by: Vivek Gautam --- drivers/phy/phy-exynos5-usbdrd.c | 219 +++--- 1 file changed, 203 insertions(+), 16 deletions(-) diff --git a/drivers/phy/phy-exynos5-usbdrd.c b/drivers/phy/phy-exynos5-usbdrd.c index

[PATCH V7 RESEND 1/2] usb: host: xhci-plat: Get PHYs for xhci's hcds

. Signed-off-by: Vivek Gautam --- drivers/usb/host/xhci-plat.c | 74 ++ 1 file changed, 74 insertions(+) diff --git a/drivers/usb/host/xhci-plat.c b/drivers/usb/host/xhci-plat.c index 08d402b..c478627 100644 --- a/drivers/usb/host/xhci-plat.c +++ b

[PATCH V7 RESEND 0/2] Fine tune USB 3.0 PHY on exynos5420

19/367 [2] https://lkml.org/lkml/2014/9/2/170; (to be specific https://lkml.org/lkml/2014/9/10/132) Vivek Gautam (2): usb: host: xhci-plat: Get PHYs for xhci's hcds phy: exynos5-usbdrd: Calibrate LOS levels for exynos5420/5800 drivers/phy/phy-exynos5-usbdrd.c | 219 +++

Re: [PATCHv5 6/7] base: platform: name the device already during allocation

rm_device_del(struct platform_device *pdev) >> if (pdev) { >> device_del(>dev); >> >> - if (pdev->id_auto) { >> - ida_simple_remove(_devid_ida, pdev->id); >> - pdev->id = PL

[PATCH V7 RESEND 2/2] phy: exynos5-usbdrd: Calibrate LOS levels for exynos5420/5800

extra lines in the register macro definitions] Signed-off-by: Vivek Gautam gautam.vi...@samsung.com --- drivers/phy/phy-exynos5-usbdrd.c | 219 +++--- 1 file changed, 203 insertions(+), 16 deletions(-) diff --git a/drivers/phy/phy-exynos5-usbdrd.c b/drivers/phy/phy

[PATCH V7 RESEND 1/2] usb: host: xhci-plat: Get PHYs for xhci's hcds

. Signed-off-by: Vivek Gautam gautam.vi...@samsung.com --- drivers/usb/host/xhci-plat.c | 74 ++ 1 file changed, 74 insertions(+) diff --git a/drivers/usb/host/xhci-plat.c b/drivers/usb/host/xhci-plat.c index 08d402b..c478627 100644 --- a/drivers/usb/host

<    6   7   8   9   10   11   12   13   14   15   >