From: Mike Looijmans <mike.looijmans@topic.nl>
To: Jonathan Cameron <jic23@kernel.org>
Cc: devicetree@vger.kernel.org, linux-iio@vger.kernel.org,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Caleb Connolly <caleb.connolly@linaro.org>,
ChiYuan Huang <cy_huang@richtek.com>,
ChiaEn Wu <chiaen_wu@richtek.com>,
Cosmin Tanislav <demonsingur@gmail.com>,
Ibrahim Tilki <Ibrahim.Tilki@analog.com>,
Lars-Peter Clausen <lars@metafoo.de>,
Ramona Bolboaca <ramona.bolboaca@analog.com>,
William Breathitt Gray <william.gray@linaro.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/2] iio: adc: Add TI ADS1100 and ADS1000
Date: Mon, 6 Mar 2023 07:31:36 +0100 [thread overview]
Message-ID: <ceb4f367-b910-578a-24bc-7c222e2f0b0f@topic.nl> (raw)
In-Reply-To: <20230304175751.2daae308@jic23-huawei>
Met vriendelijke groet / kind regards,
Mike Looijmans
System Expert
TOPIC Embedded Products B.V.
Materiaalweg 4, 5681 RJ Best
The Netherlands
T: +31 (0) 499 33 69 69
E: mike.looijmans@topicproducts.com
W: www.topic.nl
Please consider the environment before printing this e-mail
On 04-03-2023 18:57, Jonathan Cameron wrote:
> On Tue, 28 Feb 2023 07:31:51 +0100
> Mike Looijmans <mike.looijmans@topic.nl> wrote:
>
>> The ADS1100 is a 16-bit ADC (at 8 samples per second).
>> The ADS1000 is similar, but has a fixed data rate.
>>
>> Signed-off-by: Mike Looijmans <mike.looijmans@topic.nl>
> Hi Mike,
>
> A few minor things + one request for a test as trying to chase a possible
> ref count overflow around the runtime_pm was giving me a enough of a headache
> that it's easier to ask you just to poke it and see. If it doesn't fail as
> I expect I'll take a closer look!
Will do, but it may take a few days to get access to the hardware again.
I'll report on that later.
>> +static int ads1100_set_scale(struct ads1100_data *data, int val, int val2)
>> +{
>> + int microvolts;
>> + int gain;
>> + int i;
>> +
>> + /* With Vdd between 2.7 and 5V, the scale is always below 1 */
>> + if (val)
>> + return -EINVAL;
>> +
>> + microvolts = regulator_get_voltage(data->reg_vdd);
>> + /* Calculate: gain = ((microvolts / 1000) / (val2 / 1000000)) >> 15 */
>> + gain = ((microvolts + BIT(14)) >> 15) * 1000 / val2;
>> +
>> + for (i = 0; i < 4; i++) {
>> + if (BIT(i) == gain) {
>> + ads1100_set_config_bits(data, ADS1100_PGA_MASK, i);
>> + return 0;
>> + }
>> + }
> Andy's suggestion of something like..
> if (!gain)
> return -EINVAL;
> i = ffs(gain);
> if (i >= 4 || BIT(i) != gain)
> return -EINVAL;
>
> ads...
>
> Is perhaps nicer than the loop.
Yes, takes out a loop.
>
>> +static void ads1100_disable_continuous(void *data)
>> +{
>> + ads1100_set_config_bits(data, ADS1100_CFG_SC, ADS1100_SINGLESHOT);
>> +}
>> +
>> +static int ads1100_probe(struct i2c_client *client)
>> +{
>> + struct iio_dev *indio_dev;
>> + struct ads1100_data *data;
>> + struct device *dev = &client->dev;
>> + int ret;
>> +
>> + indio_dev = devm_iio_device_alloc(dev, sizeof(*data));
>> + if (!indio_dev)
>> + return -ENOMEM;
>> +
>> + data = iio_priv(indio_dev);
>> + i2c_set_clientdata(client, indio_dev);
> You can avoid the slightly nasty mix of i2c_set_clientdata vs dev_get_drvdata()
> below by taking advantage of the fact you have a local dev pointer.
>
> dev_set_drvdata(dev, indio_dev);
> and no confusing mix is left. Of course it's doing the same thing but to my
> mind slightly nicer to use the same one.
Since I don't need indio_dev anywhere, I might as well say this directly:
dev_set_drvdata(dev, data);
(Only the pm_ routines use this)
> ...
>
--
Mike Looijmans
next prev parent reply other threads:[~2023-03-06 6:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-28 6:31 [PATCH v3 1/2] dt-bindings: iio: adc: Add TI ADS1100 and ADS1000 Mike Looijmans
2023-02-28 6:31 ` [PATCH v3 2/2] " Mike Looijmans
2023-03-01 15:30 ` Andy Shevchenko
2023-03-02 7:49 ` Mike Looijmans
2023-03-02 13:16 ` Lars-Peter Clausen
2023-03-02 13:20 ` Lars-Peter Clausen
2023-03-02 14:24 ` Andy Shevchenko
2023-03-04 17:19 ` Jonathan Cameron
2023-03-02 14:23 ` Andy Shevchenko
2023-03-04 17:26 ` Jonathan Cameron
2023-03-06 12:09 ` Andy Shevchenko
2023-03-04 17:57 ` Jonathan Cameron
2023-03-06 6:31 ` Mike Looijmans [this message]
2023-03-06 11:21 ` Mike Looijmans
2023-03-12 14:53 ` Jonathan Cameron
2023-03-06 12:11 ` Andy Shevchenko
2023-03-06 12:16 ` Andy Shevchenko
2023-03-06 12:20 ` Andy Shevchenko
2023-03-06 12:56 ` Mike Looijmans
2023-03-06 13:19 ` Andy Shevchenko
2023-02-28 10:34 ` [PATCH v3 1/2] dt-bindings: " Krzysztof Kozlowski
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=ceb4f367-b910-578a-24bc-7c222e2f0b0f@topic.nl \
--to=mike.looijmans@topic.nl \
--cc=Ibrahim.Tilki@analog.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=caleb.connolly@linaro.org \
--cc=chiaen_wu@richtek.com \
--cc=cy_huang@richtek.com \
--cc=demonsingur@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ramona.bolboaca@analog.com \
--cc=william.gray@linaro.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