From: rmallon@gmail.com (Ryan Mallon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: ep93xx: clockevent support
Date: Fri, 10 Aug 2012 07:02:41 +1000 [thread overview]
Message-ID: <50242571.70402@gmail.com> (raw)
In-Reply-To: <CANapsLQ6kCUN5UoaA3xejm24SGxCKmZEFgmR_+r7N-=DPz0TVA@mail.gmail.com>
On 09/08/12 18:54, Yan Burman wrote:
> On 8/7/12, Ryan Mallon <rmallon@gmail.com> wrote:
>> On 07/08/12 21:21, Yan Burman wrote:
>>
>>> ARM: ep93xx: clockevent support
>>> I have ported to 3.6-rc1 and slightly modified a previous patch for
>>> clockevent support for the ep93xx.
>>> The porting mainly consists of sched_clock support.
>>> Tested on 9302 based board.
>>> From: Ahmed Ammar <aammar <at> edge-techno.com>
>>> Signed-off-by: Yan Burman <burman.yan@gmail.com>
>>
>>
>> Hi Yan, some comments below.
>>
>> ~Ryan
>>
>>> + case CLOCK_EVT_MODE_ONESHOT:
>>> + tmode |= EP93XX_TIMER123_CONTROL_ENABLE;
>>> + __raw_writel(tmode, EP93XX_TIMER1_CONTROL);
>>> + break;
>>> +
>>> + case CLOCK_EVT_MODE_SHUTDOWN:
>>> + case CLOCK_EVT_MODE_UNUSED:
>>> + case CLOCK_EVT_MODE_RESUME:
>>> + return;
>>
>>
>> These cases can be removed.
>>
>
> This case is something that is present in most (if not all) other architectures.
> I don't mind removing it, but it will have to be replaced with:
> default:
> ;
>
> Since GCC produces warnings otherwise.
Oh, I missed the fact the switch was on an enum. You are correct, we
should keep the code consistent with other architectures, so this
can be left as is.
> Other than that I am going to wait a while more for more comments if
> somebody has them,
> and post a new version with style fixes as well as switch to
> drivers/clocksource/mmio.c usage.
Great, thanks,
~Ryan
next prev parent reply other threads:[~2012-08-09 21:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-07 11:21 [PATCH] ARM: ep93xx: clockevent support Yan Burman
2012-08-07 13:03 ` Ryan Mallon
2012-08-07 17:47 ` H Hartley Sweeten
2012-08-09 8:54 ` Yan Burman
2012-08-09 21:02 ` Ryan Mallon [this message]
2012-08-07 14:37 ` Russell King - ARM Linux
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=50242571.70402@gmail.com \
--to=rmallon@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).