RE: [PATCH 0/3] ARM: OMAP1/2+: 32k-timer: Add hwmod lookup for 32k-timer

2012-03-07 Thread Hiremath, Vaibhav 
On Tue, Mar 06, 2012 at 04:27:52, Tony Lindgren wrote:
 * Hiremath, Vaibhav hvaib...@ti.com [120123 00:16]:
  On Thu, Jan 19, 2012 at 19:58:21, Hiremath, Vaibhav wrote:
   This patch series cleans up the existing 32k-sync timer implementation
   without any major code change and adds hwmod lookup for omap2+ devices,
   if lookup fails then fall back to gp-timer.
 ...
  
  Tony,
  
  If there are no review comments, can this be merged?
 
 Made a minor comment on the first patch, it would be nice to get
 that clean-up merged. The other two depend on some some hwmod
 data shrinkage by Paul..
 

Working on it, will be submitting next version soon.

Thanks,
Vaibhav

 Regards,
 
 Tony
 

--
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 0/3] ARM: OMAP1/2+: 32k-timer: Add hwmod lookup for 32k-timer

2012-03-05 Thread Tony Lindgren 
* Hiremath, Vaibhav hvaib...@ti.com [120123 00:16]:
 On Thu, Jan 19, 2012 at 19:58:21, Hiremath, Vaibhav wrote:
  This patch series cleans up the existing 32k-sync timer implementation
  without any major code change and adds hwmod lookup for omap2+ devices,
  if lookup fails then fall back to gp-timer.
...
 
 Tony,
 
 If there are no review comments, can this be merged?

Made a minor comment on the first patch, it would be nice to get
that clean-up merged. The other two depend on some some hwmod
data shrinkage by Paul..

Regards,

Tony
--
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 0/3] ARM: OMAP1/2+: 32k-timer: Add hwmod lookup for 32k-timer

2012-01-23 Thread Hiremath, Vaibhav 
On Thu, Jan 19, 2012 at 19:58:21, Hiremath, Vaibhav wrote:
 This patch series cleans up the existing 32k-sync timer implementation
 without any major code change and adds hwmod lookup for omap2+ devices,
 if lookup fails then fall back to gp-timer.
 
 With this, we should be able to support multi-omap boot
 including devices with/without 32k-sync timer.
 For example, AM33xx device doesn't have 32k-sync timer available,
 which breaks multi-omap boot.
 
 This patch-series has been boot tested on AM37xEVM platform, it
 would be helpful if somebody help me to validate it on OMAP2
 platform.
 
 Background:
 ==
 In 2010 timeframe 'Fillipe Balbi' had submitted first version
 of 32k-sync timer cleanup patches, but it did not made its way
 to the mainline.
 
 http://www.mail-archive.com/linux-omap@vger.kernel.org/msg37403.html
 
 Yesterday I had submitted the RFC version patch-series, which was
 built on top of earlier cleanup patches from 'Fillipe Balbi'.
 
 http://www.spinics.net/lists/linux-omap/msg63004.html
 
 Based on comments (Thanks to Russell, Marc and Tony) from community
 it was clear that, arch_init is not the correct way here.
 
 
 Vaibhav Hiremath (3):
   ARM: OMAP2+: 32k-counter: Use hwmod lookup to check presence of 32k
 timer
   ARM: OMAP2/3: Add idle_st bits for ST_32KSYNC timer to prcm-common
 header
   ARM: OMAP2+: hwmod data: Add 32k-sync timer data to hwmod database
 

Tony,

If there are no review comments, can this be merged?

Thanks,
Vaibhav

  arch/arm/mach-omap2/omap_hwmod_2420_data.c |   53 ++
  arch/arm/mach-omap2/omap_hwmod_2430_data.c |   52 +
  arch/arm/mach-omap2/omap_hwmod_3xxx_data.c |   51 +
  arch/arm/mach-omap2/omap_hwmod_44xx_data.c |2 +-
  arch/arm/mach-omap2/prcm-common.h  |4 +
  arch/arm/mach-omap2/timer.c|   27 -
  arch/arm/plat-omap/counter_32k.c   |   83 ++-
  7 files changed, 215 insertions(+), 57 deletions(-)
 
 

--
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