From: gerg@snapgear•com (Greg Ungerer)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 4/4] ARM: ks8695: convert to generic time and clocksource
Date: Mon, 3 Sep 2012 14:41:12 +1000 [thread overview]
Message-ID: <504434E8.9040205@snapgear.com> (raw)
In-Reply-To: <201209021849.54348.arnd@arndb.de>
Hi Arnd,
On 03/09/12 04:49, Arnd Bergmann wrote:
> On Friday 31 August 2012, Linus Walleij wrote:
>> On Fri, Aug 31, 2012 at 8:20 AM, Greg Ungerer <gerg@snapgear•com> wrote:
>>
>>> Ok, tested on a KS8695 based machine. Boots and runs, obviously
>>> clock is basically working. But 'date' never shows the time
>>> increasing:
>>>
>>> # date
>>> Thu Jan 1 00:00:00 UTC 1970
>>> # date
>>> Thu Jan 1 00:00:00 UTC 1970
>>> # date
>>> Thu Jan 1 00:00:00 UTC 1970
>>> #
>>>
>>> And yes, that did work before applying this patch :-)
>>
>> That mean clockevent is running but not clocksource.
>>
>> And I think that is because I forgot a ~ in the mask for disabling
>> the T1 timer, so setting up the clockevent disables the clocksource ...
>>
>> I'll send out a fixed version, plese test!
>>
>> (BTW I had not clue the 68K maintainer had a platform like
>> this, fun!)
>
> Note that this platform is one of those we talked about removing
> from the kernel for potentially being completely unused. Do we have
> reason to believe that people are still using ks8695 for anything
> with new kernels?
I'll put my hand up as a user of it. I run every release kernel
on KS8695 platforms, though I don't tend to do much testing of
rc kernels on it.
> If any of you are doing that, we'll definitely keep the port around,
> the idea is not to break anything that people are actually using.
> In that case, I would like to see a MAINTAINERS entry for the platform
> so we have a contact for someone who is able to ack and maybe test
> patches.
I am happy enough to ack and test changes, if no one else wants to
do it. I don't expect to do any real active development on it though.
I do have some board files that would have been nice to push into
mainline, but I have been holding off (for quite a while), hoping
that someone might support DTs on this sub-arch.
Regards
Greg
------------------------------------------------------------------------
Greg Ungerer -- Principal Engineer EMAIL: gerg at snapgear.com
SnapGear Group, McAfee PHONE: +61 7 3435 2888
8 Gardner Close FAX: +61 7 3217 5323
Milton, QLD, 4064, Australia WEB: http://www.SnapGear.com
next prev parent reply other threads:[~2012-09-03 4:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-29 18:27 [PATCH 4/4] ARM: ks8695: convert to generic time and clocksource Linus Walleij
2012-08-31 6:20 ` Greg Ungerer
2012-08-31 23:43 ` Linus Walleij
2012-09-02 11:45 ` Greg Ungerer
2012-09-02 18:49 ` Arnd Bergmann
2012-09-03 4:41 ` Greg Ungerer [this message]
2012-09-03 11:15 ` Arnd Bergmann
2012-09-03 12:51 ` Greg Ungerer
2012-09-03 12:02 ` Linus Walleij
2012-09-03 12:57 ` Greg Ungerer
2012-09-03 13:24 ` Arnd Bergmann
2012-09-03 14:55 ` Andrew Victor
2012-09-05 5:05 ` Olof Johansson
2012-09-07 5:42 ` Greg Ungerer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=504434E8.9040205@snapgear.com \
--to=gerg@snapgear$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox