From: Jonathan Cameron <jic23@kernel.org>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: Jonathan Cameron <jic23@cam.ac.uk>, linux-iio@vger.kernel.org
Subject: Re: [PATCH 2/4] staging:iio:adt7316: Don't expose the chip reset to userspace
Date: Tue, 16 Jul 2013 17:57:14 +0100 [thread overview]
Message-ID: <51E57B6A.5090608@kernel.org> (raw)
In-Reply-To: <1373987283-32657-2-git-send-email-lars@metafoo.de>
On 07/16/2013 04:08 PM, Lars-Peter Clausen wrote:
> There is no reason why userspace should want to trigger a manual reset of the
> device, so remove this functionality.
>
> Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
Applied to the togreg branch of iio.git
Thanks
> ---
> drivers/staging/iio/addac/adt7316.c | 27 ---------------------------
> 1 file changed, 27 deletions(-)
>
> diff --git a/drivers/staging/iio/addac/adt7316.c b/drivers/staging/iio/addac/adt7316.c
> index 506b5a7..1e13568 100644
> --- a/drivers/staging/iio/addac/adt7316.c
> +++ b/drivers/staging/iio/addac/adt7316.c
> @@ -551,31 +551,6 @@ static IIO_DEVICE_ATTR(enable_smbus_timeout, S_IRUGO | S_IWUSR,
> adt7316_store_enable_smbus_timeout,
> 0);
>
> -
> -static ssize_t adt7316_store_reset(struct device *dev,
> - struct device_attribute *attr,
> - const char *buf,
> - size_t len)
> -{
> - struct iio_dev *dev_info = dev_to_iio_dev(dev);
> - struct adt7316_chip_info *chip = iio_priv(dev_info);
> - u8 config2;
> - int ret;
> -
> - config2 = chip->config2 | ADT7316_RESET;
> -
> - ret = chip->bus.write(chip->bus.client, ADT7316_CONFIG2, config2);
> - if (ret)
> - return -EIO;
> -
> - return len;
> -}
> -
> -static IIO_DEVICE_ATTR(reset, S_IWUSR,
> - NULL,
> - adt7316_store_reset,
> - 0);
> -
> static ssize_t adt7316_show_powerdown(struct device *dev,
> struct device_attribute *attr,
> char *buf)
> @@ -1675,7 +1650,6 @@ static IIO_DEVICE_ATTR(bus_type, S_IRUGO, adt7316_show_bus_type, NULL, 0);
> static struct attribute *adt7316_attributes[] = {
> &iio_dev_attr_all_modes.dev_attr.attr,
> &iio_dev_attr_mode.dev_attr.attr,
> - &iio_dev_attr_reset.dev_attr.attr,
> &iio_dev_attr_enabled.dev_attr.attr,
> &iio_dev_attr_ad_channel.dev_attr.attr,
> &iio_dev_attr_all_ad_channels.dev_attr.attr,
> @@ -1719,7 +1693,6 @@ static struct attribute *adt7516_attributes[] = {
> &iio_dev_attr_all_modes.dev_attr.attr,
> &iio_dev_attr_mode.dev_attr.attr,
> &iio_dev_attr_select_ex_temp.dev_attr.attr,
> - &iio_dev_attr_reset.dev_attr.attr,
> &iio_dev_attr_enabled.dev_attr.attr,
> &iio_dev_attr_ad_channel.dev_attr.attr,
> &iio_dev_attr_all_ad_channels.dev_attr.attr,
>
next prev parent reply other threads:[~2013-07-16 16:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-16 15:08 [PATCH 1/4] staging:iio:ad2s1210: Don't expose the chip reset to userspace Lars-Peter Clausen
2013-07-16 15:08 ` [PATCH 2/4] staging:iio:adt7316: " Lars-Peter Clausen
2013-07-16 16:57 ` Jonathan Cameron [this message]
2013-07-16 15:08 ` [PATCH 3/4] staging:iio:ade7xxx: " Lars-Peter Clausen
2013-07-16 16:57 ` Jonathan Cameron
2013-07-16 15:08 ` [PATCH 4/4] iio: Remove IIO_DEV_ATTR_RESET macro Lars-Peter Clausen
2013-07-16 16:57 ` Jonathan Cameron
2013-07-16 16:56 ` [PATCH 1/4] staging:iio:ad2s1210: Don't expose the chip reset to userspace 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=51E57B6A.5090608@kernel.org \
--to=jic23@kernel.org \
--cc=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 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).