From: Jonathan Cameron <jic23@kernel.org>
To: Maxime Ripard <maxime.ripard@free-electrons.com>
Cc: linux-iio@vger.kernel.org
Subject: Re: [PATCH 2/2] Move RTC trigger to in-core frequency support
Date: Tue, 24 Apr 2012 09:22:00 +0100 [thread overview]
Message-ID: <4F9662A8.5020905@kernel.org> (raw)
In-Reply-To: <1334851538-21408-3-git-send-email-maxime.ripard@free-electrons.com>
On 4/19/2012 5:05 PM, Maxime Ripard wrote:
The irony here is that I was going to suggest we droped this driver entirely
as I didn't think anyone was using it! Guess they are given you've gone
to the effort of cleaning it up.
One trivial change inline. Otherwise looks good.
> Signed-off-by: Maxime Ripard<maxime.ripard@free-electrons.com>
> ---
> .../staging/iio/trigger/iio-trig-periodic-rtc.c | 50 ++++----------------
> 1 files changed, 10 insertions(+), 40 deletions(-)
>
> diff --git a/drivers/staging/iio/trigger/iio-trig-periodic-rtc.c b/drivers/staging/iio/trigger/iio-trig-periodic-rtc.c
> index a80cf67..ffabf80 100644
> --- a/drivers/staging/iio/trigger/iio-trig-periodic-rtc.c
> +++ b/drivers/staging/iio/trigger/iio-trig-periodic-rtc.c
> @@ -24,7 +24,6 @@ static DEFINE_MUTEX(iio_prtc_trigger_list_lock);
>
> struct iio_prtc_trigger_info {
> struct rtc_device *rtc;
> - int frequency;
> struct rtc_task task;
> };
>
> @@ -37,50 +36,19 @@ static int iio_trig_periodic_rtc_set_state(struct iio_trigger *trig, bool state)
> return rtc_irq_set_state(trig_info->rtc,&trig_info->task, state);
> }
>
> -static ssize_t iio_trig_periodic_read_freq(struct device *dev,
> - struct device_attribute *attr,
> - char *buf)
> +static int update_infos(struct iio_trigger *trig, const unsigned long mask)
> {
> - struct iio_trigger *trig = dev_get_drvdata(dev);
> struct iio_prtc_trigger_info *trig_info = trig->private_data;
> - return sprintf(buf, "%u\n", trig_info->frequency);
> -}
> -
> -static ssize_t iio_trig_periodic_write_freq(struct device *dev,
> - struct device_attribute *attr,
> - const char *buf,
> - size_t len)
> -{
> - struct iio_trigger *trig = dev_get_drvdata(dev);
> - struct iio_prtc_trigger_info *trig_info = trig->private_data;
> - unsigned long val;
> - int ret;
> -
> - ret = strict_strtoul(buf, 10,&val);
> - if (ret)
> - goto error_ret;
> -
> - ret = rtc_irq_set_freq(trig_info->rtc,&trig_info->task, val);
> - if (ret)
> - goto error_ret;
> -
> - trig_info->frequency = val;
>
> - return len;
> -
> -error_ret:
> - return ret;
> + switch (mask) {
> + case IIO_TRIGGER_INFO_FREQUENCY:
> + return rtc_irq_set_freq(trig_info->rtc,&trig_info->task,
> + trig->frequency);
> + default:
return -EINVAL. Any other write is an error, not a clean return. Of course
it can't happen, but still best to be clear we aren't happy if it does!
> + return 0;
> + }
> }
>
> -static DEVICE_ATTR(frequency, S_IRUGO | S_IWUSR,
> - iio_trig_periodic_read_freq,
> - iio_trig_periodic_write_freq);
> -
> -static struct attribute *iio_trig_prtc_attrs[] = {
> - &dev_attr_frequency.attr,
> - NULL,
> -};
> -
> static const struct attribute_group iio_trig_prtc_attr_group = {
> .attrs = iio_trig_prtc_attrs,
> };
> @@ -99,6 +67,7 @@ static void iio_prtc_trigger_poll(void *private_data)
> static const struct iio_trigger_ops iio_prtc_trigger_ops = {
> .owner = THIS_MODULE,
> .set_trigger_state =&iio_trig_periodic_rtc_set_state,
> + .update_infos =&iio_trig_periodic_rtc_update_infos,
> };
>
> static int iio_trig_periodic_rtc_probe(struct platform_device *dev)
> @@ -124,6 +93,7 @@ static int iio_trig_periodic_rtc_probe(struct platform_device *dev)
> ret = -ENOMEM;
> goto error_put_trigger_and_remove_from_list;
> }
> + trig->info_mask = IIO_TRIGGER_INFO_FREQUENCY;
> trig->private_data = trig_info;
> trig->ops =&iio_prtc_trigger_ops;
> /* RTC access */
next prev parent reply other threads:[~2012-04-24 8:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-19 16:05 [RFC] Add frequency support in trigger core Maxime Ripard
2012-04-19 16:05 ` [PATCH 1/2] IIO: Add frequency sysfs files to triggers Maxime Ripard
2012-04-24 8:19 ` Jonathan Cameron
2012-04-26 13:48 ` Maxime Ripard
2012-04-19 16:05 ` [PATCH 2/2] Move RTC trigger to in-core frequency support Maxime Ripard
2012-04-24 8:22 ` Jonathan Cameron [this message]
2012-04-24 8:36 ` Maxime Ripard
2012-04-24 9:10 ` Jonathan Cameron
2012-04-24 8:12 ` [RFC] Add frequency support in trigger core Jonathan Cameron
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=4F9662A8.5020905@kernel.org \
--to=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=maxime.ripard@free-electrons.com \
/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).