From: Jonathan Cameron <jic23@cam.ac.uk>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: linux-iio@vger.kernel.org
Subject: Re: [PATCH 1/2] staging:iio:trigger: Use to_iio_trigger() instead of dev_get_drvdata()
Date: Thu, 21 Jun 2012 15:19:36 +0100 [thread overview]
Message-ID: <4FE32D78.9@cam.ac.uk> (raw)
In-Reply-To: <1340037978-16915-1-git-send-email-lars@metafoo.de>
On 6/18/2012 5:46 PM, Lars-Peter Clausen wrote:
> Use to_iio_trigger(dev) instead of dev_get_drvdata(dev). Both will return the
> trigger which belongs to the device, but the the first on is a bit more
> lightweight. Also this will eventually free up the drvdata pointer of the device
> for driver specific data.
>
> Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
Acked-by: Jonathan Cameron <jic23@kernel.org>
> ---
> drivers/staging/iio/trigger/iio-trig-bfin-timer.c | 4 ++--
> drivers/staging/iio/trigger/iio-trig-periodic-rtc.c | 4 ++--
> drivers/staging/iio/trigger/iio-trig-sysfs.c | 2 +-
> 3 files changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/staging/iio/trigger/iio-trig-bfin-timer.c b/drivers/staging/iio/trigger/iio-trig-bfin-timer.c
> index f85734d..ce6a7b1 100644
> --- a/drivers/staging/iio/trigger/iio-trig-bfin-timer.c
> +++ b/drivers/staging/iio/trigger/iio-trig-bfin-timer.c
> @@ -60,7 +60,7 @@ struct bfin_tmr_state {
> static ssize_t iio_bfin_tmr_frequency_store(struct device *dev,
> struct device_attribute *attr, const char *buf, size_t count)
> {
> - struct iio_trigger *trig = dev_get_drvdata(dev);
> + struct iio_trigger *trig = to_iio_trigger(dev);
> struct bfin_tmr_state *st = trig->private_data;
> long val;
> int ret;
> @@ -97,7 +97,7 @@ static ssize_t iio_bfin_tmr_frequency_show(struct device *dev,
> struct device_attribute *attr,
> char *buf)
> {
> - struct iio_trigger *trig = dev_get_drvdata(dev);
> + struct iio_trigger *trig = to_iio_trigger(dev);
> struct bfin_tmr_state *st = trig->private_data;
>
> return sprintf(buf, "%lu\n",
> diff --git a/drivers/staging/iio/trigger/iio-trig-periodic-rtc.c b/drivers/staging/iio/trigger/iio-trig-periodic-rtc.c
> index 9f2d055..4ceaa18 100644
> --- a/drivers/staging/iio/trigger/iio-trig-periodic-rtc.c
> +++ b/drivers/staging/iio/trigger/iio-trig-periodic-rtc.c
> @@ -41,7 +41,7 @@ static ssize_t iio_trig_periodic_read_freq(struct device *dev,
> struct device_attribute *attr,
> char *buf)
> {
> - struct iio_trigger *trig = dev_get_drvdata(dev);
> + struct iio_trigger *trig = to_iio_trigger(dev);
> struct iio_prtc_trigger_info *trig_info = trig->private_data;
> return sprintf(buf, "%u\n", trig_info->frequency);
> }
> @@ -51,7 +51,7 @@ static ssize_t iio_trig_periodic_write_freq(struct device *dev,
> const char *buf,
> size_t len)
> {
> - struct iio_trigger *trig = dev_get_drvdata(dev);
> + struct iio_trigger *trig = to_iio_trigger(dev);
> struct iio_prtc_trigger_info *trig_info = trig->private_data;
> unsigned long val;
> int ret;
> diff --git a/drivers/staging/iio/trigger/iio-trig-sysfs.c b/drivers/staging/iio/trigger/iio-trig-sysfs.c
> index 552763b..fee4746 100644
> --- a/drivers/staging/iio/trigger/iio-trig-sysfs.c
> +++ b/drivers/staging/iio/trigger/iio-trig-sysfs.c
> @@ -92,7 +92,7 @@ static struct device iio_sysfs_trig_dev = {
> static ssize_t iio_sysfs_trigger_poll(struct device *dev,
> struct device_attribute *attr, const char *buf, size_t count)
> {
> - struct iio_trigger *trig = dev_get_drvdata(dev);
> + struct iio_trigger *trig = to_iio_trigger(dev);
> iio_trigger_poll_chained(trig, 0);
>
> return count;
>
next prev parent reply other threads:[~2012-06-21 14:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-18 16:46 [PATCH 1/2] staging:iio:trigger: Use to_iio_trigger() instead of dev_get_drvdata() Lars-Peter Clausen
2012-06-18 16:46 ` [PATCH 2/2] iio:trigger: " Lars-Peter Clausen
2012-06-21 14:20 ` Jonathan Cameron
2012-06-21 14:19 ` Jonathan Cameron [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-06-21 17:10 [PATCH 1/2] staging:iio:trigger: " Lars-Peter Clausen
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=4FE32D78.9@cam.ac.uk \
--to=jic23@cam.ac.uk \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.