From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
To: <alexandru.ardelean@analog.com>
Cc: <linux-iio@vger.kernel.org>, <michael.hennerich@analog.com>
Subject: Re: [PATCH][RESEND] staging: iio: adc: ad7192: disable burnout currents on misconfig
Date: Tue, 16 Jan 2018 10:46:47 +0000 [thread overview]
Message-ID: <20180116104647.0000656e@huawei.com> (raw)
In-Reply-To: <20180116100437.10220-1-alexandru.ardelean@analog.com>
On Tue, 16 Jan 2018 12:04:37 +0200
<alexandru.ardelean@analog.com> wrote:
> From: Alexandru Ardelean <alexandru.ardelean@analog.com>
>
Firstly, even a change to a description makes this a V2 patch
not a resend. Resends should be identical and only occur if
either:
1) Someone asks you to resend for some reason (wrong cc's perhaps)
2) It has been a long time since anyone responded and looks like
your series has been forgotten.
> According to the datasheet for all ad719x ADCs,
> the burnout currents can be enabled only if buffer is enabled
> and CHOP is disabled.
>
> So, if neither of these conditions are met, then
> we should disable the burnout currents in the driver as well,
> and warn the user.
>
> This change doesn't fix anything.
> The burnout currents simply won't work if CHOP is enabled
> or buffer is disabled.
> The intent is to provide the user with some feedback
> instead of silently not working inside the chip.
>
> This is especially useful when considering device-tree
> support (and/or device-tree overlays) at a later point,
> which will allow for a quicker/simpler reconfiguration
> of the chip settings.
>
> Signed-off-by: Alexandru Ardelean <alexandru.ardelean@analog.com>
Thanks, much better description. I'll pick this up when I'm next
on the correct PC (possibly not until the weekend).
Jonathan
> ---
> drivers/staging/iio/adc/ad7192.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/drivers/staging/iio/adc/ad7192.c b/drivers/staging/iio/adc/ad7192.c
> index d11c6de9c777..7f204013d6d4 100644
> --- a/drivers/staging/iio/adc/ad7192.c
> +++ b/drivers/staging/iio/adc/ad7192.c
> @@ -266,6 +266,12 @@ static int ad7192_setup(struct ad7192_state *st,
>
> st->conf = AD7192_CONF_GAIN(0);
>
> + if (pdata->burnout_curr_en && (!pdata->buf_en || pdata->chop_en)) {
> + pdata->burnout_curr_en = false;
> + dev_warn(dev,
> + "Can't enable burnout currents: see CHOP or buffer\n");
> + }
> +
> if (pdata->rej60_en)
> st->mode |= AD7192_MODE_REJ60;
>
next prev parent reply other threads:[~2018-01-16 10:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-16 10:04 [PATCH][RESEND] staging: iio: adc: ad7192: disable burnout currents on misconfig alexandru.ardelean
2018-01-16 10:46 ` Jonathan Cameron [this message]
2018-01-16 11:09 ` Ardelean, Alexandru
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=20180116104647.0000656e@huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=alexandru.ardelean@analog.com \
--cc=linux-iio@vger.kernel.org \
--cc=michael.hennerich@analog.com \
/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.