[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <192e8364fed24e91a12b5dec78fa06f0@svr-chch-ex1.atlnz.lc>
Date: Sun, 11 Jun 2017 21:54:14 +0000
From: Chris Packham <Chris.Packham@...iedtelesis.co.nz>
To: Ralph Sennhauser <ralph.sennhauser@...il.com>,
Gregory CLEMENT <gregory.clement@...e-electrons.com>
CC: Linus Walleij <linus.walleij@...aro.org>,
"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
"linux-kernel@...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"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH v2] gpio: mvebu: fix regmap_update_bits usage
On 10/06/17 00:22, Ralph Sennhauser wrote:
> 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
Also works for me
Tested-by: Chris Packham <Chris.Packham@...iedtelesis.co.nz>
Powered by blists - more mailing lists