Re: [RFC] [PATCH] ARM: OMAP1: Add clocksource driver for OMAP1

[Dirk Behme <dirk.behme@googlemail.com>]

Daniel Walker wrote:
> On Sat, 2006-12-02 at 07:11 +0100, Dirk Behme wrote:
> 
>>>When Thomas did his -mm update all the clocksources got dropped
>>
>>I'm not talking about (OMAP) clocksource here. I'm talking 
>>about the rest [3], especially OMAP clockevent patch.
> 
> ok.
> 
>>- OMAP clockevent is potentially something for this list as 
>>well. But currently, it isn't discussed here and I can't 
>>find it discussed or included anywhere else. So it looks to 
>>me that it is lost (until anybody cares again). This is the 
>>core of my question: Is it currently nowhere maintained?
> 
> I guess Kevin and I maintain it. It's not such a large piece of code.
> The reason that it's not getting pushed hard at the moment is because
> HRT is testing in -mm .. So we're at a limbo point when we can't move
> the code to RMK, and it's not really appropriate for the code to go into
> -mm .. We just have to wait till HRT gets shaken out in -mm .
> 
> The reason we are able to send the clocksource to RMK is cause generic
> time went into the 2.6.18 stable release.
> 
>>- The other patches, e.g. for ixp4xx and versatile, I think 
>>nobody will care on this list and update them here. So until 
>>they are not handled somewhere else (are they?), they will 
>>be lost as well.
>>
>>>Nothing should go via Thomas.
>>
>>You originally sent most of the patches to Thomas, don't you? ;)
> 
> Yes, before HRT went to -mm. The reason that it was useful to send them
> to Thomas was for our own testing, and progressing HRT at an early
> point. I wouldn't have minded if the OMAP clockevents when into -mm ,
> but I've never seen anything like that happen (i.e. non-i386 board
> specific code going into -mm).

Okay. Many thanks for clarifying these tricky dependencies!

Looks like then nothing is lost, only "waiting". Would be 
nice if you can keep us updated regarding this.

Dirk