From: Michael Hennerich <michael.hennerich@analog.com>
To: Axel Lin <axel.lin@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Michael Hennerich <hennerich@blackfin.uclinux.org>,
Samuel Ortiz <sameo@linux.intel.com>,
"device-drivers-devel@blackfin.uclinux.org"
<device-drivers-devel@blackfin.uclinux.org>
Subject: Re: [PATCH] mfd: adp5520: Ensure setting bits if new value is different from the old value
Date: Mon, 31 Oct 2011 10:43:59 +0100 [thread overview]
Message-ID: <4EAE6DDF.6010608@analog.com> (raw)
In-Reply-To: <1320030006.2690.8.camel@phoenix>
On 10/31/2011 04:00 AM, Axel Lin wrote:
> Current code checks if all the bit_mask bits are all zero is wrong.
> We need to write new value if the bit mask fields of new value is
> not equal to old value.
>
> Signed-off-by: Axel Lin<axel.lin@gmail.com>
Acked-by: Michael Hennerich <michael.hennerich@analog.com>
Right - the da903x suffers the same problem.
> ---
> drivers/mfd/adp5520.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/mfd/adp5520.c b/drivers/mfd/adp5520.c
> index f1d8848..8d816cc 100644
> --- a/drivers/mfd/adp5520.c
> +++ b/drivers/mfd/adp5520.c
> @@ -109,7 +109,7 @@ int adp5520_set_bits(struct device *dev, int reg, uint8_t bit_mask)
>
> ret = __adp5520_read(chip->client, reg,®_val);
>
> - if (!ret&& ((reg_val& bit_mask) == 0)) {
> + if (!ret&& ((reg_val& bit_mask) != bit_mask)) {
> reg_val |= bit_mask;
> ret = __adp5520_write(chip->client, reg, reg_val);
> }
--
Greetings,
Michael
--
Analog Devices GmbH Wilhelm-Wagenfeld-Str. 6 80807 Muenchen
Sitz der Gesellschaft: Muenchen; Registergericht: Muenchen HRB 40368;
Geschaeftsfuehrer:Dr.Carsten Suckrow, Thomas Wessel, William A. Martin,
Margaret Seif
next prev parent reply other threads:[~2011-10-31 9:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-31 3:00 [PATCH] mfd: adp5520: Ensure setting bits if new value is different from the old value Axel Lin
2011-10-31 9:43 ` Michael Hennerich [this message]
2011-11-14 0:02 ` Samuel Ortiz
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=4EAE6DDF.6010608@analog.com \
--to=michael.hennerich@analog.com \
--cc=axel.lin@gmail.com \
--cc=device-drivers-devel@blackfin.uclinux.org \
--cc=hennerich@blackfin.uclinux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sameo@linux.intel.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.