[PATCH V4 0/5] ARM: OMAP: HOST: TLL driver implementation

2012-07-16 Thread Keshava Munegowda
The TLL (Transceiver Less Link) is an separate IP block, independent of
the host controller. Basically this TLL operates like USB PHY which allows
the user to connect two USB transceiver interfaces together directly
without the use of differential transceivers in omap3 and later chips.
The TLL configuration is removed from the UHH driver and implemented as
a seperate platform driver. Now, the UHH driver configures the TLL
through API's exported by the TLL platform driver.

Signed-off-by: Keshava Munegowda 

In v4:
- rebased on top of linux kernel version 3.5.rc7
- reworked as per the comments given by Paul Walmsley 

In v3:
  - rebased on top V3 of Russ dill's patch
   'ARM: OMAP3: USB: Fix the EHCI ULPI PHY reset issue'
   fixes an issue where the ULPI PHYs were not held in reset
   while initializing the EHCI controller
http://permalink.gmane.org/gmane.linux.usb.general/65988
  
  - rebased on top of patch 
OMAP: USB : Fix the EHCI enumeration and core retention issue
 http://permalink.gmane.org/gmane.linux.usb.general/66239

In V2:
- covered review comments from linux omap and usb community
- rebased on top Russ dill's patch
   'ARM: OMAP3: USB: Fix the EHCI ULPI PHY reset issue'
   fixes an issue where the ULPI PHYs were not held in reset
   while initializing the EHCI controller

Keshava Munegowda (5):
  ARM: OMAP: Add the USB TLL clocks device name
  ARM: OMAP: USB: HOST TLL platform driver
  ARM: OMAP: USB: Invoke the TLL driver from USB HS core driver
  ARM: OMAP: USB: Remove TLL specific code from USB HS core driver
  ARM: OMAP: Remove older device name of the USB TLL clocks

 arch/arm/mach-omap2/clock3xxx_data.c  |8 +-
 arch/arm/mach-omap2/clock44xx_data.c  |4 +-
 arch/arm/mach-omap2/usb-host.c|   31 ++-
 arch/arm/plat-omap/include/plat/usb.h |7 +
 drivers/mfd/Kconfig   |2 +-
 drivers/mfd/Makefile  |2 +-
 drivers/mfd/omap-usb-host.c   |  238 ++---
 drivers/mfd/omap-usb-tll.c|  471 +
 8 files changed, 523 insertions(+), 240 deletions(-)
 create mode 100644 drivers/mfd/omap-usb-tll.c

-- 
1.7.9.5

--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [PATCH V4 0/5] ARM: OMAP: HOST: TLL driver implementation

2012-07-19 Thread Munegowda, Keshava
On Mon, Jul 16, 2012 at 7:01 PM, Keshava Munegowda
 wrote:
> The TLL (Transceiver Less Link) is an separate IP block, independent of
> the host controller. Basically this TLL operates like USB PHY which allows
> the user to connect two USB transceiver interfaces together directly
> without the use of differential transceivers in omap3 and later chips.
> The TLL configuration is removed from the UHH driver and implemented as
> a seperate platform driver. Now, the UHH driver configures the TLL
> through API's exported by the TLL platform driver.
>
> Signed-off-by: Keshava Munegowda 
>
> In v4:
> - rebased on top of linux kernel version 3.5.rc7
> - reworked as per the comments given by Paul Walmsley 
>
> In v3:
>   - rebased on top V3 of Russ dill's patch
>'ARM: OMAP3: USB: Fix the EHCI ULPI PHY reset issue'
>fixes an issue where the ULPI PHYs were not held in reset
>while initializing the EHCI controller
> http://permalink.gmane.org/gmane.linux.usb.general/65988
>
>   - rebased on top of patch
> OMAP: USB : Fix the EHCI enumeration and core retention issue
>  http://permalink.gmane.org/gmane.linux.usb.general/66239
>
> In V2:
> - covered review comments from linux omap and usb community
> - rebased on top Russ dill's patch
>'ARM: OMAP3: USB: Fix the EHCI ULPI PHY reset issue'
>fixes an issue where the ULPI PHYs were not held in reset
>while initializing the EHCI controller
>
> Keshava Munegowda (5):
>   ARM: OMAP: Add the USB TLL clocks device name
>   ARM: OMAP: USB: HOST TLL platform driver
>   ARM: OMAP: USB: Invoke the TLL driver from USB HS core driver
>   ARM: OMAP: USB: Remove TLL specific code from USB HS core driver
>   ARM: OMAP: Remove older device name of the USB TLL clocks
>
>  arch/arm/mach-omap2/clock3xxx_data.c  |8 +-
>  arch/arm/mach-omap2/clock44xx_data.c  |4 +-
>  arch/arm/mach-omap2/usb-host.c|   31 ++-
>  arch/arm/plat-omap/include/plat/usb.h |7 +
>  drivers/mfd/Kconfig   |2 +-
>  drivers/mfd/Makefile  |2 +-
>  drivers/mfd/omap-usb-host.c   |  238 ++---
>  drivers/mfd/omap-usb-tll.c|  471 
> +
>  8 files changed, 523 insertions(+), 240 deletions(-)
>  create mode 100644 drivers/mfd/omap-usb-tll.c
>
> --
> 1.7.9.5


Felipe/ Paul
  please let me know if you have any review comments on this v4 series.

regards
keshava
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [PATCH V4 0/5] ARM: OMAP: HOST: TLL driver implementation

2012-07-23 Thread Munegowda, Keshava
On Thu, Jul 19, 2012 at 3:48 PM, Munegowda, Keshava
 wrote:
> On Mon, Jul 16, 2012 at 7:01 PM, Keshava Munegowda
>  wrote:
>> The TLL (Transceiver Less Link) is an separate IP block, independent of
>> the host controller. Basically this TLL operates like USB PHY which allows
>> the user to connect two USB transceiver interfaces together directly
>> without the use of differential transceivers in omap3 and later chips.
>> The TLL configuration is removed from the UHH driver and implemented as
>> a seperate platform driver. Now, the UHH driver configures the TLL
>> through API's exported by the TLL platform driver.
>>
>> Signed-off-by: Keshava Munegowda 
>>
>> In v4:
>> - rebased on top of linux kernel version 3.5.rc7
>> - reworked as per the comments given by Paul Walmsley 
>>
>> In v3:
>>   - rebased on top V3 of Russ dill's patch
>>'ARM: OMAP3: USB: Fix the EHCI ULPI PHY reset issue'
>>fixes an issue where the ULPI PHYs were not held in reset
>>while initializing the EHCI controller
>> http://permalink.gmane.org/gmane.linux.usb.general/65988
>>
>>   - rebased on top of patch
>> OMAP: USB : Fix the EHCI enumeration and core retention issue
>>  http://permalink.gmane.org/gmane.linux.usb.general/66239
>>
>> In V2:
>> - covered review comments from linux omap and usb community
>> - rebased on top Russ dill's patch
>>'ARM: OMAP3: USB: Fix the EHCI ULPI PHY reset issue'
>>fixes an issue where the ULPI PHYs were not held in reset
>>while initializing the EHCI controller
>>
>> Keshava Munegowda (5):
>>   ARM: OMAP: Add the USB TLL clocks device name
>>   ARM: OMAP: USB: HOST TLL platform driver
>>   ARM: OMAP: USB: Invoke the TLL driver from USB HS core driver
>>   ARM: OMAP: USB: Remove TLL specific code from USB HS core driver
>>   ARM: OMAP: Remove older device name of the USB TLL clocks
>>
>>  arch/arm/mach-omap2/clock3xxx_data.c  |8 +-
>>  arch/arm/mach-omap2/clock44xx_data.c  |4 +-
>>  arch/arm/mach-omap2/usb-host.c|   31 ++-
>>  arch/arm/plat-omap/include/plat/usb.h |7 +
>>  drivers/mfd/Kconfig   |2 +-
>>  drivers/mfd/Makefile  |2 +-
>>  drivers/mfd/omap-usb-host.c   |  238 ++---
>>  drivers/mfd/omap-usb-tll.c|  471 
>> +
>>  8 files changed, 523 insertions(+), 240 deletions(-)
>>  create mode 100644 drivers/mfd/omap-usb-tll.c
>>
>> --
>> 1.7.9.5
>
>
> Felipe/ Paul
>   please let me know if you have any review comments on this v4 series.
>
> regards
> keshava

Hi Felipe
  please let me know if you have any review comments on this series now.


regards
keshava
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [PATCH V4 0/5] ARM: OMAP: HOST: TLL driver implementation

2012-07-23 Thread Felipe Balbi
Hi,

On Mon, Jul 23, 2012 at 07:31:10PM +0530, Munegowda, Keshava wrote:
> On Thu, Jul 19, 2012 at 3:48 PM, Munegowda, Keshava
>  wrote:
> > On Mon, Jul 16, 2012 at 7:01 PM, Keshava Munegowda
> >  wrote:
> >> The TLL (Transceiver Less Link) is an separate IP block, independent of
> >> the host controller. Basically this TLL operates like USB PHY which allows
> >> the user to connect two USB transceiver interfaces together directly
> >> without the use of differential transceivers in omap3 and later chips.
> >> The TLL configuration is removed from the UHH driver and implemented as
> >> a seperate platform driver. Now, the UHH driver configures the TLL
> >> through API's exported by the TLL platform driver.
> >>
> >> Signed-off-by: Keshava Munegowda 
> >>
> >> In v4:
> >> - rebased on top of linux kernel version 3.5.rc7
> >> - reworked as per the comments given by Paul Walmsley 
> >>
> >> In v3:
> >>   - rebased on top V3 of Russ dill's patch
> >>'ARM: OMAP3: USB: Fix the EHCI ULPI PHY reset issue'
> >>fixes an issue where the ULPI PHYs were not held in reset
> >>while initializing the EHCI controller
> >> http://permalink.gmane.org/gmane.linux.usb.general/65988
> >>
> >>   - rebased on top of patch
> >> OMAP: USB : Fix the EHCI enumeration and core retention issue
> >>  http://permalink.gmane.org/gmane.linux.usb.general/66239
> >>
> >> In V2:
> >> - covered review comments from linux omap and usb community
> >> - rebased on top Russ dill's patch
> >>'ARM: OMAP3: USB: Fix the EHCI ULPI PHY reset issue'
> >>fixes an issue where the ULPI PHYs were not held in reset
> >>while initializing the EHCI controller
> >>
> >> Keshava Munegowda (5):
> >>   ARM: OMAP: Add the USB TLL clocks device name
> >>   ARM: OMAP: USB: HOST TLL platform driver
> >>   ARM: OMAP: USB: Invoke the TLL driver from USB HS core driver
> >>   ARM: OMAP: USB: Remove TLL specific code from USB HS core driver
> >>   ARM: OMAP: Remove older device name of the USB TLL clocks
> >>
> >>  arch/arm/mach-omap2/clock3xxx_data.c  |8 +-
> >>  arch/arm/mach-omap2/clock44xx_data.c  |4 +-
> >>  arch/arm/mach-omap2/usb-host.c|   31 ++-
> >>  arch/arm/plat-omap/include/plat/usb.h |7 +
> >>  drivers/mfd/Kconfig   |2 +-
> >>  drivers/mfd/Makefile  |2 +-
> >>  drivers/mfd/omap-usb-host.c   |  238 ++---
> >>  drivers/mfd/omap-usb-tll.c|  471 
> >> +
> >>  8 files changed, 523 insertions(+), 240 deletions(-)
> >>  create mode 100644 drivers/mfd/omap-usb-tll.c
> >>
> >> --
> >> 1.7.9.5
> >
> >
> > Felipe/ Paul
> >   please let me know if you have any review comments on this v4 series.
> >
> > regards
> > keshava
> 
> Hi Felipe
>   please let me know if you have any review comments on this series 
> now.

looks ok... pretty much just moving code around.

-- 
balbi


signature.asc
Description: Digital signature


Re: [PATCH V4 0/5] ARM: OMAP: HOST: TLL driver implementation

2012-07-23 Thread Munegowda, Keshava
On Mon, Jul 23, 2012 at 7:38 PM, Felipe Balbi  wrote:
> Hi,
>
> On Mon, Jul 23, 2012 at 07:31:10PM +0530, Munegowda, Keshava wrote:
>> On Thu, Jul 19, 2012 at 3:48 PM, Munegowda, Keshava
>>  wrote:
>> > On Mon, Jul 16, 2012 at 7:01 PM, Keshava Munegowda
>> >  wrote:
>> >> The TLL (Transceiver Less Link) is an separate IP block, independent of
>> >> the host controller. Basically this TLL operates like USB PHY which allows
>> >> the user to connect two USB transceiver interfaces together directly
>> >> without the use of differential transceivers in omap3 and later chips.
>> >> The TLL configuration is removed from the UHH driver and implemented as
>> >> a seperate platform driver. Now, the UHH driver configures the TLL
>> >> through API's exported by the TLL platform driver.
>> >>
>> >> Signed-off-by: Keshava Munegowda 
>> >>
>> >> In v4:
>> >> - rebased on top of linux kernel version 3.5.rc7
>> >> - reworked as per the comments given by Paul Walmsley 
>> >>
>> >> In v3:
>> >>   - rebased on top V3 of Russ dill's patch
>> >>'ARM: OMAP3: USB: Fix the EHCI ULPI PHY reset issue'
>> >>fixes an issue where the ULPI PHYs were not held in reset
>> >>while initializing the EHCI controller
>> >> http://permalink.gmane.org/gmane.linux.usb.general/65988
>> >>
>> >>   - rebased on top of patch
>> >> OMAP: USB : Fix the EHCI enumeration and core retention issue
>> >>  http://permalink.gmane.org/gmane.linux.usb.general/66239
>> >>
>> >> In V2:
>> >> - covered review comments from linux omap and usb community
>> >> - rebased on top Russ dill's patch
>> >>'ARM: OMAP3: USB: Fix the EHCI ULPI PHY reset issue'
>> >>fixes an issue where the ULPI PHYs were not held in reset
>> >>while initializing the EHCI controller
>> >>
>> >> Keshava Munegowda (5):
>> >>   ARM: OMAP: Add the USB TLL clocks device name
>> >>   ARM: OMAP: USB: HOST TLL platform driver
>> >>   ARM: OMAP: USB: Invoke the TLL driver from USB HS core driver
>> >>   ARM: OMAP: USB: Remove TLL specific code from USB HS core driver
>> >>   ARM: OMAP: Remove older device name of the USB TLL clocks
>> >>
>> >>  arch/arm/mach-omap2/clock3xxx_data.c  |8 +-
>> >>  arch/arm/mach-omap2/clock44xx_data.c  |4 +-
>> >>  arch/arm/mach-omap2/usb-host.c|   31 ++-
>> >>  arch/arm/plat-omap/include/plat/usb.h |7 +
>> >>  drivers/mfd/Kconfig   |2 +-
>> >>  drivers/mfd/Makefile  |2 +-
>> >>  drivers/mfd/omap-usb-host.c   |  238 ++---
>> >>  drivers/mfd/omap-usb-tll.c|  471 
>> >> +
>> >>  8 files changed, 523 insertions(+), 240 deletions(-)
>> >>  create mode 100644 drivers/mfd/omap-usb-tll.c
>> >>
>> >> --
>> >> 1.7.9.5
>> >
>> >
>> > Felipe/ Paul
>> >   please let me know if you have any review comments on this v4 series.
>> >
>> > regards
>> > keshava
>>
>> Hi Felipe
>>   please let me know if you have any review comments on this series 
>> now.
>
> looks ok... pretty much just moving code around.
>
> --
> balbi


Thanks Felipe

then I request please give your Ack by for this series.

regards
keshava
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [PATCH V4 0/5] ARM: OMAP: HOST: TLL driver implementation

2012-07-27 Thread Munegowda, Keshava
On Mon, Jul 23, 2012 at 8:04 PM, Munegowda, Keshava
 wrote:
> On Mon, Jul 23, 2012 at 7:38 PM, Felipe Balbi  wrote:
>> Hi,
>>
>> On Mon, Jul 23, 2012 at 07:31:10PM +0530, Munegowda, Keshava wrote:
>>> On Thu, Jul 19, 2012 at 3:48 PM, Munegowda, Keshava
>>>  wrote:
>>> > On Mon, Jul 16, 2012 at 7:01 PM, Keshava Munegowda
>>> >  wrote:
>>> >> The TLL (Transceiver Less Link) is an separate IP block, independent of
>>> >> the host controller. Basically this TLL operates like USB PHY which 
>>> >> allows
>>> >> the user to connect two USB transceiver interfaces together directly
>>> >> without the use of differential transceivers in omap3 and later chips.
>>> >> The TLL configuration is removed from the UHH driver and implemented as
>>> >> a seperate platform driver. Now, the UHH driver configures the TLL
>>> >> through API's exported by the TLL platform driver.
>>> >>
>>> >> Signed-off-by: Keshava Munegowda 
>>> >>
>>> >> In v4:
>>> >> - rebased on top of linux kernel version 3.5.rc7
>>> >> - reworked as per the comments given by Paul Walmsley 
>>> >> 
>>> >>
>>> >> In v3:
>>> >>   - rebased on top V3 of Russ dill's patch
>>> >>'ARM: OMAP3: USB: Fix the EHCI ULPI PHY reset issue'
>>> >>fixes an issue where the ULPI PHYs were not held in reset
>>> >>while initializing the EHCI controller
>>> >> http://permalink.gmane.org/gmane.linux.usb.general/65988
>>> >>
>>> >>   - rebased on top of patch
>>> >> OMAP: USB : Fix the EHCI enumeration and core retention issue
>>> >>  http://permalink.gmane.org/gmane.linux.usb.general/66239
>>> >>
>>> >> In V2:
>>> >> - covered review comments from linux omap and usb community
>>> >> - rebased on top Russ dill's patch
>>> >>'ARM: OMAP3: USB: Fix the EHCI ULPI PHY reset issue'
>>> >>fixes an issue where the ULPI PHYs were not held in reset
>>> >>while initializing the EHCI controller
>>> >>
>>> >> Keshava Munegowda (5):
>>> >>   ARM: OMAP: Add the USB TLL clocks device name
>>> >>   ARM: OMAP: USB: HOST TLL platform driver
>>> >>   ARM: OMAP: USB: Invoke the TLL driver from USB HS core driver
>>> >>   ARM: OMAP: USB: Remove TLL specific code from USB HS core driver
>>> >>   ARM: OMAP: Remove older device name of the USB TLL clocks
>>> >>
>>> >>  arch/arm/mach-omap2/clock3xxx_data.c  |8 +-
>>> >>  arch/arm/mach-omap2/clock44xx_data.c  |4 +-
>>> >>  arch/arm/mach-omap2/usb-host.c|   31 ++-
>>> >>  arch/arm/plat-omap/include/plat/usb.h |7 +
>>> >>  drivers/mfd/Kconfig   |2 +-
>>> >>  drivers/mfd/Makefile  |2 +-
>>> >>  drivers/mfd/omap-usb-host.c   |  238 ++---
>>> >>  drivers/mfd/omap-usb-tll.c|  471 
>>> >> +
>>> >>  8 files changed, 523 insertions(+), 240 deletions(-)
>>> >>  create mode 100644 drivers/mfd/omap-usb-tll.c
>>> >>
>>> >> --
>>> >> 1.7.9.5
>>> >
>>> >
>>> > Felipe/ Paul
>>> >   please let me know if you have any review comments on this v4 
>>> > series.
>>> >
>>> > regards
>>> > keshava
>>>
>>> Hi Felipe
>>>   please let me know if you have any review comments on this series 
>>> now.
>>
>> looks ok... pretty much just moving code around.
>>
>> --
>> balbi
>
>
> Thanks Felipe
>
> then I request please give your Ack by for this series.
>
> regards
> keshava

Hi Paul
do you have any review comments on this series?
Felipe is OK with this series.  if there are no review comments on this series
I request your ack by for the same.
Once this series gets in to mainline. i will start the Device tree
conversion for usb2 host.

regards
keshava
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [PATCH V4 0/5] ARM: OMAP: HOST: TLL driver implementation

2012-08-13 Thread Munegowda, Keshava
On Fri, Jul 27, 2012 at 5:44 PM, Munegowda, Keshava
 wrote:
> On Mon, Jul 23, 2012 at 8:04 PM, Munegowda, Keshava
>  wrote:
>> On Mon, Jul 23, 2012 at 7:38 PM, Felipe Balbi  wrote:
>>> Hi,
>>>
>>> On Mon, Jul 23, 2012 at 07:31:10PM +0530, Munegowda, Keshava wrote:
 On Thu, Jul 19, 2012 at 3:48 PM, Munegowda, Keshava
  wrote:
 > On Mon, Jul 16, 2012 at 7:01 PM, Keshava Munegowda
 >  wrote:
 >> The TLL (Transceiver Less Link) is an separate IP block, independent of
 >> the host controller. Basically this TLL operates like USB PHY which 
 >> allows
 >> the user to connect two USB transceiver interfaces together directly
 >> without the use of differential transceivers in omap3 and later chips.
 >> The TLL configuration is removed from the UHH driver and implemented as
 >> a seperate platform driver. Now, the UHH driver configures the TLL
 >> through API's exported by the TLL platform driver.
 >>
 >> Signed-off-by: Keshava Munegowda 
 >>
 >> In v4:
 >> - rebased on top of linux kernel version 3.5.rc7
 >> - reworked as per the comments given by Paul Walmsley 
 >> 
 >>
 >> In v3:
 >>   - rebased on top V3 of Russ dill's patch
 >>'ARM: OMAP3: USB: Fix the EHCI ULPI PHY reset issue'
 >>fixes an issue where the ULPI PHYs were not held in reset
 >>while initializing the EHCI controller
 >> http://permalink.gmane.org/gmane.linux.usb.general/65988
 >>
 >>   - rebased on top of patch
 >> OMAP: USB : Fix the EHCI enumeration and core retention issue
 >>  http://permalink.gmane.org/gmane.linux.usb.general/66239
 >>
 >> In V2:
 >> - covered review comments from linux omap and usb community
 >> - rebased on top Russ dill's patch
 >>'ARM: OMAP3: USB: Fix the EHCI ULPI PHY reset issue'
 >>fixes an issue where the ULPI PHYs were not held in reset
 >>while initializing the EHCI controller
 >>
 >> Keshava Munegowda (5):
 >>   ARM: OMAP: Add the USB TLL clocks device name
 >>   ARM: OMAP: USB: HOST TLL platform driver
 >>   ARM: OMAP: USB: Invoke the TLL driver from USB HS core driver
 >>   ARM: OMAP: USB: Remove TLL specific code from USB HS core driver
 >>   ARM: OMAP: Remove older device name of the USB TLL clocks
 >>
 >>  arch/arm/mach-omap2/clock3xxx_data.c  |8 +-
 >>  arch/arm/mach-omap2/clock44xx_data.c  |4 +-
 >>  arch/arm/mach-omap2/usb-host.c|   31 ++-
 >>  arch/arm/plat-omap/include/plat/usb.h |7 +
 >>  drivers/mfd/Kconfig   |2 +-
 >>  drivers/mfd/Makefile  |2 +-
 >>  drivers/mfd/omap-usb-host.c   |  238 ++---
 >>  drivers/mfd/omap-usb-tll.c|  471 
 >> +
 >>  8 files changed, 523 insertions(+), 240 deletions(-)
 >>  create mode 100644 drivers/mfd/omap-usb-tll.c
 >>
 >> --
 >> 1.7.9.5
 >
 >
 > Felipe/ Paul
 >   please let me know if you have any review comments on this v4 
 > series.
 >
 > regards
 > keshava

 Hi Felipe
   please let me know if you have any review comments on this 
 series now.
>>>
>>> looks ok... pretty much just moving code around.
>>>
>>> --
>>> balbi
>>
>>
>> Thanks Felipe
>>
>> then I request please give your Ack by for this series.
>>
>> regards
>> keshava
>
> Hi Paul
> do you have any review comments on this series?
> Felipe is OK with this series.  if there are no review comments on this series
> I request your ack by for the same.
> Once this series gets in to mainline. i will start the Device tree
> conversion for usb2 host.
>
> regards
> keshava

Hi Felipe
   please give you ack by this series , so that I request
samuel to merge to mainline.


regards
keshava
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [PATCH V4 0/5] ARM: OMAP: HOST: TLL driver implementation

2012-08-13 Thread Felipe Balbi
On Mon, Aug 13, 2012 at 06:52:13PM +0530, Munegowda, Keshava wrote:
> On Fri, Jul 27, 2012 at 5:44 PM, Munegowda, Keshava
>  wrote:
> > On Mon, Jul 23, 2012 at 8:04 PM, Munegowda, Keshava
> >  wrote:
> >> On Mon, Jul 23, 2012 at 7:38 PM, Felipe Balbi  wrote:
> >>> Hi,
> >>>
> >>> On Mon, Jul 23, 2012 at 07:31:10PM +0530, Munegowda, Keshava wrote:
>  On Thu, Jul 19, 2012 at 3:48 PM, Munegowda, Keshava
>   wrote:
>  > On Mon, Jul 16, 2012 at 7:01 PM, Keshava Munegowda
>  >  wrote:
>  >> The TLL (Transceiver Less Link) is an separate IP block, independent 
>  >> of
>  >> the host controller. Basically this TLL operates like USB PHY which 
>  >> allows
>  >> the user to connect two USB transceiver interfaces together directly
>  >> without the use of differential transceivers in omap3 and later chips.
>  >> The TLL configuration is removed from the UHH driver and implemented 
>  >> as
>  >> a seperate platform driver. Now, the UHH driver configures the TLL
>  >> through API's exported by the TLL platform driver.
>  >>
>  >> Signed-off-by: Keshava Munegowda 
>  >>
>  >> In v4:
>  >> - rebased on top of linux kernel version 3.5.rc7
>  >> - reworked as per the comments given by Paul Walmsley 
>  >> 
>  >>
>  >> In v3:
>  >>   - rebased on top V3 of Russ dill's patch
>  >>'ARM: OMAP3: USB: Fix the EHCI ULPI PHY reset issue'
>  >>fixes an issue where the ULPI PHYs were not held in reset
>  >>while initializing the EHCI controller
>  >> http://permalink.gmane.org/gmane.linux.usb.general/65988
>  >>
>  >>   - rebased on top of patch
>  >> OMAP: USB : Fix the EHCI enumeration and core retention issue
>  >>  http://permalink.gmane.org/gmane.linux.usb.general/66239
>  >>
>  >> In V2:
>  >> - covered review comments from linux omap and usb community
>  >> - rebased on top Russ dill's patch
>  >>'ARM: OMAP3: USB: Fix the EHCI ULPI PHY reset issue'
>  >>fixes an issue where the ULPI PHYs were not held in reset
>  >>while initializing the EHCI controller
>  >>
>  >> Keshava Munegowda (5):
>  >>   ARM: OMAP: Add the USB TLL clocks device name
>  >>   ARM: OMAP: USB: HOST TLL platform driver
>  >>   ARM: OMAP: USB: Invoke the TLL driver from USB HS core driver
>  >>   ARM: OMAP: USB: Remove TLL specific code from USB HS core driver
>  >>   ARM: OMAP: Remove older device name of the USB TLL clocks
>  >>
>  >>  arch/arm/mach-omap2/clock3xxx_data.c  |8 +-
>  >>  arch/arm/mach-omap2/clock44xx_data.c  |4 +-
>  >>  arch/arm/mach-omap2/usb-host.c|   31 ++-
>  >>  arch/arm/plat-omap/include/plat/usb.h |7 +
>  >>  drivers/mfd/Kconfig   |2 +-
>  >>  drivers/mfd/Makefile  |2 +-
>  >>  drivers/mfd/omap-usb-host.c   |  238 ++---
>  >>  drivers/mfd/omap-usb-tll.c|  471 
>  >> +
>  >>  8 files changed, 523 insertions(+), 240 deletions(-)
>  >>  create mode 100644 drivers/mfd/omap-usb-tll.c
>  >>
>  >> --
>  >> 1.7.9.5
>  >
>  >
>  > Felipe/ Paul
>  >   please let me know if you have any review comments on this v4 
>  > series.
>  >
>  > regards
>  > keshava
> 
>  Hi Felipe
>    please let me know if you have any review comments on this 
>  series now.
> >>>
> >>> looks ok... pretty much just moving code around.
> >>>
> >>> --
> >>> balbi
> >>
> >>
> >> Thanks Felipe
> >>
> >> then I request please give your Ack by for this series.
> >>
> >> regards
> >> keshava
> >
> > Hi Paul
> > do you have any review comments on this series?
> > Felipe is OK with this series.  if there are no review comments on this 
> > series
> > I request your ack by for the same.
> > Once this series gets in to mainline. i will start the Device tree
> > conversion for usb2 host.
> >
> > regards
> > keshava
> 
> Hi Felipe
>please give you ack by this series , so that I request
> samuel to merge to mainline.

sure, here you go

Acked-by: Felipe Balbi 

-- 
balbi


signature.asc
Description: Digital signature


Re: [PATCH V4 0/5] ARM: OMAP: HOST: TLL driver implementation

2012-08-13 Thread Munegowda, Keshava
On Mon, Aug 13, 2012 at 7:39 PM, Felipe Balbi  wrote:
> On Mon, Aug 13, 2012 at 06:52:13PM +0530, Munegowda, Keshava wrote:
>> On Fri, Jul 27, 2012 at 5:44 PM, Munegowda, Keshava
>>  wrote:
>> > On Mon, Jul 23, 2012 at 8:04 PM, Munegowda, Keshava
>> >  wrote:
>> >> On Mon, Jul 23, 2012 at 7:38 PM, Felipe Balbi  wrote:
>> >>> Hi,
>> >>>
>> >>> On Mon, Jul 23, 2012 at 07:31:10PM +0530, Munegowda, Keshava wrote:
>>  On Thu, Jul 19, 2012 at 3:48 PM, Munegowda, Keshava
>>   wrote:
>>  > On Mon, Jul 16, 2012 at 7:01 PM, Keshava Munegowda
>>  >  wrote:
>>  >> The TLL (Transceiver Less Link) is an separate IP block, independent 
>>  >> of
>>  >> the host controller. Basically this TLL operates like USB PHY which 
>>  >> allows
>>  >> the user to connect two USB transceiver interfaces together directly
>>  >> without the use of differential transceivers in omap3 and later 
>>  >> chips.
>>  >> The TLL configuration is removed from the UHH driver and implemented 
>>  >> as
>>  >> a seperate platform driver. Now, the UHH driver configures the TLL
>>  >> through API's exported by the TLL platform driver.
>>  >>
>>  >> Signed-off-by: Keshava Munegowda 
>>  >>
>>  >> In v4:
>>  >> - rebased on top of linux kernel version 3.5.rc7
>>  >> - reworked as per the comments given by Paul Walmsley 
>>  >> 
>>  >>
>>  >> In v3:
>>  >>   - rebased on top V3 of Russ dill's patch
>>  >>'ARM: OMAP3: USB: Fix the EHCI ULPI PHY reset issue'
>>  >>fixes an issue where the ULPI PHYs were not held in reset
>>  >>while initializing the EHCI controller
>>  >> http://permalink.gmane.org/gmane.linux.usb.general/65988
>>  >>
>>  >>   - rebased on top of patch
>>  >> OMAP: USB : Fix the EHCI enumeration and core retention issue
>>  >>  http://permalink.gmane.org/gmane.linux.usb.general/66239
>>  >>
>>  >> In V2:
>>  >> - covered review comments from linux omap and usb community
>>  >> - rebased on top Russ dill's patch
>>  >>'ARM: OMAP3: USB: Fix the EHCI ULPI PHY reset issue'
>>  >>fixes an issue where the ULPI PHYs were not held in reset
>>  >>while initializing the EHCI controller
>>  >>
>>  >> Keshava Munegowda (5):
>>  >>   ARM: OMAP: Add the USB TLL clocks device name
>>  >>   ARM: OMAP: USB: HOST TLL platform driver
>>  >>   ARM: OMAP: USB: Invoke the TLL driver from USB HS core driver
>>  >>   ARM: OMAP: USB: Remove TLL specific code from USB HS core driver
>>  >>   ARM: OMAP: Remove older device name of the USB TLL clocks
>>  >>
>>  >>  arch/arm/mach-omap2/clock3xxx_data.c  |8 +-
>>  >>  arch/arm/mach-omap2/clock44xx_data.c  |4 +-
>>  >>  arch/arm/mach-omap2/usb-host.c|   31 ++-
>>  >>  arch/arm/plat-omap/include/plat/usb.h |7 +
>>  >>  drivers/mfd/Kconfig   |2 +-
>>  >>  drivers/mfd/Makefile  |2 +-
>>  >>  drivers/mfd/omap-usb-host.c   |  238 ++---
>>  >>  drivers/mfd/omap-usb-tll.c|  471 
>>  >> +
>>  >>  8 files changed, 523 insertions(+), 240 deletions(-)
>>  >>  create mode 100644 drivers/mfd/omap-usb-tll.c
>>  >>
>>  >> --
>>  >> 1.7.9.5
>>  >
>>  >
>>  > Felipe/ Paul
>>  >   please let me know if you have any review comments on this v4 
>>  > series.
>>  >
>>  > regards
>>  > keshava
>> 
>>  Hi Felipe
>>    please let me know if you have any review comments on this 
>>  series now.
>> >>>
>> >>> looks ok... pretty much just moving code around.
>> >>>
>> >>> --
>> >>> balbi
>> >>
>> >>
>> >> Thanks Felipe
>> >>
>> >> then I request please give your Ack by for this series.
>> >>
>> >> regards
>> >> keshava
>> >
>> > Hi Paul
>> > do you have any review comments on this series?
>> > Felipe is OK with this series.  if there are no review comments on this 
>> > series
>> > I request your ack by for the same.
>> > Once this series gets in to mainline. i will start the Device tree
>> > conversion for usb2 host.
>> >
>> > regards
>> > keshava
>>
>> Hi Felipe
>>please give you ack by this series , so that I request
>> samuel to merge to mainline.
>
> sure, here you go
>
> Acked-by: Felipe Balbi 
>
> --
> balbi


Thanks Felipe

Samuel
  I request please queue this series for the next merge window.

regards
keshava
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [PATCH V4 0/5] ARM: OMAP: HOST: TLL driver implementation

2012-09-13 Thread Munegowda, Keshava
On Mon, Aug 13, 2012 at 8:23 PM, Munegowda, Keshava
 wrote:
> On Mon, Aug 13, 2012 at 7:39 PM, Felipe Balbi  wrote:
>> On Mon, Aug 13, 2012 at 06:52:13PM +0530, Munegowda, Keshava wrote:
>>> On Fri, Jul 27, 2012 at 5:44 PM, Munegowda, Keshava
>>>  wrote:
>>> > On Mon, Jul 23, 2012 at 8:04 PM, Munegowda, Keshava
>>> >  wrote:
>>> >> On Mon, Jul 23, 2012 at 7:38 PM, Felipe Balbi  wrote:
>>> >>> Hi,
>>> >>>
>>> >>> On Mon, Jul 23, 2012 at 07:31:10PM +0530, Munegowda, Keshava wrote:
>>>  On Thu, Jul 19, 2012 at 3:48 PM, Munegowda, Keshava
>>>   wrote:
>>>  > On Mon, Jul 16, 2012 at 7:01 PM, Keshava Munegowda
>>>  >  wrote:
>>>  >> The TLL (Transceiver Less Link) is an separate IP block, 
>>>  >> independent of
>>>  >> the host controller. Basically this TLL operates like USB PHY which 
>>>  >> allows
>>>  >> the user to connect two USB transceiver interfaces together directly
>>>  >> without the use of differential transceivers in omap3 and later 
>>>  >> chips.
>>>  >> The TLL configuration is removed from the UHH driver and 
>>>  >> implemented as
>>>  >> a seperate platform driver. Now, the UHH driver configures the TLL
>>>  >> through API's exported by the TLL platform driver.
>>>  >>
>>>  >> Signed-off-by: Keshava Munegowda 
>>>  >>
>>>  >> In v4:
>>>  >> - rebased on top of linux kernel version 3.5.rc7
>>>  >> - reworked as per the comments given by Paul Walmsley 
>>>  >> 
>>>  >>
>>>  >> In v3:
>>>  >>   - rebased on top V3 of Russ dill's patch
>>>  >>'ARM: OMAP3: USB: Fix the EHCI ULPI PHY reset issue'
>>>  >>fixes an issue where the ULPI PHYs were not held in reset
>>>  >>while initializing the EHCI controller
>>>  >> http://permalink.gmane.org/gmane.linux.usb.general/65988
>>>  >>
>>>  >>   - rebased on top of patch
>>>  >> OMAP: USB : Fix the EHCI enumeration and core retention issue
>>>  >>  http://permalink.gmane.org/gmane.linux.usb.general/66239
>>>  >>
>>>  >> In V2:
>>>  >> - covered review comments from linux omap and usb community
>>>  >> - rebased on top Russ dill's patch
>>>  >>'ARM: OMAP3: USB: Fix the EHCI ULPI PHY reset issue'
>>>  >>fixes an issue where the ULPI PHYs were not held in reset
>>>  >>while initializing the EHCI controller
>>>  >>
>>>  >> Keshava Munegowda (5):
>>>  >>   ARM: OMAP: Add the USB TLL clocks device name
>>>  >>   ARM: OMAP: USB: HOST TLL platform driver
>>>  >>   ARM: OMAP: USB: Invoke the TLL driver from USB HS core driver
>>>  >>   ARM: OMAP: USB: Remove TLL specific code from USB HS core driver
>>>  >>   ARM: OMAP: Remove older device name of the USB TLL clocks
>>>  >>
>>>  >>  arch/arm/mach-omap2/clock3xxx_data.c  |8 +-
>>>  >>  arch/arm/mach-omap2/clock44xx_data.c  |4 +-
>>>  >>  arch/arm/mach-omap2/usb-host.c|   31 ++-
>>>  >>  arch/arm/plat-omap/include/plat/usb.h |7 +
>>>  >>  drivers/mfd/Kconfig   |2 +-
>>>  >>  drivers/mfd/Makefile  |2 +-
>>>  >>  drivers/mfd/omap-usb-host.c   |  238 ++---
>>>  >>  drivers/mfd/omap-usb-tll.c|  471 
>>>  >> +
>>>  >>  8 files changed, 523 insertions(+), 240 deletions(-)
>>>  >>  create mode 100644 drivers/mfd/omap-usb-tll.c
>>>  >>
>>>  >> --
>>>  >> 1.7.9.5
>>>  >
>>>  >
>>>  > Felipe/ Paul
>>>  >   please let me know if you have any review comments on this v4 
>>>  > series.
>>>  >
>>>  > regards
>>>  > keshava
>>> 
>>>  Hi Felipe
>>>    please let me know if you have any review comments on this 
>>>  series now.
>>> >>>
>>> >>> looks ok... pretty much just moving code around.
>>> >>>
>>> >>> --
>>> >>> balbi
>>> >>
>>> >>
>>> >> Thanks Felipe
>>> >>
>>> >> then I request please give your Ack by for this series.
>>> >>
>>> >> regards
>>> >> keshava
>>> >
>>> > Hi Paul
>>> > do you have any review comments on this series?
>>> > Felipe is OK with this series.  if there are no review comments on this 
>>> > series
>>> > I request your ack by for the same.
>>> > Once this series gets in to mainline. i will start the Device tree
>>> > conversion for usb2 host.
>>> >
>>> > regards
>>> > keshava
>>>
>>> Hi Felipe
>>>please give you ack by this series , so that I request
>>> samuel to merge to mainline.
>>
>> sure, here you go
>>
>> Acked-by: Felipe Balbi 
>>
>> --
>> balbi
>
>
> Thanks Felipe
>
> Samuel
>   I request please queue this series for the next merge window.
>
> regards
> keshava


samuel : ping

regards
keshava
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info

Re: [PATCH V4 0/5] ARM: OMAP: HOST: TLL driver implementation

2012-09-18 Thread Munegowda, Keshava
On Thu, Sep 13, 2012 at 5:14 PM, Munegowda, Keshava
 wrote:
> On Mon, Aug 13, 2012 at 8:23 PM, Munegowda, Keshava
>  wrote:
>> On Mon, Aug 13, 2012 at 7:39 PM, Felipe Balbi  wrote:
>>> On Mon, Aug 13, 2012 at 06:52:13PM +0530, Munegowda, Keshava wrote:
 On Fri, Jul 27, 2012 at 5:44 PM, Munegowda, Keshava
  wrote:
 > On Mon, Jul 23, 2012 at 8:04 PM, Munegowda, Keshava
 >  wrote:
 >> On Mon, Jul 23, 2012 at 7:38 PM, Felipe Balbi  wrote:
 >>> Hi,
 >>>
 >>> On Mon, Jul 23, 2012 at 07:31:10PM +0530, Munegowda, Keshava wrote:
  On Thu, Jul 19, 2012 at 3:48 PM, Munegowda, Keshava
   wrote:
  > On Mon, Jul 16, 2012 at 7:01 PM, Keshava Munegowda
  >  wrote:
  >> The TLL (Transceiver Less Link) is an separate IP block, 
  >> independent of
  >> the host controller. Basically this TLL operates like USB PHY 
  >> which allows
  >> the user to connect two USB transceiver interfaces together 
  >> directly
  >> without the use of differential transceivers in omap3 and later 
  >> chips.
  >> The TLL configuration is removed from the UHH driver and 
  >> implemented as
  >> a seperate platform driver. Now, the UHH driver configures the TLL
  >> through API's exported by the TLL platform driver.
  >>
  >> Signed-off-by: Keshava Munegowda 
  >>
  >> In v4:
  >> - rebased on top of linux kernel version 3.5.rc7
  >> - reworked as per the comments given by Paul Walmsley 
  >> 
  >>
  >> In v3:
  >>   - rebased on top V3 of Russ dill's patch
  >>'ARM: OMAP3: USB: Fix the EHCI ULPI PHY reset issue'
  >>fixes an issue where the ULPI PHYs were not held in reset
  >>while initializing the EHCI controller
  >> http://permalink.gmane.org/gmane.linux.usb.general/65988
  >>
  >>   - rebased on top of patch
  >> OMAP: USB : Fix the EHCI enumeration and core retention issue
  >>  http://permalink.gmane.org/gmane.linux.usb.general/66239
  >>
  >> In V2:
  >> - covered review comments from linux omap and usb community
  >> - rebased on top Russ dill's patch
  >>'ARM: OMAP3: USB: Fix the EHCI ULPI PHY reset issue'
  >>fixes an issue where the ULPI PHYs were not held in reset
  >>while initializing the EHCI controller
  >>
  >> Keshava Munegowda (5):
  >>   ARM: OMAP: Add the USB TLL clocks device name
  >>   ARM: OMAP: USB: HOST TLL platform driver
  >>   ARM: OMAP: USB: Invoke the TLL driver from USB HS core driver
  >>   ARM: OMAP: USB: Remove TLL specific code from USB HS core driver
  >>   ARM: OMAP: Remove older device name of the USB TLL clocks
  >>
  >>  arch/arm/mach-omap2/clock3xxx_data.c  |8 +-
  >>  arch/arm/mach-omap2/clock44xx_data.c  |4 +-
  >>  arch/arm/mach-omap2/usb-host.c|   31 ++-
  >>  arch/arm/plat-omap/include/plat/usb.h |7 +
  >>  drivers/mfd/Kconfig   |2 +-
  >>  drivers/mfd/Makefile  |2 +-
  >>  drivers/mfd/omap-usb-host.c   |  238 ++---
  >>  drivers/mfd/omap-usb-tll.c|  471 
  >> +
  >>  8 files changed, 523 insertions(+), 240 deletions(-)
  >>  create mode 100644 drivers/mfd/omap-usb-tll.c
  >>
  >> --
  >> 1.7.9.5
  >
  >
  > Felipe/ Paul
  >   please let me know if you have any review comments on this v4 
  > series.
  >
  > regards
  > keshava
 
  Hi Felipe
    please let me know if you have any review comments on this 
  series now.
 >>>
 >>> looks ok... pretty much just moving code around.
 >>>
 >>> --
 >>> balbi
 >>
 >>
 >> Thanks Felipe
 >>
 >> then I request please give your Ack by for this series.
 >>
 >> regards
 >> keshava
 >
 > Hi Paul
 > do you have any review comments on this series?
 > Felipe is OK with this series.  if there are no review comments on this 
 > series
 > I request your ack by for the same.
 > Once this series gets in to mainline. i will start the Device tree
 > conversion for usb2 host.
 >
 > regards
 > keshava

 Hi Felipe
please give you ack by this series , so that I request
 samuel to merge to mainline.
>>>
>>> sure, here you go
>>>
>>> Acked-by: Felipe Balbi 
>>>
>>> --
>>> balbi
>>
>>
>> Thanks Felipe
>>
>> Samuel
>>   I request please queue this series for the next merge window.
>>
>> regards
>> keshava
>
>
> samuel : 

Re: [PATCH V4 0/5] ARM: OMAP: HOST: TLL driver implementation

2012-09-19 Thread Samuel Ortiz
Hi Keshava,

On Mon, Jul 16, 2012 at 07:01:06PM +0530, Keshava Munegowda wrote:
> The TLL (Transceiver Less Link) is an separate IP block, independent of
> the host controller. Basically this TLL operates like USB PHY which allows
> the user to connect two USB transceiver interfaces together directly
> without the use of differential transceivers in omap3 and later chips.
> The TLL configuration is removed from the UHH driver and implemented as
> a seperate platform driver. Now, the UHH driver configures the TLL
> through API's exported by the TLL platform driver.
> 
> Signed-off-by: Keshava Munegowda 
> 
> In v4:
> - rebased on top of linux kernel version 3.5.rc7
> - reworked as per the comments given by Paul Walmsley 
> 
> In v3:
>   - rebased on top V3 of Russ dill's patch
>'ARM: OMAP3: USB: Fix the EHCI ULPI PHY reset issue'
>fixes an issue where the ULPI PHYs were not held in reset
>while initializing the EHCI controller
>   http://permalink.gmane.org/gmane.linux.usb.general/65988
>   
>   - rebased on top of patch 
> OMAP: USB : Fix the EHCI enumeration and core retention issue
>  http://permalink.gmane.org/gmane.linux.usb.general/66239
> 
> In V2:
> - covered review comments from linux omap and usb community
> - rebased on top Russ dill's patch
>'ARM: OMAP3: USB: Fix the EHCI ULPI PHY reset issue'
>fixes an issue where the ULPI PHYs were not held in reset
>while initializing the EHCI controller
> 
> Keshava Munegowda (5):
>   ARM: OMAP: Add the USB TLL clocks device name
>   ARM: OMAP: USB: HOST TLL platform driver
>   ARM: OMAP: USB: Invoke the TLL driver from USB HS core driver
>   ARM: OMAP: USB: Remove TLL specific code from USB HS core driver
>   ARM: OMAP: Remove older device name of the USB TLL clocks
All 5 patches applied now. I had to manually apply patches #1 and #5. Could
you please check that it's looking good to you ?

Cheers,
Samuel.

-- 
Intel Open Source Technology Centre
http://oss.intel.com/
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [PATCH V4 0/5] ARM: OMAP: HOST: TLL driver implementation

2012-09-19 Thread Paul Walmsley

Hi Samuel,

I've queued patch 1 of this series for 3.7, which should go upstream via 
the OMAP -> arm-soc path.  Also asked Keshava to re-send patch 5 to me 
once patches 2-4 have been merged.

It's up to you how to handle patches 2-4.  The series is a good step 
forward for us in terms of cleanup.  But what is probably worthwhile at 
some point is for that USB TLL "phy" code (added in patch 2) to be moved 
into some place like drivers/usb/phy, since it's not MFD-related.


- Paul
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [PATCH V4 0/5] ARM: OMAP: HOST: TLL driver implementation

2012-09-21 Thread Samuel Ortiz
Hi Paul,

On Wed, Sep 19, 2012 at 08:39:40PM +, Paul Walmsley wrote:
> 
> Hi Samuel,
> 
> I've queued patch 1 of this series for 3.7, which should go upstream via 
> the OMAP -> arm-soc path.  Also asked Keshava to re-send patch 5 to me 
> once patches 2-4 have been merged.
> 
> It's up to you how to handle patches 2-4.  The series is a good step 
> forward for us in terms of cleanup.  But what is probably worthwhile at 
> some point is for that USB TLL "phy" code (added in patch 2) to be moved 
> into some place like drivers/usb/phy, since it's not MFD-related.
That would be ideal, yes. I kept patches 2-4 as they're alreeady going in the
right direction (I dropped patches 1 and 5).

Thanks for the heads up.

Cheers,
Samuel.

-- 
Intel Open Source Technology Centre
http://oss.intel.com/
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [PATCH V4 0/5] ARM: OMAP: HOST: TLL driver implementation

2012-09-24 Thread Munegowda, Keshava
On Sat, Sep 22, 2012 at 3:37 AM, Samuel Ortiz  wrote:
> Hi Paul,
>
> On Wed, Sep 19, 2012 at 08:39:40PM +, Paul Walmsley wrote:
>>
>> Hi Samuel,
>>
>> I've queued patch 1 of this series for 3.7, which should go upstream via
>> the OMAP -> arm-soc path.  Also asked Keshava to re-send patch 5 to me
>> once patches 2-4 have been merged.
>>
>> It's up to you how to handle patches 2-4.  The series is a good step
>> forward for us in terms of cleanup.  But what is probably worthwhile at
>> some point is for that USB TLL "phy" code (added in patch 2) to be moved
>> into some place like drivers/usb/phy, since it's not MFD-related.
> That would be ideal, yes. I kept patches 2-4 as they're alreeady going in the
> right direction (I dropped patches 1 and 5).
>
> Thanks for the heads up.
>
> Cheers,
> Samuel.
>
> --
> Intel Open Source Technology Centre
> http://oss.intel.com/


thanks paul and Samuel

regards
keshava

regards
keshava
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html