linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Baluta <daniel.baluta@intel.com>
To: jic23@kernel.org
Cc: knaack.h@gmx.de, lars@metafoo.de, pmeerw@pmeerw.net,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] staging: iio: trigger: Use standard attr for sampling frequency
Date: Wed, 11 Mar 2015 18:36:17 +0200	[thread overview]
Message-ID: <1426091777-30592-1-git-send-email-daniel.baluta@intel.com> (raw)

As written in Documentation/ABI/testing/sysfs-bus-iio the trigger
attribute for sampling frequency should be sampling_frequency.

Fix this for iio-trig-periodic-rtc module in order to prepare it
for moving out of staging.

Signed-off-by: Daniel Baluta <daniel.baluta@intel.com>
---
Jonathan, this module is very useful for devices that do not have
an interrupt pin.

We are working on drivers for such devices and would be very nice to
move this driver in advance to the IIO non-staging location.

What do you say?

 drivers/staging/iio/trigger/iio-trig-periodic-rtc.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/staging/iio/trigger/iio-trig-periodic-rtc.c b/drivers/staging/iio/trigger/iio-trig-periodic-rtc.c
index 89df1d3..f1cfe2d 100644
--- a/drivers/staging/iio/trigger/iio-trig-periodic-rtc.c
+++ b/drivers/staging/iio/trigger/iio-trig-periodic-rtc.c
@@ -87,12 +87,12 @@ error_ret:
 	return ret;
 }
 
-static DEVICE_ATTR(frequency, S_IRUGO | S_IWUSR,
+static DEVICE_ATTR(sampling_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,
+	&dev_attr_sampling_frequency.attr,
 	NULL,
 };
 
-- 
1.9.1

             reply	other threads:[~2015-03-11 16:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-11 16:36 Daniel Baluta [this message]
2015-03-12  8:16 ` [PATCH] staging: iio: trigger: Use standard attr for sampling frequency Octavian Purdila
2015-03-12  8:40   ` Lars-Peter Clausen
2015-03-12 12:48     ` Daniel Baluta
2015-03-14 17:21       ` Jonathan Cameron
2015-03-15 20:34         ` Daniel Baluta
2015-03-15 20:49           ` Jonathan Cameron
2015-03-15 20:52             ` Daniel Baluta
2015-03-18 15:04         ` Daniel Baluta
2015-03-18 16:47           ` Lars-Peter Clausen
2015-03-18 17:21             ` Daniel Baluta
2015-03-18 17:25               ` Lars-Peter Clausen
2015-03-21 11:44                 ` Jonathan Cameron
2015-03-14 17:26     ` 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=1426091777-30592-1-git-send-email-daniel.baluta@intel.com \
    --to=daniel.baluta@intel.com \
    --cc=jic23@kernel.org \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmeerw@pmeerw.net \
    /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).