linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Looijmans <mike.looijmans@topic.nl>
To: Lars-Peter Clausen <lars@metafoo.de>,
	Jonathan Cameron <jic23@kernel.org>
Cc: Hartmut Knaack <knaack.h@gmx.de>,
	Peter Meerwald <pmeerw@pmeerw.net>, <linux-iio@vger.kernel.org>
Subject: Re: [PATCH] iio: ad799x: Fix ad7991/ad7995/ad7999 config setup
Date: Wed, 26 Nov 2014 12:51:07 +0100	[thread overview]
Message-ID: <5475BEAB.3020700@topic.nl> (raw)
In-Reply-To: <1416998135-19931-1-git-send-email-lars@metafoo.de>

Tested it on the Miami board, and this patch indeed fixes the issue. You can 
add my tested-by if you like:

Tested-by: Mike Looijmans <mike.looijmans@topic.nl>


On 11/26/2014 11:35 AM, Lars-Peter Clausen wrote:
> The ad7991/ad7995/ad7999 does not have a configuration register like the
> other devices that can be written and read. The configuration is written as
> part of the conversion sequence.
>
> Fixes: 0f7ddcc1bff1 ("iio:adc:ad799x: Write default config on probe and reset alert status on probe")
> Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
> ---
>   drivers/iio/adc/ad799x.c | 15 +++++++++++++--
>   1 file changed, 13 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/iio/adc/ad799x.c b/drivers/iio/adc/ad799x.c
> index e37412d..b99de00 100644
> --- a/drivers/iio/adc/ad799x.c
> +++ b/drivers/iio/adc/ad799x.c
> @@ -143,9 +143,15 @@ static int ad799x_write_config(struct ad799x_state *st, u16 val)
>   	case ad7998:
>   		return i2c_smbus_write_word_swapped(st->client, AD7998_CONF_REG,
>   			val);
> -	default:
> +	case ad7992:
> +	case ad7993:
> +	case ad7994:
>   		return i2c_smbus_write_byte_data(st->client, AD7998_CONF_REG,
>   			val);
> +	default:
> +		/* Will be written when doing a conversion */
> +		st->config = val;
> +		return 0;
>   	}
>   }
>
> @@ -155,8 +161,13 @@ static int ad799x_read_config(struct ad799x_state *st)
>   	case ad7997:
>   	case ad7998:
>   		return i2c_smbus_read_word_swapped(st->client, AD7998_CONF_REG);
> -	default:
> +	case ad7992:
> +	case ad7993:
> +	case ad7994:
>   		return i2c_smbus_read_byte_data(st->client, AD7998_CONF_REG);
> +	default:
> +		/* No readback support */
> +		return st->config;
>   	}
>   }
>
>



Met vriendelijke groet / kind regards,

Mike Looijmans
System Expert


TOPIC Embedded Systems
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: (+31) (0) 499 33 69 79
Telefax:  (+31) (0) 499 33 69 70
E-mail: mike.looijmans@topic.nl
Website: www.topic.nl

Please consider the environment before printing this e-mail

Topic zoekt gedreven (embedded) software specialisten!
http://topic.nl/vacatures/topic-zoekt-software-engineers/


  reply	other threads:[~2014-11-26 11:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-26 10:35 [PATCH] iio: ad799x: Fix ad7991/ad7995/ad7999 config setup Lars-Peter Clausen
2014-11-26 11:51 ` Mike Looijmans [this message]
2014-12-12 12:34   ` 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=5475BEAB.3020700@topic.nl \
    --to=mike.looijmans@topic.nl \
    --cc=jic23@kernel.org \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=pmeerw@pmeerw.net \
    /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).