From: tglx@linutronix.de (Thomas Gleixner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] clockevents: introduce ->set_dev_mode() which can return error
Date: Fri, 23 Jan 2015 12:57:28 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.11.1501231223470.5526@nanos> (raw)
In-Reply-To: <1418162614-19182-2-git-send-email-khilman@kernel.org>
On Tue, 9 Dec 2014, Kevin Hilman wrote:
> diff --git a/kernel/time/clockevents.c b/kernel/time/clockevents.c
> index 55449909f114..f7614041240e 100644
> --- a/kernel/time/clockevents.c
> +++ b/kernel/time/clockevents.c
> @@ -105,7 +105,16 @@ void clockevents_set_mode(struct clock_event_device *dev,
> enum clock_event_mode mode)
> {
> if (dev->mode != mode) {
> - dev->set_mode(mode, dev);
> + if (dev->set_dev_mode) {
> + int ret = dev->set_dev_mode(mode, dev);
> +
> + /* Currently available modes shouldn't fail */
> + WARN_ONCE(ret, "Requested mode: %d, error: %d\n",
> + mode, ret);
> + } else {
> + dev->set_mode(mode, dev);
> + }
> +
> dev->mode = mode;
>
> /*
> @@ -448,8 +457,14 @@ int __clockevents_update_freq(struct clock_event_device *dev, u32 freq)
> if (dev->mode == CLOCK_EVT_MODE_ONESHOT)
> return clockevents_program_event(dev, dev->next_event, false);
>
> - if (dev->mode == CLOCK_EVT_MODE_PERIODIC)
> - dev->set_mode(CLOCK_EVT_MODE_PERIODIC, dev);
> + if (dev->mode == CLOCK_EVT_MODE_PERIODIC) {
> + /* Shouldn't fail while switching to PERIODIC MODE */
> + if (dev->set_dev_mode)
> + WARN_ON_ONCE(dev->set_dev_mode(CLOCK_EVT_MODE_PERIODIC,
> + dev));
> + else
> + dev->set_mode(CLOCK_EVT_MODE_PERIODIC, dev);
Please split that out into
static int __clockevents_set_mode(dev, mode)
{
int ret = 0;
if (dev->set_dev_mode) {
ret = set_dev_mode(mode, dev);
WARN_ON_ONCE(ret);
} else {
dev->set_mode(CLOCK_EVT_MODE_PERIODIC, dev);
}
return ret;
}
Now looking at the conversion patch, it looks like we add lots of
case X:
case Y:
return 0;
to avoid the
default:
return -ENOSYS;
After staring at that I'm less convinced about this approach. So lets
think about something different:
static int __clockevents_set_mode(dev, mode)
{
/* Transition mode */
if (dev->set_mode) {
if (mode > CLOCK_EVT_MODE_RESUME)
return -ENOSYS;
dev->set_mode(mode, dev);
return 0;
}
if (dev->features & CLOCK_EVT_FEAT_DUMMY)
return 0;
switch (mode) {
/*
* This is an internal state, which is guaranteed to
* go from SHUTDOWN to UNUSED. No driver interaction
* required.
*/
case CLOCK_EVT_MODE_UNUSED:
return 0;
case CLOCK_EVT_MODE_SHUTDOWN:
return dev->shutdown(dev);
case CLOCK_EVT_MODE_PERIODIC:
/* Core internal bug */
if (!(dev->features & CLOCK_EVT_FEAT_PERIODIC))
return -ENOSYS;
return dev->setup_periodic(dev);
case CLOCK_EVT_MODE_ONESHOT:
/* Core internal bug */
if (!(dev->features & CLOCK_EVT_FEAT_ONESHOT))
return -ENOSYS;
return dev->setup_oneshot(dev);
case CLOCK_EVT_MODE_RESUME:
return dev->setup_resume(dev);
default:
return -ENOSYS;
}
And do sanity checking on registration time:
static int ce_check(dev)
{
if (dev->set_mode)
return 0;
if (dev->features & CLOCK_EVT_FEAT_DUMMY)
return 0;
if (!dev->shutdown)
return -EMORON;
if ((dev->features & CLOCK_EVT_FEAT_PERIODIC) &&
!dev->setup_periodic)
return -EMORON;
if ((dev->features & CLOCK_EVT_FEAT_ONESHOT) &&
!dev->setup_oneshot)
return -EMORON;
/* Optional callbacks */
if (!dev->setup_resume)
dev->setup_resume = setup_noop();
return 0;
}
That gives us a clear distinction of required and optional callbacks,
which will make error handling and recovery simpler as well.
Thanks,
tglx
next prev parent reply other threads:[~2015-01-23 11:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-09 22:03 [PATCH 0/2] clockevents: introduce ->set_dev_mode() and convert a few drivers Kevin Hilman
2014-12-09 22:03 ` [PATCH 1/2] clockevents: introduce ->set_dev_mode() which can return error Kevin Hilman
2014-12-10 3:27 ` Preeti U Murthy
2015-01-23 11:57 ` Thomas Gleixner [this message]
2015-01-25 13:57 ` Viresh Kumar
2015-01-25 15:03 ` Thomas Gleixner
2014-12-09 22:03 ` [PATCH 2/2] clockevents: migrate some drivers to new ->set_dev_mode() Kevin Hilman
2015-01-15 18:41 ` [PATCH 0/2] clockevents: introduce ->set_dev_mode() and convert a few drivers Kevin Hilman
2015-01-15 22:25 ` Thomas Gleixner
-- strict thread matches above, loose matches on Subject: below --
2014-11-19 18:39 Kevin Hilman
2014-11-19 18:39 ` [PATCH 1/2] clockevents: introduce ->set_dev_mode() which can return error Kevin Hilman
2014-11-20 4:04 ` Preeti U Murthy
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=alpine.DEB.2.11.1501231223470.5526@nanos \
--to=tglx@linutronix.de \
--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