From: Alexandru Ardelean <alexandru.ardelean@analog.com>
To: <linux-iio@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <jic23@kernel.org>, Stefan Popa <stefan.popa@analog.com>,
Alexandru Ardelean <alexandru.ardelean@analog.com>
Subject: [PATCH 2/2] iio: imu: adis16480: Add the option to enable/disable burst mode
Date: Tue, 4 Aug 2020 13:04:14 +0300 [thread overview]
Message-ID: <20200804100414.39002-2-alexandru.ardelean@analog.com> (raw)
In-Reply-To: <20200804100414.39002-1-alexandru.ardelean@analog.com>
From: Stefan Popa <stefan.popa@analog.com>
Although the burst read function does not require a stall time between
each 16-bit segment, it however requires more processing since the
software needs to look for the BURST_ID and take into account the offset
to the first data channel. Some users might find it useful to be able to
switch between the two modes.
Signed-off-by: Stefan Popa <stefan.popa@analog.com>
Signed-off-by: Alexandru Ardelean <alexandru.ardelean@analog.com>
---
drivers/iio/imu/adis16480.c | 48 +++++++++++++++++++++++++++++++++++++
1 file changed, 48 insertions(+)
diff --git a/drivers/iio/imu/adis16480.c b/drivers/iio/imu/adis16480.c
index 9b100c8fb744..7d7712c33435 100644
--- a/drivers/iio/imu/adis16480.c
+++ b/drivers/iio/imu/adis16480.c
@@ -330,6 +330,45 @@ static int adis16480_debugfs_init(struct iio_dev *indio_dev)
#endif
+static ssize_t adis16495_burst_mode_enable_get(struct device *dev,
+ struct device_attribute *attr,
+ char *buf)
+{
+ struct adis16480 *st = iio_priv(dev_to_iio_dev(dev));
+
+ return sprintf(buf, "%d\n", st->adis.burst->en);
+}
+
+static ssize_t adis16495_burst_mode_enable_set(struct device *dev,
+ struct device_attribute *attr,
+ const char *buf, size_t len)
+{
+ struct adis16480 *st = iio_priv(dev_to_iio_dev(dev));
+ bool val;
+ int ret;
+
+ ret = kstrtobool(buf, &val);
+ if (ret)
+ return ret;
+
+ st->adis.burst->en = val;
+
+ return len;
+}
+
+static IIO_DEVICE_ATTR(burst_mode_enable, 0644,
+ adis16495_burst_mode_enable_get,
+ adis16495_burst_mode_enable_set, 0);
+
+static struct attribute *adis16495_attributes[] = {
+ &iio_dev_attr_burst_mode_enable.dev_attr.attr,
+ NULL,
+};
+
+static const struct attribute_group adis16495_attribute_group = {
+ .attrs = adis16495_attributes,
+};
+
static int adis16480_set_freq(struct iio_dev *indio_dev, int val, int val2)
{
struct adis16480 *st = iio_priv(indio_dev);
@@ -1131,6 +1170,14 @@ static const struct iio_info adis16480_info = {
.debugfs_reg_access = adis_debugfs_reg_access,
};
+static const struct iio_info adis16495_info = {
+ .attrs = &adis16495_attribute_group,
+ .read_raw = &adis16480_read_raw,
+ .write_raw = &adis16480_write_raw,
+ .update_scan_mode = adis_update_scan_mode,
+ .debugfs_reg_access = adis_debugfs_reg_access,
+};
+
static int adis16480_stop_device(struct iio_dev *indio_dev)
{
struct adis16480 *st = iio_priv(indio_dev);
@@ -1365,6 +1412,7 @@ static int adis16480_probe(struct spi_device *spi)
if (st->chip_info->burst) {
st->adis.burst = st->chip_info->burst;
st->adis.burst_extra_len = st->chip_info->burst->extra_len;
+ indio_dev->info = &adis16495_info;
}
ret = adis_setup_buffer_and_trigger(&st->adis, indio_dev,
--
2.17.1
next prev parent reply other threads:[~2020-08-04 10:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-04 10:04 [PATCH 1/2] iio: imu: adis16480: Add support for burst read function Alexandru Ardelean
2020-08-04 10:04 ` Alexandru Ardelean [this message]
2020-08-06 18:02 ` [PATCH 2/2] iio: imu: adis16480: Add the option to enable/disable burst mode Jonathan Cameron
2020-08-07 9:23 ` Andy Shevchenko
2020-08-05 7:33 ` [PATCH 1/2] iio: imu: adis16480: Add support for burst read function Andy Shevchenko
2020-08-06 17:59 ` 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=20200804100414.39002-2-alexandru.ardelean@analog.com \
--to=alexandru.ardelean@analog.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stefan.popa@analog.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).