Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Marcelo Schmitt <marcelo.schmitt1@gmail.com>
Cc: nuno.sa@analog.com, lars@metafoo.de,
	Michael.Hennerich@analog.com, lgirdwood@gmail.com,
	broonie@kernel.org, Chandrakant.Minajigi@analog.com,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] iio: dac: ad3552r: Correct device IDs
Date: Sat, 5 Aug 2023 19:01:31 +0100	[thread overview]
Message-ID: <20230805190131.0cab0b3d@jic23-huawei> (raw)
In-Reply-To: <011f480220799fbfabdd53896f8a2f251ad995ad.1691091324.git.marcelo.schmitt1@gmail.com>

On Thu, 3 Aug 2023 16:56:23 -0300
Marcelo Schmitt <marcelo.schmitt1@gmail.com> wrote:

> Device IDs for AD3542R and AD3552R were swapped leading to unintended
> collection of DAC output ranges being used for each design.
> Change device ID values so they are correct for each DAC chip.
> 
> Fixes: 8f2b54824b28 ("drivers:iio:dac: Add AD3552R driver support")
> Signed-off-by: Marcelo Schmitt <marcelo.schmitt1@gmail.com>
> Reported-by: Chandrakant Minajigi <Chandrakant.Minajigi@analog.com>
Applied to the fixes-togreg branch of iio.git and marked for stable.

Thanks,

Jonathan

> ---
> A user has reported that the IDs were wrong and the output ranges were not ok.
> Also, the dt-doc and the driver require the adi,output-range-microvolt property
> for ad3542r but not for ad3552r, which could cause actual ad3552r probing to
> fail if the device node did not have that property.
> It's not clear from datasheet if setting the output range is really required for
> ad3542r.
> 
> Was once better at sending patches. Hope I get used to it again :)
> 
> Thanks
> 
>  drivers/iio/dac/ad3552r.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/iio/dac/ad3552r.c b/drivers/iio/dac/ad3552r.c
> index d5ea1a1be122..a492e8f2fc0f 100644
> --- a/drivers/iio/dac/ad3552r.c
> +++ b/drivers/iio/dac/ad3552r.c
> @@ -140,8 +140,8 @@ enum ad3552r_ch_vref_select {
>  };
>  
>  enum ad3542r_id {
> -	AD3542R_ID = 0x4008,
> -	AD3552R_ID = 0x4009,
> +	AD3542R_ID = 0x4009,
> +	AD3552R_ID = 0x4008,
>  };
>  
>  enum ad3552r_ch_output_range {


      reply	other threads:[~2023-08-05 18:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-03 19:56 [PATCH v2] iio: dac: ad3552r: Correct device IDs Marcelo Schmitt
2023-08-05 18:01 ` Jonathan Cameron [this message]

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=20230805190131.0cab0b3d@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=Chandrakant.Minajigi@analog.com \
    --cc=Michael.Hennerich@analog.com \
    --cc=broonie@kernel.org \
    --cc=lars@metafoo.de \
    --cc=lgirdwood@gmail.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.schmitt1@gmail.com \
    --cc=nuno.sa@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox