On 10/10/11 11:42, Kukjin Kim wrote:
Padmavathi Venna wrote:

This patchset modifies the existing clkdev to make SPI driver
independent of the clock names send from platform data. This
patches enables the SPI driver to request SPI bus clocks
using generic connection ID.

V1 patch series are:
        http://www.spinics.net/lists/arm-kernel/msg141671.html

Changes since V1:
        -Add newly introduced CLKDEV_INIT macro for creating clk_lookup
        structure as suggested by Russell King
        V2 patches series are:
        http://www.spinics.net/lists/arm-kernel/msg142733.html

Changes since V2:
        -Reworked the patches as per the following link. Patch series in
        the following link removed&  and , from the macro declaration and
added
        in the macro defination.
        http://www.spinics.net/lists/arm-kernel/msg143663.html

Padmavathi Venna (4):
   ARM: S3C64XX: Add SPI clkdev support
   ARM: S5PC100: Add SPI clkdev support
   ARM: S5P64X0: Add SPI clkdev support
   ARM: S5PV210: Add SPI clkdev support

  arch/arm/mach-s3c64xx/clock.c         |   98 ++++++++++++++++--------
  arch/arm/mach-s5p64x0/clock-s5p6440.c |   57 +++++++++-----
  arch/arm/mach-s5p64x0/clock-s5p6450.c |   57 +++++++++-----
  arch/arm/mach-s5pc100/clock.c         |  132 ++++++++++++++++++++--------
-----
  arch/arm/mach-s5pv210/clock.c         |   58 ++++++++++-----
  5 files changed, 259 insertions(+), 143 deletions(-)

--
1.7.4.4
Looks ok but this needs 'CLKDEV_INIT' patch. Please wait until it can be
sent to upstream for this patch.

Padmavathi,

As I said, this looks ok and can be applied now.

Could you please rework this based on my next-samsung-dt branch which includes device tree patches so that I can apply this easily for v3.2?

If any problems, please let me know.

Thanks.

Best regards,
Kgene.
--
Kukjin Kim <[email protected]>, Senior Engineer,
SW Solution Development Team, Samsung Electronics Co., Ltd.
--
To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to