RE: [PATCH v5 0/12] dmtimer adaptation to platform_driver

2010-12-14 Thread DebBarma, Tarun Kanti
Kevin,
 -Original Message-
 From: Kevin Hilman [mailto:khil...@deeprootsystems.com]
 Sent: Wednesday, December 15, 2010 7:37 AM
 To: DebBarma, Tarun Kanti
 Cc: linux-omap@vger.kernel.org
 Subject: Re: [PATCH v5 0/12] dmtimer adaptation to platform_driver
 
 Tarun Kanti DebBarma tarun.ka...@ti.com writes:
 
  dmtimer adaptation to platform_driver.
 
  This patch series is adaptation of dmtimer code to platform driver
  using omap_device and omap_hwmod abstraction.
 
  Tested on following platforms:
  OMAP4430, OMAP3430, OMAP3630, OMAP2430
  OMAP2420 -- Image with omap2plus_defconfig in too large to download on
 N800.
 
 And OMAP1?
BTW, I have posted v6 yesterday and in that for testing on N800
I have removed OMAP3 and OMAP4 options and I was able to download.

Coming to OMAP1, I am getting Bad Magic Number while download.
Looks like there is problem in selecting the right platform info.
I am trying to resolve this and test.
--
Tarun

 
 Kevin
--
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 v5 0/12] dmtimer adaptation to platform_driver

2010-12-13 Thread Kevin Hilman
DebBarma, Tarun Kanti tarun.ka...@ti.com writes:

 On Tue, Dec 07, 2010 at 05:14:07AM +0530, Tarun Kanti DebBarma wrote:
  dmtimer adaptation to platform_driver.
 
  This patch series is adaptation of dmtimer code to platform driver
  using omap_device and omap_hwmod abstraction.
 
  Tested on following platforms:
  OMAP4430, OMAP3430, OMAP3630, OMAP2430
  OMAP2420 -- Image with omap2plus_defconfig in too large to download on
 N800.
 
 How about omap1? The mainline code happily compiles and boots on osk5912
 but this series is going to break omap1 build.

 I have built and booted on OMAP1 during v3. This time I could not because
 My OMAP1710 has gone bad. I am looking for one to test.
 That's precisely the reason I have not mentioned OMAP1. 

Rather than not mentioning OMAP1, you should state whether (or not) it
was tested on OMAP1.   As build/boot testing on OMAP1 is a requirement
for merge, this information is crucial.

Kevin


--
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 v5 0/12] dmtimer adaptation to platform_driver

2010-12-13 Thread Paul Walmsley
On Tue, 7 Dec 2010, Tarun Kanti DebBarma wrote:

 Tested on following platforms:
 OMAP4430, OMAP3430, OMAP3630, OMAP2430
 OMAP2420 -- Image with omap2plus_defconfig in too large to download on N800.

Just build a minimal N800 config for testing.  It's really quite easy.  
Use 'make menuconfig' and then you can remove lots of unnecessary stuff.


- 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 v5 0/12] dmtimer adaptation to platform_driver

2010-12-06 Thread G, Manjunath Kondaiah
On Tue, Dec 07, 2010 at 05:14:07AM +0530, Tarun Kanti DebBarma wrote:
 dmtimer adaptation to platform_driver.
 
 This patch series is adaptation of dmtimer code to platform driver
 using omap_device and omap_hwmod abstraction.
 
 Tested on following platforms:
 OMAP4430, OMAP3430, OMAP3630, OMAP2430
 OMAP2420 -- Image with omap2plus_defconfig in too large to download on N800.

How about omap1? The mainline code happily compiles and boots on osk5912
but this series is going to break omap1 build.

As per Tony's comments for GPIO and DMA hwmod, the changes should build and
boot for omap1 also.

-Manjunath

[...]
--
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 v5 0/12] dmtimer adaptation to platform_driver

2010-12-06 Thread DebBarma, Tarun Kanti
 -Original Message-
 From: G, Manjunath Kondaiah [mailto:manj...@ti.com]
 Sent: Monday, December 06, 2010 9:59 PM
 To: DebBarma, Tarun Kanti
 Cc: linux-omap@vger.kernel.org
 Subject: Re: [PATCH v5 0/12] dmtimer adaptation to platform_driver
 
 On Tue, Dec 07, 2010 at 05:14:07AM +0530, Tarun Kanti DebBarma wrote:
  dmtimer adaptation to platform_driver.
 
  This patch series is adaptation of dmtimer code to platform driver
  using omap_device and omap_hwmod abstraction.
 
  Tested on following platforms:
  OMAP4430, OMAP3430, OMAP3630, OMAP2430
  OMAP2420 -- Image with omap2plus_defconfig in too large to download on
 N800.
 
 How about omap1? The mainline code happily compiles and boots on osk5912
 but this series is going to break omap1 build.
I have built and booted on OMAP1 during v3. This time I could not because
My OMAP1710 has gone bad. I am looking for one to test.
That's precisely the reason I have not mentioned OMAP1. 

 
 As per Tony's comments for GPIO and DMA hwmod, the changes should build
 and
 boot for omap1 also.
Yes, I guess this is quite understood. Thanks anyways.

--
Tarun

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