Tony Lindgren wrote on Monday, September 19, 2011 11:11 PM:
> device driver)
>
> * Pedanekar, Hemant [110918 20:32]:
>>
>> Tony,
>> Kernel boots fine on TI816X (should also boot on TI814X) with your patch
>> and patches (including OSC clock fix) from series
>> http://www.spinics.net/lists/linux
* Mohammed, Afzal [110918 21:48]:
> Hi Tony,
>
> On Sat, Sep 17, 2011 at 07:05:31, Tony Lindgren wrote:
> >
> > Afzal, care to check if that works for AM335X/TI816X/TI814X?
>
> With following patch over yours, AM335X (the only board with me) boots up
> fine.
Thanks for catching that, will fol
* DebBarma, Tarun Kanti [110918 04:53]:
> >
> > But we can map the interrupt registers separately and then have
> > the rest start from func_base that is different based on the timer
> > version. Rebasing the rest of the dmtimer hwmod patches on this
> > should be fairly easy, mostly just need to
* Pedanekar, Hemant [110918 20:32]:
>
> Tony,
> Kernel boots fine on TI816X (should also boot on TI814X) with your patch
> and patches (including OSC clock fix) from series
> http://www.spinics.net/lists/linux-omap/msg57011.html
OK good to hear, I assume I can add your Tested-by then?
Regards
Hi Tony,
On Sat, Sep 17, 2011 at 07:05:31, Tony Lindgren wrote:
>
> Afzal, care to check if that works for AM335X/TI816X/TI814X?
With following patch over yours, AM335X (the only board with me) boots up fine.
Regards
Afzal
From ff64a239e60f9b517860eb2fe9c4f88a188ca51d Mon Sep 17 00:00:00 2001
Tony Lindgren wrote on Saturday, September 17, 2011 7:06 AM:
> device driver)
>
> * DebBarma, Tarun Kanti [110916 01:56]:
>> [...]
>
> Afzal, care to check if that works for AM335X/TI816X/TI814X?
> It tried it briefly with omap4 gptimer3 as the clockevent and
> CONFIG_LOCAL_TIMER disabled.
>
[...]
> Well here's what I came up with to deal with the different timer
> registers. We can't use the context registers as those are for
> the value naturally..
>
> But we can map the interrupt registers separately and then have
> the rest start from func_base that is different based on the timer
* DebBarma, Tarun Kanti [110916 01:56]:
> [...]
> >>> 1. Modify the inline access functions to take the PEND and others
> >>> if needed registers as a parameter
> >>>
> >>> 2. Modify mach-omap2/timer.c to initialize the PEND and others
> >>> in the SoC specific timer_init function
> Just to
[...]
>>> 1. Modify the inline access functions to take the PEND and others
>>> if needed registers as a parameter
>>>
>>> 2. Modify mach-omap2/timer.c to initialize the PEND and others
>>> in the SoC specific timer_init function
Just to make my understanding complete, need some clarification
On Thu, Sep 15, 2011 at 10:35 PM, Tony Lindgren wrote:
> * Tony Lindgren [110915 09:24]:
>> * Mohammed, Afzal [110915 01:13]:
>> >
>> > We need clocksource & clockevent to be able to work with
>> > timers requiring addition of offsets. Without this AM335X,
>> > TI816X and TI814X SoC's will not b
* Tony Lindgren [110915 09:24]:
> * Mohammed, Afzal [110915 01:13]:
> >
> > We need clocksource & clockevent to be able to work with
> > timers requiring addition of offsets. Without this AM335X,
> > TI816X and TI814X SoC's will not boot.
>
> OK. Then how about let's do the following things:
>
* Mohammed, Afzal [110915 01:13]:
> Hi Tony,
>
> On Thu, Sep 15, 2011 at 11:12:53, DebBarma, Tarun Kanti wrote:
> > On Thu, Sep 15, 2011 at 3:15 AM, Tony Lindgren wrote:
> > > * Tarun Kanti DebBarma [110908 13:36]:
> > >> removed from timer code. New set of timers present on
> > >> OMAP4 are no
Hi Tony,
On Thu, Sep 15, 2011 at 11:12:53, DebBarma, Tarun Kanti wrote:
> On Thu, Sep 15, 2011 at 3:15 AM, Tony Lindgren wrote:
> > * Tarun Kanti DebBarma [110908 13:36]:
> >> removed from timer code. New set of timers present on
> >> OMAP4 are now supported.
> > Also, as we don't need the suppo
On Thu, Sep 15, 2011 at 3:15 AM, Tony Lindgren wrote:
> Hi,
>
> * Tarun Kanti DebBarma [110908 13:36]:
>> Register timer devices by going through hwmod database using
>> hwmod API. The driver probes each of the registered devices.
>> Functionality which are already performed by hwmod framework
>>
* Tony Lindgren [110914 14:12]:
>
> Also, as we don't need the support for different register offsets
> for the first two omap4 timers, please rather implement support
> for the new timers and the timeouts directly in plat-omap/dmtimer.c.
>
> That way we can still keep the minimal timer support
Hi,
* Tarun Kanti DebBarma [110908 13:36]:
> Register timer devices by going through hwmod database using
> hwmod API. The driver probes each of the registered devices.
> Functionality which are already performed by hwmod framework
> are removed from timer code. New set of timers present on
> OMA
16 matches
Mail list logo
