On Fri, May 11, 2012 at 03:06:48, Janusz Krzysztofik wrote:
Dnia czwartek, 3 maja 2012 13:28:58 Vaibhav Hiremath pisze:
Current OMAP code supports couple of clocksource options based
on compilation flag (CONFIG_OMAP_32K_TIMER). The 32KHz sync-timer
and a gptimer which can run on 32KHz or
Dnia czwartek, 3 maja 2012 13:28:58 Vaibhav Hiremath pisze:
Current OMAP code supports couple of clocksource options based
on compilation flag (CONFIG_OMAP_32K_TIMER). The 32KHz sync-timer
and a gptimer which can run on 32KHz or system clock (e.g 38.4 MHz)
This patch series cleans up the
Hi Janusz,
On Thu, 10 May 2012, Janusz Krzysztofik wrote:
Tried to test this branch, merged into 3.4-rc6, and with my Amstrad
Delta fixes applied, using my custom Amstrad Delta config, but initially
failed because an unrelated issue rised to the surface:
| LD .tmp_vmlinux1
|
* Janusz Krzysztofik jmkrzy...@gmail.com [120510 14:40]:
Otherwise, if configured with OMAP16xx selected, builds and seems to work
correctly for me, to the extent possible to verify without physical
access to the hardware. However, please note that the Amstrad Delta
doesn't make use of
Hello Janusz,
On Thu, 10 May 2012, Janusz Krzysztofik wrote:
Tried to test this branch, merged into 3.4-rc6, and with my Amstrad
Delta fixes applied, using my custom Amstrad Delta config, but initially
failed because an unrelated issue rised to the surface:
| LD .tmp_vmlinux1
|
* Vaibhav Hiremath hvaib...@ti.com [120503 01:02]:
Current OMAP code supports couple of clocksource options based
on compilation flag (CONFIG_OMAP_32K_TIMER). The 32KHz sync-timer
and a gptimer which can run on 32KHz or system clock (e.g 38.4 MHz)
I'll apply these into cleanup-timer branch
Current OMAP code supports couple of clocksource options based
on compilation flag (CONFIG_OMAP_32K_TIMER). The 32KHz sync-timer
and a gptimer which can run on 32KHz or system clock (e.g 38.4 MHz)
This patch series cleans up the existing 32k-sync timer implementation,
movind SoC init code to
