From: Drew Fustini <drew@pdp7.com>
To: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Cc: "Sa, Nuno" <Nuno.Sa@analog.com>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
linux-iio <linux-iio@vger.kernel.org>,
Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>
Subject: Re: [PATCH v2 1/1] iio: ltc2983: fix device probe
Date: Thu, 12 Aug 2021 11:31:35 -0700 [thread overview]
Message-ID: <20210812183135.GA3120809@x1> (raw)
In-Reply-To: <20210812191919.00000217@Huawei.com>
On Thu, Aug 12, 2021 at 07:19:19PM +0100, Jonathan Cameron wrote:
> On Thu, 12 Aug 2021 06:54:13 +0000
> "Sa, Nuno" <Nuno.Sa@analog.com> wrote:
>
> > > -----Original Message-----
> > > From: Andy Shevchenko <andy.shevchenko@gmail.com>
> > > Sent: Wednesday, August 11, 2021 6:15 PM
> > > To: Sa, Nuno <Nuno.Sa@analog.com>
> > > Cc: linux-iio <linux-iio@vger.kernel.org>; Jonathan Cameron
> > > <jic23@kernel.org>; Lars-Peter Clausen <lars@metafoo.de>; Drew
> > > Fustini <drew@pdp7.com>
> > > Subject: Re: [PATCH v2 1/1] iio: ltc2983: fix device probe
> > >
> > > [External]
> > >
> > > On Wed, Aug 11, 2021 at 4:32 PM Nuno Sá <nuno.sa@analog.com>
> > > wrote:
> > >
> > > Thanks for an update, my comments below.
> > > Depending on Jonathan's wishes it may or may not require a v3.
> > > If you address the minor issues I commented on, take mine
> > > Reviewed-by: Andy Shevchenko <andy.shevchenko@gmail.com>
> > >
> >
> > Thanks for reviewing... Yeah, I will wait for Jonathan's feedback before
> > sending a v3. It might be that he can apply your inputs when applying
> > the patch.
>
> Patch looks sensible. I can make the tweaks whilst applying when I
> happen to be on the right computer.
>
> Having glanced at the datasheet, I wonder if you ever had the
> reset pin wired up (and perhaps decided to drop that
> complexity later)? The driver rather oddly
> include of_gpio.h and has no gpio accesses which makes me
> wonder ;)
I'm sure Nuno will have something to say but I wanted to mention that I
was initially thinking about this. The reset pin is connected to a GPIO
on the Zynq-7000 on the custom board I am using. I added that gpio line
as an active low gpio hog under the gpio controller node in the DTS and
that worked ok. Though I had wondered whether there would ever be a
case in which the driver would want to reset the LTC2983.
Thanks,
Drew
next prev parent reply other threads:[~2021-08-12 18:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-11 13:32 [PATCH v2 0/1] Fix ltc2983 probing Nuno Sá
2021-08-11 13:32 ` [PATCH v2 1/1] iio: ltc2983: fix device probe Nuno Sá
2021-08-11 16:15 ` Andy Shevchenko
2021-08-12 6:54 ` Sa, Nuno
2021-08-12 18:19 ` Jonathan Cameron
2021-08-12 18:31 ` Drew Fustini [this message]
2021-08-13 7:21 ` Sa, Nuno
2021-08-15 15:33 ` Jonathan Cameron
2021-08-12 1:09 ` Drew Fustini
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=20210812183135.GA3120809@x1 \
--to=drew@pdp7.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=Nuno.Sa@analog.com \
--cc=andy.shevchenko@gmail.com \
--cc=jic23@kernel.org \
--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.