linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Nishad Kamdar <nishadkamdar@gmail.com>
Cc: Shreeya Patel <shreeya.patel23498@gmail.com>,
	Slawomir Stepien <sst@poczta.fm>,
	Michael Hennerich <Michael.Hennerich@analog.com>,
	Hartmut Knaack <knaack.h@gmx.de>,
	Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-iio@vger.kernel.org, devel@driverdev.osuosl.org,
	"linux-kernel@vger.kernel.org Lars-Peter Clausen"
	<lars@metafoo.de>
Subject: Re: [PATCH] staging: iio: adt7316: Switch to the gpio descriptor interface
Date: Sun, 28 Oct 2018 14:58:38 +0000	[thread overview]
Message-ID: <20181028145838.329b2768@archlinux> (raw)
In-Reply-To: <20181024163352.GA18959@nishad>

On Wed, 24 Oct 2018 22:03:54 +0530
Nishad Kamdar <nishadkamdar@gmail.com> wrote:

> On Mon, Oct 22, 2018 at 11:22:15PM +0530, Shreeya Patel wrote:
> > On Mon, 2018-10-22 at 22:44 +0530, Nishad Kamdar wrote:  
> > > Use the gpiod interface instead of the deprecated old non-descriptor
> > > interface for ldac_pin.
> > > 
> > > Signed-off-by: Nishad Kamdar <nishadkamdar@gmail.com>
> > > ---  
> > 
> > Hi Nishad,
> > 
> > I have been working on implementing device tree bindings for this
> > driver and removing platform data from it.
> > 
> > I've sent a series of patches for it to Jonathan. I didn't send it 
> > on the mailing list as I wanted to confirm from Jonathan if we wants
> > something more to be done in the series. That series also includes
> > the change which you are proposing here.
> > I am really sorry that you didn't know about this.
> > If you are planning to send any other patches for this driver then
> > let me know before you start implementing it so that we can
> > co-ordinate before doing any work.
> > 
> > Thanks
> > 
> >   
> > >  drivers/staging/iio/addac/adt7316.c | 17 ++++++++++++-----
> > >  1 file changed, 12 insertions(+), 5 deletions(-)
> > > 
> > > diff --git a/drivers/staging/iio/addac/adt7316.c
> > > b/drivers/staging/iio/addac/adt7316.c
> > > index 3f22d1088713..94f945ba0097 100644
> > > --- a/drivers/staging/iio/addac/adt7316.c
> > > +++ b/drivers/staging/iio/addac/adt7316.c
> > > @@ -8,7 +8,7 @@
> > >   */
> > >  
> > >  #include <linux/interrupt.h>
> > > -#include <linux/gpio.h>
> > > +#include <linux/gpio/consumer.h>
> > >  #include <linux/workqueue.h>
> > >  #include <linux/device.h>
> > >  #include <linux/kernel.h>
> > > @@ -177,7 +177,7 @@
> > >  
> > >  struct adt7316_chip_info {
> > >  	struct adt7316_bus	bus;
> > > -	u16			ldac_pin;
> > > +	struct gpio_desc	*ldac_pin;
> > >  	u16			int_mask;	/* 0x2f */
> > >  	u8			config1;
> > >  	u8			config2;
> > > @@ -950,8 +950,8 @@ static ssize_t adt7316_store_update_DAC(struct
> > > device *dev,
> > >  		if (ret)
> > >  			return -EIO;
> > >  	} else {
> > > -		gpio_set_value(chip->ldac_pin, 0);
> > > -		gpio_set_value(chip->ldac_pin, 1);
> > > +		gpiod_set_value(chip->ldac_pin, 0);
> > > +		gpiod_set_value(chip->ldac_pin, 1);
> > >  	}
> > >  
> > >  	return len;
> > > @@ -2120,7 +2120,14 @@ int adt7316_probe(struct device *dev, struct
> > > adt7316_bus *bus,
> > >  	else
> > >  		return -ENODEV;
> > >  
> > > -	chip->ldac_pin = adt7316_platform_data[1];
> > > +	chip->ldac_pin = devm_gpiod_get(dev, "ldac",
> > > GPIOD_OUT_HIGH);
> > > +	if (IS_ERR(chip->ldac_pin)) {
> > > +		ret = PTR_ERR(chip->ldac_pin);
> > > +		dev_err(dev, "Failed to request ldac GPIO: %d\n",
> > > +			ret);
> > > +		return ret;
> > > +	}
> > > +
> > >  	if (chip->ldac_pin) {
> > >  		chip->config3 |= ADT7316_DA_EN_VIA_DAC_LDCA;
> > >  		if ((chip->id & ID_FAMILY_MASK) == ID_ADT75XX)  
> Hello Shreeya,
> 
> Sure no problem.
> 
> Thanks and regards,
> Nishad

Hi Nishad,

Thanks for being so understanding on this.  I would normally operate
a policy of first to post on the list (assuming they update reasonably
quickly) is the on I apply, but as you are fine with it and this will
save Shreeya a little time (by avoiding a rebase) I'll wait for Shreeya's
public version.

I once discovered I was one of 3 people working on new drivers for a
single camera sensor years ago.  All 3 got posted in the same week
despite the part having been around for years before that.  Sometimes
we get unlucky - the nature of opensource ;)

Jonathan

  reply	other threads:[~2018-10-28 23:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-22 17:14 [PATCH] staging: iio: adt7316: Switch to the gpio descriptor interface Nishad Kamdar
2018-10-22 17:52 ` Shreeya Patel
2018-10-24 16:33   ` Nishad Kamdar
2018-10-28 14:58     ` Jonathan Cameron [this message]
2018-10-23  5:39 ` Dan Carpenter

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=20181028145838.329b2768@archlinux \
    --to=jic23@kernel.org \
    --cc=Michael.Hennerich@analog.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=nishadkamdar@gmail.com \
    --cc=pmeerw@pmeerw.net \
    --cc=shreeya.patel23498@gmail.com \
    --cc=sst@poczta.fm \
    /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).