From: Jonathan Cameron <jic23@kernel.org>
To: David Lechner <david@lechnology.com>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
linux-iio@vger.kernel.org
Subject: Re: [PATCH v2 1/2] iio: adc: ti-ads7950: Allow to use on ACPI platforms
Date: Sun, 30 Jul 2017 14:31:58 +0100 [thread overview]
Message-ID: <20170730143158.3b907e8f@kernel.org> (raw)
In-Reply-To: <9d74cad7-be8e-9893-58bd-9fdd50298723@lechnology.com>
On Sat, 29 Jul 2017 20:27:13 -0500
David Lechner <david@lechnology.com> wrote:
> On 07/28/2017 05:20 PM, Andy Shevchenko wrote:
> > ACPI enabled platforms do not have a mean of regulators. Instead we use
> > hard coded voltage value for reference pin. When value is 0 (default) we
> > fall back to request a regulator.
> >
> > Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> > ---
> > drivers/iio/adc/ti-ads7950.c | 24 ++++++++++++++++++++----
> > 1 file changed, 20 insertions(+), 4 deletions(-)
> >
> > diff --git a/drivers/iio/adc/ti-ads7950.c b/drivers/iio/adc/ti-ads7950.c
> > index 16a06633332c..ab669af291b7 100644
> > --- a/drivers/iio/adc/ti-ads7950.c
> > +++ b/drivers/iio/adc/ti-ads7950.c
> > @@ -21,6 +21,7 @@
> > * GNU General Public License for more details.
> > */
> >
> > +#include <linux/acpi.h>
> > #include <linux/bitops.h>
> > #include <linux/device.h>
> > #include <linux/err.h>
> > @@ -37,6 +38,12 @@
> > #include <linux/iio/trigger_consumer.h>
> > #include <linux/iio/triggered_buffer.h>
> >
> > +/*
> > + * In case of ACPI, we use the 5000 mV as default for the reference pin.
> > + * Device tree users encode that via the vref-supply regulator.
> > + */
> > +#define TI_ADS7950_VA_MV_ACPI_DEFAULT 5000
>
> Now that I've thought about it a bit, you don't need to call this the
> ACPI default, just call it the default. Then it will be obvious that
> this is used when you don't have a regulator.
>
> > +
> > #define TI_ADS7950_CR_MANUAL BIT(12)
> > #define TI_ADS7950_CR_WRITE BIT(11)
> > #define TI_ADS7950_CR_CHAN(ch) ((ch) << 7)
> > @@ -58,6 +65,7 @@ struct ti_ads7950_state {
> > struct spi_message scan_single_msg;
> >
> > struct regulator *reg;
> > + unsigned int vref_mv;
> >
> > unsigned int settings;
> >
> > @@ -305,11 +313,15 @@ static int ti_ads7950_get_range(struct ti_ads7950_state *st)
> > {
> > int vref;
> >
> > - vref = regulator_get_voltage(st->reg);
> > - if (vref < 0)
> > - return vref;
> > + if (st->vref_mv) {
> > + vref = st->vref_mv;
> > + } else {
> > + vref = regulator_get_voltage(st->reg);
> > + if (vref < 0)
> > + return vref;
> >
> > - vref /= 1000;
> > + vref /= 1000;
> > + }
> >
> > if (st->settings & TI_ADS7950_CR_RANGE_5V)
> > vref *= 2;
> > @@ -411,6 +423,10 @@ static int ti_ads7950_probe(struct spi_device *spi)
> > spi_message_init_with_transfers(&st->scan_single_msg,
> > st->scan_single_xfer, 3);
> >
> > + /* Use hard coded value for reference voltage in ACPI case */
> > + if (ACPI_COMPANION(&spi->dev))
> > + st->vref_mv = TI_ADS7950_VA_MV_ACPI_DEFAULT;
>
> Instead of checking or ACPI, you could just say "if we have a dummy
> regulator, then use the default value".
>
Agreed. Sounds sensible to me. Hopefully in DT people will
provide the right regulator, but chances are this won't
always happen.
Jonathan
> > +
> > st->reg = devm_regulator_get(&spi->dev, "vref");
> > if (IS_ERR(st->reg)) {
> > dev_err(&spi->dev, "Failed get get regulator \"vref\"\n");
> >
>
next prev parent reply other threads:[~2017-07-30 13:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-28 22:20 [PATCH v2 0/2] iio: ti-ads7950: Make it working on ACPI platforms Andy Shevchenko
2017-07-28 22:20 ` [PATCH v2 1/2] iio: adc: ti-ads7950: Allow to use " Andy Shevchenko
2017-07-30 1:27 ` David Lechner
2017-07-30 13:31 ` Jonathan Cameron [this message]
2017-08-01 15:45 ` Andy Shevchenko
2017-08-01 16:21 ` David Lechner
2017-08-01 16:41 ` Andy Shevchenko
2017-08-01 17:09 ` David Lechner
2017-08-01 17:44 ` Andy Shevchenko
2017-08-01 17:15 ` David Lechner
2017-08-01 17:24 ` Andy Shevchenko
2017-08-09 13:24 ` Jonathan Cameron
2017-08-13 14:25 ` Andy Shevchenko
2017-08-20 10:48 ` Jonathan Cameron
2017-07-28 22:20 ` [PATCH v2 2/2] iio: adc: ti-ads7950: Add OF device ID table Andy Shevchenko
2017-08-01 15:48 ` Andy Shevchenko
2017-08-09 13: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=20170730143158.3b907e8f@kernel.org \
--to=jic23@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=david@lechnology.com \
--cc=knaack.h@gmx.de \
--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).