From: Jonathan Cameron <jic23@cam.ac.uk>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: Michael Hennerich <michael.hennerich@analog.com>,
linux-iio@vger.kernel.org,
device-drivers-devel@blackfin.uclinux.org
Subject: Re: [PATCH] staging:iio: AD5638: Fix channel address
Date: Thu, 06 Oct 2011 14:41:10 +0100 [thread overview]
Message-ID: <4E8DAFF6.2030602@cam.ac.uk> (raw)
In-Reply-To: <1317907147-15677-1-git-send-email-lars@metafoo.de>
On 10/06/11 14:19, Lars-Peter Clausen wrote:
> Commit c6fc806247 ("staging:iio: ABI rework - add in_ or out_ prefix to
> channnels") added the AD5868_CHANNEL macro to simplify channel initialization.
> Unfortunately the macro hardcodes the channel's address to AD5686_ADDR_DAC0. As
> a result writing to any of the channels will change the value of the first
> channel.
>
> This patch fixes the issue by calculating the channel address based on the
> channel number.
>
oops, not one of my better moments. It always seems to be the simple
cleanups that have this dumb ass bugs in them.
Less churn to use
AD5656_ADDR_DAC##chan, but yours is cleaner in the end.
Thanks!
Please send on to Greg (no need to go through my tree now Greg's
is publicly visible again).
> Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
Acked-by: Jonathan Cameron <jic23@cam.ac.uk>
> ---
> drivers/staging/iio/dac/ad5686.c | 7 ++-----
> 1 files changed, 2 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/staging/iio/dac/ad5686.c b/drivers/staging/iio/dac/ad5686.c
> index b55ef42..adf898f 100644
> --- a/drivers/staging/iio/dac/ad5686.c
> +++ b/drivers/staging/iio/dac/ad5686.c
> @@ -26,10 +26,7 @@
> #define AD5686_ADDR(x) ((x) << 16)
> #define AD5686_CMD(x) ((x) << 20)
>
> -#define AD5686_ADDR_DAC0 0x1
> -#define AD5686_ADDR_DAC1 0x2
> -#define AD5686_ADDR_DAC2 0x4
> -#define AD5686_ADDR_DAC3 0x8
> +#define AD5686_ADDR_DAC(chan) (0x1 << (chan))
> #define AD5686_ADDR_ALL_DAC 0xF
>
> #define AD5686_CMD_NOOP 0x0
> @@ -103,7 +100,7 @@ enum ad5686_supported_device_ids {
> .output = 1, \
> .channel = chan, \
> .info_mask = (1 << IIO_CHAN_INFO_SCALE_SHARED), \
> - .address = AD5686_ADDR_DAC0, \
> + .address = AD5686_ADDR_DAC(chan), \
> .scan_type = IIO_ST('u', bits, 16, shift) \
> }
> static const struct ad5686_chip_info ad5686_chip_info_tbl[] = {
prev parent reply other threads:[~2011-10-06 13:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-06 13:19 [PATCH] staging:iio: AD5638: Fix channel address Lars-Peter Clausen
2011-10-06 13:41 ` 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=4E8DAFF6.2030602@cam.ac.uk \
--to=jic23@cam.ac.uk \
--cc=device-drivers-devel@blackfin.uclinux.org \
--cc=lars@metafoo.de \
--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.