[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170609142144.5f6c916b@gmail.com>
Date: Fri, 9 Jun 2017 14:21:44 +0200
From: Ralph Sennhauser <ralph.sennhauser@...il.com>
To: Gregory CLEMENT <gregory.clement@...e-electrons.com>
Cc: Linus Walleij <linus.walleij@...aro.org>,
linux-gpio@...r.kernel.org, linux-kernel@...r.kernel.org,
Jason Cooper <jason@...edaemon.net>,
Andrew Lunn <andrew@...n.ch>,
Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>,
Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>,
linux-arm-kernel@...ts.infradead.org,
Chris Packham <Chris.Packham@...iedtelesis.co.nz>
Subject: Re: [PATCH v2] gpio: mvebu: fix regmap_update_bits usage
On Fri, 9 Jun 2017 12:09:17 +0200
Gregory CLEMENT <gregory.clement@...e-electrons.com> wrote:
> In some place in the driver regmap_update_bits was misused. Indeed the
> last argument is not the value of the bit (or group of bits) itself
> but the mask value inside the register.
>
> So when setting the bit N, then the value must be BIT(N) and not 1.
>
> CC: Chris Packham <Chris.Packham@...iedtelesis.co.nz>
> CC: Ralph Sennhauser <ralph.sennhauser@...il.com>
> Signed-off-by: Gregory CLEMENT <gregory.clement@...e-electrons.com>
> ---
Hi Gregory,
Tested-by: Ralph Sennhauser <ralph.sennhauser@...il.com>
Thanks for the prompt fix
Ralph
Powered by blists - more mailing lists