From: Joe Perches <joe@perches.com>
To: Chanwoo Choi <cw00.choi@samsung.com>
Cc: Dan Carpenter <dan.carpenter@oracle.com>,
Krzysztof Kozlowski <k.kozlowski@samsung.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [patch] regulator: max77686: fix a shift wrapping bug
Date: Fri, 15 May 2015 10:10:26 -0700 [thread overview]
Message-ID: <1431709826.15709.15.camel@perches.com> (raw)
In-Reply-To: <5555C814.7030405@samsung.com>
On Fri, 2015-05-15 at 19:19 +0900, Chanwoo Choi wrote:
> On 05/15/2015 06:25 PM, Dan Carpenter wrote:
> > We need to be able to handle more than 32 bits here because "id" can go
> > up to MAX77686_BUCK9 (34). ->gpio_enabled is a u64 so that's fine
> > already.
> >
> > Fixes: 3307e9025d29 ('regulator: max77686: Add GPIO control')
> > Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Alternate suggested patch below:
> > diff --git a/drivers/regulator/max77686.c b/drivers/regulator/max77686.c
[]
> > @@ -121,7 +121,7 @@ static unsigned int max77686_map_normal_mode(struct max77686_data *max77686,
> > - if (max77686->gpio_enabled & (1 << id))
> > + if (max77686->gpio_enabled & (1ULL << id))
[]
> > @@ -277,7 +277,7 @@ static int max77686_of_parse_cb(struct device_node *np,
> > if (gpio_is_valid(config->ena_gpio)) {
> > - max77686->gpio_enabled |= (1 << desc->id);
> > + max77686->gpio_enabled |= (1ULL << desc->id);
[]
> Looks good to me.
> Reviewed-by: Chanwoo Choi <cw00.choi@samsung.com>
This could be better with DECLARE_BITMAP and test_bit/set_bit
---
drivers/regulator/max77686.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/regulator/max77686.c b/drivers/regulator/max77686.c
index 23b7c06..17ccf36 100644
--- a/drivers/regulator/max77686.c
+++ b/drivers/regulator/max77686.c
@@ -88,7 +88,7 @@ enum max77686_ramp_rate {
};
struct max77686_data {
- u64 gpio_enabled:MAX77686_REGULATORS;
+ DECLARE_BITMAP(gpio_enabled, MAX77686_REGULATORS);
/* Array indexed by regulator id */
unsigned int opmode[MAX77686_REGULATORS];
@@ -121,7 +121,7 @@ static unsigned int max77686_map_normal_mode(struct max77686_data *max77686,
case MAX77686_BUCK8:
case MAX77686_BUCK9:
case MAX77686_LDO20 ... MAX77686_LDO22:
- if (max77686->gpio_enabled & (1 << id))
+ if (test_bit(id, max77686->gpio_enabled))
return MAX77686_GPIO_CONTROL;
}
@@ -277,7 +277,7 @@ static int max77686_of_parse_cb(struct device_node *np,
}
if (gpio_is_valid(config->ena_gpio)) {
- max77686->gpio_enabled |= (1 << desc->id);
+ set_bit(desc->id, max77686->gpio_enabled);
return regmap_update_bits(config->regmap, desc->enable_reg,
desc->enable_mask,
next prev parent reply other threads:[~2015-05-15 17:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-15 9:25 [patch] regulator: max77686: fix a shift wrapping bug Dan Carpenter
2015-05-15 10:12 ` Krzysztof Kozlowski
2015-05-15 10:19 ` Chanwoo Choi
2015-05-15 17:10 ` Joe Perches [this message]
2015-05-16 0:27 ` Krzysztof Kozlowski
2015-05-18 9:22 ` Dan Carpenter
2015-05-18 17:01 ` [PATCH] regulator: max77686: fix gpio_enabled " Joe Perches
2015-05-19 0:16 ` Krzysztof Kozlowski
2015-05-20 18:10 ` Mark Brown
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=1431709826.15709.15.camel@perches.com \
--to=joe@perches.com \
--cc=broonie@kernel.org \
--cc=cw00.choi@samsung.com \
--cc=dan.carpenter@oracle.com \
--cc=k.kozlowski@samsung.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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