Hi Kishon,
Thanks for the explanation.
On Thu, Jan 17, 2013 at 6:01 PM, kishon wrote:
> Hi,
>
>
> On Thursday 17 January 2013 05:41 PM, Vivek Gautam wrote:
>>
>> Hi Kishon,
>>
>>
>> On Wed, Jan 16, 2013 at 8:30 PM, Kishon Vijay Abraham I
>&g
HI Kukjin,
On Fri, Jan 18, 2013 at 6:46 AM, Kukjin Kim wrote:
> Vivek Gautam wrote:
>>
>> Adding support to parse device node data in order to get
>> required properties to set pmu isolation for usb-phy.
>>
>> Signed-off-by: Vivek Gautam
>> Reviewed-by: S
Hi Felipe,
On Fri, Jan 18, 2013 at 6:46 PM, Felipe Balbi wrote:
> Hi,
>
> On Mon, Jan 14, 2013 at 05:52:15PM +0530, Vivek Gautam wrote:
>> This patch adds host phy support to samsung-usbphy driver and
>> further adds support for samsung's exynos5250 usb-phy.
>>
HI Balbi,
On Fri, Jan 18, 2013 at 7:52 PM, Felipe Balbi wrote:
> On Fri, Jan 18, 2013 at 07:51:08PM +0530, Vivek Gautam wrote:
>> Hi Felipe,
>>
>>
>> On Fri, Jan 18, 2013 at 6:46 PM, Felipe Balbi wrote:
>> > Hi,
>> >
>> > On Mon, Jan 14, 20
Hi Alan,
On Fri, Jan 18, 2013 at 6:46 PM, Felipe Balbi wrote:
> On Fri, Jan 11, 2013 at 08:32:29PM +0530, Vivek Gautam wrote:
>> Adding the phy driver to ehci-s5p. Keeping the platform data
>> for continuing the smooth operation for boards which still uses it
>>
>>
Hi Felipe,
On Mon, Jan 14, 2013 at 6:29 PM, Vivek Gautam wrote:
> Changes from v2:
> - Renaming 'samsung-usbphy.c' driver to 'samsung-usb2.c' indicating
>usb 2.0 phy controller's driver for Samsung's SoCs.
> - Moving the register definitions and s
Hi Kukjin,
On Fri, Jan 18, 2013 at 8:37 PM, Felipe Balbi wrote:
> On Fri, Jan 18, 2013 at 07:59:52PM +0530, Vivek Gautam wrote:
>> HI Balbi,
>>
>>
>> On Fri, Jan 18, 2013 at 7:52 PM, Felipe Balbi wrote:
>> > On Fri, Jan 18, 2013 at 07:51:08PM +0530,
Dropping __devinit, __devexit_p, __exit annotations since they are
nop and no longer supported.
Signed-off-by: Vivek Gautam
---
drivers/usb/phy/samsung-usbphy.c |6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/usb/phy/samsung-usbphy.c b/drivers/usb/phy
Hi Kukjin,
On Tue, Jan 22, 2013 at 11:05 AM, Kukjin Kim wrote:
> Sylwester Nawrocki wrote:
>>
>> On 12/24/2012 09:13 AM, Vivek Gautam wrote:
>> >>>> These two changes look good to me. For both of them:
>> >>>>
>> >>>> Revie
Hi Kukjin,
On Tue, Jan 22, 2013 at 10:36 AM, Kukjin Kim wrote:
> Felipe Balbi wrote:
>>
>> On Fri, Jan 18, 2013 at 03:10:13PM +0200, Felipe Balbi wrote:
>> > Hi,
>> >
>> > On Tue, Dec 18, 2012 at 09:09:40PM +0530, Vivek Gautam wrote:
>> > &g
Hi Felipe,
On Tue, Jan 22, 2013 at 2:20 PM, Felipe Balbi wrote:
> HI,
>
> On Mon, Jan 21, 2013 at 09:23:28PM -0800, Kukjin Kim wrote:
>> Vivek Gautam wrote:
>> >
>> > Changes from v5:
>> > - Rebased on top of latest patches:
>> > usb:
Hi Felipe,
On Tue, Jan 22, 2013 at 3:02 PM, Felipe Balbi wrote:
> HI,
>
> On Tue, Jan 22, 2013 at 11:29:47AM +0200, Felipe Balbi wrote:
>> On Tue, Jan 22, 2013 at 02:45:26PM +0530, Vivek Gautam wrote:
>> > Hi Felipe,
>> >
>> >
>> > On Tue, Jan
phy_set_type()
and samsung_usbphy_cfg_sel().
- Addressed few nits:
-- added macro for 'KHZ'
-- removing useless 'if' from samsung_usbphy_cfg_sel()
-- keeping the place of clk_get intact and requesting driver
data before that.
Vivek Gautam (4)
Updating the names of usb-phy types to more generic names:
USB_PHY_TYPE_DEIVCE & USB_PHY_TYPE_HOST; and further update
its dependencies.
Signed-off-by: Praveen Paneri
Signed-off-by: Vivek Gautam
Acked-by: Kukjin Kim
---
drivers/usb/host/ehci-s5p.c |9 +
drivers/usb/
This patch adds host phy support to samsung-usbphy driver and
further adds support for samsung's exynos5250 usb-phy.
Signed-off-by: Praveen Paneri
Signed-off-by: Vivek Gautam
Acked-by: Kukjin Kim
---
.../devicetree/bindings/usb/samsung-usbphy.txt | 12 +-
drivers/usb/phy/Kc
Adding the phy driver to ehci-s5p. Keeping the platform data
for continuing the smooth operation for boards which still uses it
Signed-off-by: Vivek Gautam
Acked-by: Jingoo Han
Acked-by: Alan Stern
Acked-by: Kukjin Kim
---
drivers/usb/host/ehci-s5p.c | 80
Adding the phy-driver to ohci-exynos. Keeping the platform data
for continuing the smooth operation for boards which still uses it
Signed-off-by: Vivek Gautam
Acked-by: Jingoo Han
Acked-by: Alan Stern
Acked-by: Kukjin Kim
---
drivers/usb/host/ohci-exynos.c | 84
Adding usbphy node for Exynos5250 along with the
necessary device data to be parsed.
Signed-off-by: Vivek Gautam
---
arch/arm/boot/dts/exynos5250.dtsi | 15 +++
1 files changed, 15 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/exynos5250.dtsi
b/arch/arm/boot/dts
Adding usb3.0 phy node for Exynos5250 along with the
necessary device data to be parsed.
Signed-off-by: Vivek Gautam
---
arch/arm/boot/dts/exynos5250.dtsi | 13 +
1 files changed, 13 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/exynos5250.dtsi
b/arch/arm/boot/dts
- Aligning as per the patch:
usb: phy: samsung: Add support to set pmu isolation
- Replaced phy-handle approach for PHY CONTROL registers
to child nodes.
- Removing AUX data entry from exynos5250 dt file.
Vivek Gautam (2):
ARM: Exynos5250: Enabling samsung-usbphy driver
ARM: Exynos5250
Hi all,
On Wed, Jan 23, 2013 at 3:20 PM, Felipe Balbi wrote:
> Hi,
>
> On Tue, Jan 22, 2013 at 02:04:56PM -0800, Kukjin Kim wrote:
>> Felipe Balbi wrote:
>> > Hi,
>> >
>> Hi Felipe,
>>
>> [...]
>>
>> > > Right, DWC has version number, but that being the kind of USB controller
>> > > (USB 2.0 and
Hi Tomasz,
On Wed, Jan 16, 2013 at 8:35 PM, Vivek Gautam wrote:
> Hi Tomasz,
>
>
> On Wed, Jan 16, 2013 at 1:19 PM, Tomasz Figa wrote:
>> Hi Vivek,
>>
>> Don't you need also some clkdev lookup entry to make the clock available
>> in the driver?
>&g
Hi Sylwester,
On Wed, Jan 23, 2013 at 6:10 PM, Sylwester Nawrocki
wrote:
> Hi,
>
> On 01/23/2013 01:20 PM, Vivek Gautam wrote:
>>>>>> - { .compatible = "samsung,exynos-dwc3" },
>>>>>> + { .compatible = "samsung,synopsis-dwc3&q
"samsung,exynos5250-dwusb3" as per discussion happened in thread:
[PATCH 0/2] usb: exynos: Fix compatible strings used for device.
Vivek Gautam (2):
usb: ehci-s5p/ohci-exynos: Fix compatible strings for the device
usb: dwc3-exynos: Fix compatible strings for the device
Using specific chip in compatible strings. Newer SOCs can claim
device by using older string in the compatible list.
Signed-off-by: Vivek Gautam
Acked-by: Grant Likely
Reviewed-by: Doug Anderson
---
drivers/usb/host/ehci-s5p.c|2 +-
drivers/usb/host/ohci-exynos.c |2 +-
2 files
Using specific chip in compatible strings. Newer SOCs can claim
device by using older string in the compatible list.
Signed-off-by: Vivek Gautam
Acked-by: Grant Likely
Reviewed-by: Doug Anderson
---
drivers/usb/dwc3/dwc3-exynos.c |2 +-
1 files changed, 1 insertions(+), 1 deletions
On Thu, Jan 24, 2013 at 7:15 PM, Vivek Gautam wrote:
> Using chip specific compatible string as it should be.
> So fixing this for ehci-s5p, ohci-exynos and dwc3-exynos
> which till now used a generic 'exynos' in their compatible strings.
>
> Changes from v1:
>
Multiple dwc3 probe calls try to allocate no_op_xceive platform
device. Having static IDs for these will throw sysfs error -EEXIST.
Changing these static platform device IDs to AUTO to enable
multiple dwc3 controller support on a SoC.
Signed-off-by: Vivek Gautam
---
drivers/usb/dwc3/dwc3
branch of Felipe Balbi's usb tree.
Vivek Gautam (2):
usb: dwc3: exynos/omap: Change platform device IDs for no_op_xceive
to AUTO
usb: dwc3: host: Change platform device ID for xhci-hcd to AUTO
drivers/usb/dwc3/dwc3-exynos.c |4 ++--
drivers/usb/dwc3/dwc3-omap.c |4 ++--
d
Multiple dwc3 controllers will try to allocate multiple xhci-hcd
interfaces.
Changing platform device IDs from NONE to AUTO to support
such cases.
Signed-off-by: Vivek Gautam
---
drivers/usb/dwc3/host.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/usb/dwc3
usb: ehci: fsl: use bus->sysdev for DMA configuration
> usb: xhci: use bus->sysdev for DMA configuration
> usb: dwc3: use bus->sysdev for DMA configuration
> usb: dwc3: Do not set dma coherent mask
Tested patches 1, 4 & 5 on db820c platform with required set of patches [1] for
phy.
; The code in question is not performance sensitive so extra
> calls are not a problem. No extra checks means less code.
>
> Also the current code seems to be more in line with the rest
> of the kernel.
What functionality is missing without the suspend clock? Would
it make sense to change
Hi,
On Wed, Jun 22, 2016 at 2:00 PM, Roger Quadros wrote:
Luckily hit this thread while checking about DRD role functionality for DWC3.
> On 22/06/16 11:14, Felipe Balbi wrote:
>>
>> Hi,
>>
>> Roger Quadros writes:
>>> For the real use case, some Carplay platforms need it.
>>
Hi Roger,
On 2017-01-19 17:45, Roger Quadros wrote:
Vivek,
On 19/01/17 13:56, Vivek Gautam wrote:
Hi,
On Wed, Jun 22, 2016 at 2:00 PM, Roger Quadros wrote:
Luckily hit this thread while checking about DRD role functionality
for DWC3.
On 22/06/16 11:14, Felipe Balbi wrote:
Hi,
Roger
On 01/20/2017 02:00 PM, Roger Quadros wrote:
Vivek,
On 19/01/17 17:15, vivek.gau...@codeaurora.org wrote:
Hi Roger,
On 2017-01-19 17:45, Roger Quadros wrote:
Vivek,
On 19/01/17 13:56, Vivek Gautam wrote:
Hi,
On Wed, Jun 22, 2016 at 2:00 PM, Roger Quadros wrote:
Luckily hit this
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
y phy-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
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 bein
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 cu
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 avai
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 working/non-working
Fixing the sequence of events in dwc3_core_init() error exit path.
dwc3_core_exit() call is removed from the error path since,
whatever it's doing is already done.
Signed-off-by: Vivek Gautam
Cc: Felipe Balbi
---
Based on usb-next.
drivers/usb/dwc3/core.c | 5 ++---
1 file chang
Hi,
On Fri, Oct 21, 2016 at 3:45 PM, Felipe Balbi wrote:
>
> Hi,
>
> Vivek Gautam writes:
>> Fixing the sequence of events in dwc3_core_init() error exit path.
>> dwc3_core_exit() call is removed from the error path since,
>> whatever it's doing is alrea
ff-by: Vivek Gautam
---
Based on usb-next.
Build tested.
Changes since v1:
- Added reference to original commit that this patch fixes.
- CC'ed kernel stable.
drivers/usb/dwc3/core.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/drivers/usb/dwc3/core.c b/driver
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
> ---
> .../devicetree/bindings/phy/qcom,usb-hsic-ph
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(&ulpi->
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
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
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
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
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.
>>
>> Signed-off-by
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.
>>
>>
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
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,
>>>
>&
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
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
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.
>
>
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
t; is known to the system firmware or hardware.
>
> Signed-off-by: Arnd Bergmann
> Signed-off-by: Sriram Dash
> Tested-by: Baolin Wang
> Tested-by: Vivek Gautam
> Tested-by: Alexander Sverdlin
> Signed-off-by: Mathias Nyman
> ---
This patch doesn't work for me anym
t; Signed-off-by: Arnd Bergmann
>> > Signed-off-by: Sriram Dash
>> > Tested-by: Baolin Wang
>> > Tested-by: Vivek Gautam
>> > Tested-by: Alexander Sverdlin
>> > Signed-off-by: Mathias Nyman
>> > ---
>> > diff --git a/drivers/usb/host/x
gt; Tested-by: Baolin Wang
> Tested-by: Brian Norris
> Tested-by: Alexander Sverdlin
> Tested-by: Vivek Gautam
> Signed-off-by: Mathias Nyman
> Cc: Felipe Balbi
> Cc: Grygorii Strashko
> Cc: Sinjan Kumar
> Cc: David Fisher
> Cc: Catalin Marinas
> Cc: "Th
Hi Roger,
On Mon, Jan 23, 2017 at 4:49 PM, Roger Quadros wrote:
> Hi,
>
> We rely on the OTG controller block to provide us with
> VBUS and ID line status via an interrupt.
>
> This is then used to switch the controller between host, peripheral
> and idle roles based on the following table.
>
>
On Thu, Feb 9, 2017 at 1:19 PM, Roger Quadros wrote:
> Vivek,
>
> On 09/02/17 08:42, Vivek Gautam wrote:
>> Hi Roger,
>>
>> On Mon, Jan 23, 2017 at 4:49 PM, Roger Quadros wrote:
>>> Hi,
>>>
>>> We rely on the OTG controller block to provid
device, all the DMA parameters are not
>>> configured properly, notably dma ops for dwc3 devices. So, set
>>> the dma for xhci from sysdev. sysdev is pointing to device that
>>> is known to the system firmware or hardware.
>>>
>>> Signed-off-by: Arn
;>> is known to the system firmware or hardware.
>>>>
>>>> Signed-off-by: Arnd Bergmann
>>>> Signed-off-by: Sriram Dash
>>>> Tested-by: Baolin Wang
>>>> Tested-by: Vivek Gautam
>>>> Tested-by: Alexander Sverdlin
hardware.
Cc: Baolin Wang
Cc: Vivek Gautam
Cc: Alexander Sverdlin
Cc: Mathias Nyman
Signed-off-by: Arnd Bergmann
Signed-off-by: Sriram Dash
---
Hi, Baolin, Vivek and Alexander,
I removed your tested-by tag due to add one change that adding sysdev
for shared hcd too, if your test shows this change
Add support to get a list of resets available for the device.
These resets must be kept de-asserted until the device is
in use.
Cc: Felipe Balbi
Signed-off-by: Vivek Gautam
---
Based on torvald's master branch.
drivers/usb/dwc3/dwc3-of-simple.c | 49 +
Count number of reset phandles available with the device node
to know the resets a given device has.
Cc: Philipp Zabel
Signed-off-by: Vivek Gautam
---
Based on torvald's master branch.
include/linux/reset.h | 16
1 file changed, 16 insertions(+)
diff --git a/include/
On 02/16/2017 06:36 PM, Roger Quadros wrote:
dra7 OTG core limits the host controller to USB2.0 (high-speed) mode
when we're operating in dual-role.
We work around that by bypassing the OTG core and reading the
extcon framework directly for ID/VBUS events.
Signed-off-by: Roger Quadros
---
On 02/24/2017 06:27 AM, Peter Chen wrote:
On Thu, Feb 23, 2017 at 02:04:50PM +0530, Vivek Gautam wrote:
On 02/16/2017 06:36 PM, Roger Quadros wrote:
dra7 OTG core limits the host controller to USB2.0 (high-speed) mode
when we're operating in dual-role.
We work around that by bypassin
On Sat, Feb 25, 2017 at 9:20 AM, Chanwoo Choi wrote:
> 2017-02-25 12:46 GMT+09:00 Chanwoo Choi :
>> Hi,
>>
>> 2017-02-24 21:02 GMT+09:00 Roger Quadros :
>>> +Chanwoo
>>>
>>> Hi Vivek,
>>>
>>> On 23/02/17 10:34, Vivek Gautam
On Fri, Mar 10, 2017 at 4:54 PM, Felipe Balbi wrote:
> Vivek Gautam writes:
>
>> Add support to get a list of resets available for the device.
>> These resets must be kept de-asserted until the device is
>> in use.
>>
>> Cc: Felipe Balbi
>> Signed-of
Hi Philipp,
On Wed, Feb 22, 2017 at 10:54 AM, Vivek Gautam
wrote:
> Count number of reset phandles available with the device node
> to know the resets a given device has.
>
> Cc: Philipp Zabel
> Signed-off-by: Vivek Gautam
> ---
Any thoughts on this change?
A small addition
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
Cc: Kishon Vijay
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
Cc: Kishon Vijay
Hi Krzysztof,
On 03/14/2017 12:14 PM, Krzysztof Kozlowski wrote:
On Tue, Mar 14, 2017 at 8:22 AM, 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
On Wed, Mar 15, 2017 at 1:38 PM, Heiko Stübner wrote:
> Am Dienstag, 14. März 2017, 11:52:50 CET schrieb Vivek Gautam:
>> Adding vendor specific directories in phy to group
>> phy drivers under their respective vendor umbrella.
>>
>> Also updated the MAINTAINERS
Hi Philipp,
On Wed, Mar 15, 2017 at 4:10 PM, Philipp Zabel wrote:
> Hi Vivek,
>
> On Fri, 2017-03-10 at 20:10 +0530, Vivek Gautam wrote:
>> Hi Philipp,
>>
>>
>> On Wed, Feb 22, 2017 at 10:54 AM, Vivek Gautam
>> wrote:
>> > Count number of reset
Hi,
On 03/15/2017 04:15 PM, Philipp Zabel wrote:
On Wed, 2017-02-22 at 10:54 +0530, Vivek Gautam wrote:
Add support to get a list of resets available for the device.
These resets must be kept de-asserted until the device is
in use.
Cc: Felipe Balbi
Signed-off-by: Vivek Gautam
---
Based on
On Tue, Jan 31, 2017 at 12:55 AM, Shuah Khan wrote:
> Change goto labels to meaningful names from a series of errNs.
>
> Signed-off-by: Shuah Khan
> ---
>
> Rebased to usb-next
>
> drivers/usb/dwc3/dwc3-exynos.c | 22 +++---
> 1 file changed, 11 insertions(+), 11 deletions(-)
>
>
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
Cc: Stephen Boyd
Cc: Heikki Krogerus
Cc: Kishon Vijay Abraham I
Cc: linux-arm-ker...@lists.infradead.org
Cc: linux-ker
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
Acked-by: Krzysztof
inux-phy/next branch.
[1] https://www.spinics.net/lists/arm-kernel/msg568370.html
Signed-off-by: Vivek Gautam
Cc: Kishon Vijay Abraham I
Cc: linux-arm-ker...@lists.infradead.org
Cc: linux-arm-...@vger.kernel.org
Cc: linux-ker...@vger.kernel.org
Cc: linux-usb@vger.kernel.org
--
Vivek Gautam (3)
Ulpi phy header is not used for anything. Remove the same
from qcom-hs and qcom-hsic phy drivers.
Signed-off-by: Vivek Gautam
Suggested-by: Stephen Boyd
Cc: Kishon Vijay Abraham I
Cc: linux-arm-ker...@lists.infradead.org
Cc: linux-arm-...@vger.kernel.org
Cc: linux-ker...@vger.kernel.org
Cc
Qualcomm SOCs have QMP phy controller that provides support
to a number of controller, viz. PCIe, UFS, and USB.
Add a new driver, based on generic phy framework, for this
phy controller.
Signed-off-by: Vivek Gautam
Tested-by: Srinivas Kandagatla
---
Changes since v5:
- Rebased on top of phy
Qualcomm chipsets have QMP phy controller that provides
support to a number of controller, viz. PCIe, UFS, and USB.
Adding dt binding information for the same.
Signed-off-by: Vivek Gautam
Acked-by: Rob Herring
---
Changes since v5:
- Added Rob's 'Ack' for the new child nodes
PHY transceiver driver for QUSB2 phy controller that provides
HighSpeed functionality for DWC3 controller present on
Qualcomm chipsets.
Signed-off-by: Vivek Gautam
Reviewed-by: Stephen Boyd
---
Changes since v5:
- Rebased on top of phy grouping series. So the driver now sits in
drivers/phy
Qualcomm chipsets have QUSB2 phy controller that provides
HighSpeed functionality for DWC3 controller.
Adding dt binding information for the same.
Signed-off-by: Vivek Gautam
Acked-by: Rob Herring
---
Changes since v5:
- Removed leading 0 from the address in 'reg' property.
Change
/lists/arm-kernel/msg569990.html
[2] https://patchwork.kernel.org/patch/9567767/
[3] https://patchwork.kernel.org/patch/9567779/
[4] https://github.com/vivekgautam1/linux/tree/linux-phy-next-qcom-phy-db820c
Vivek Gautam (4):
dt-bindings: phy: Add support for QUSB2 phy
phy: qcom-qusb2: New driver for
On 03/20/2017 07:24 PM, Vivek Gautam wrote:
This patch series adds couple of PHY drivers for Qualcomm chipsets.
a) qcom-qusb2 phy driver: that provides High Speed USB functionality.
b) qcom-qmp phy driver: that is a combo phy providing support for
USB3, PCIe, UFS and few other controllers
Make use of reset_control_array_*() set of APIs to manage
an array of reset controllers available with the device.
Cc: Thierry Reding
Cc: Philipp Zabel
Signed-off-by: Vivek Gautam
---
Changes since v1:
- New patch added to the series to enable this driver use the
newer set of APIs that
b820c target for dwc3-of-simple driver.
-- Build tested for tegra/pmc driver. Needs testing.
[1] https://lkml.org/lkml/2017/2/22/12
[2] https://lkml.org/lkml/2017/2/22/11
Vivek Gautam (4):
reset: Add API to count number of reset available with device
reset: Add APIs to manage array of resets
Add support to get a list of resets available for the device.
These resets must be kept de-asserted until the device is
in use.
Cc: Felipe Balbi
Cc: Philipp Zabel
Signed-off-by: Vivek Gautam
---
Changes since v1:
- Using new APIs for reset control array.
- Using the *_get_exclusive() API
Many devices may want to request a bunch of resets
and control them. So it's better to manage them as an
array. Add APIs to _get(), _assert(), and _deassert()
an array of reset_control.
Cc: Philipp Zabel
Signed-off-by: Vivek Gautam
---
Changes since v1:
- New patch added to the s
Count number of reset phandles available with the device node
to know the resets a given device has.
Cc: Philipp Zabel
Signed-off-by: Vivek Gautam
---
Changes since v1:
- Handling the error path by returning error code for failures
and ENODEV for count equal to 0.
- Moved the function to
:
https://github.com/0day-ci/linux/commits/Vivek-Gautam/reset-APIs-to-manage-a-list-of-resets/20170404-111639
base: https://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb.git next
config: x86_64-randconfig-x004-201714 (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
find my comments inline.
On Mon, 2017-04-03 at 19:12 +0530, Vivek Gautam wrote:
Many devices may want to request a bunch of resets
and control them. So it's better to manage them as an
array. Add APIs to _get(), _assert(), and _deassert()
an array of reset_control.
Cc: Philipp Zabel
Sig
Hi Philipp,
On 04/04/2017 06:17 PM, Philipp Zabel wrote:
Hi Vivek,
On Tue, 2017-04-04 at 16:09 +0530, Vivek Gautam wrote:
[...]
I'd prefer to mirror the gpiod API a little, and to have the number
contained in the array structure, similar to struct gpio_descs:
[...]
Alright, i can u
On 04/04/2017 11:58 PM, Stephen Boyd wrote:
On 03/20, Vivek Gautam wrote:
diff --git a/Documentation/devicetree/bindings/phy/qcom-qusb2-phy.txt
b/Documentation/devicetree/bindings/phy/qcom-qusb2-phy.txt
new file mode 100644
index ..a6d19acde9e0
--- /dev/null
+++ b/Documentation
[4] https://lkml.org/lkml/2017/3/20/407
Vivek Gautam (4):
dt-bindings: phy: Add support for QUSB2 phy
phy: qcom-qusb2: New driver for QUSB2 PHY on Qcom chips
dt-bindings: phy: Add support for QMP phy
phy: qcom-qmp: new qmp phy driver for qcom-chipsets
.../devicetree/bindings/phy/qcom-q
101 - 200 of 868 matches
Mail list logo
