[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <032a7c70-38b1-c147-4f13-ddb71971ae80@axentia.se>
Date: Fri, 2 Dec 2016 09:56:21 +0100
From: Peter Rosin <peda@...ntia.se>
To: Linus Walleij <linus.walleij@...aro.org>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Andrey Smirnov <andrew.smirnov@...il.com>,
Neil Armstrong <narmstrong@...libre.com>,
"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>
Subject: Re: [PATCH 1/3] pinctrl: sx150x: use correct registers for reg_sense
(sx1502 and sx1508)
On 2016-11-25 14:40, Linus Walleij wrote:
> On Thu, Nov 24, 2016 at 9:45 PM, Peter Rosin <peda@...ntia.se> wrote:
>
>> All other registers on these chips are 8-bit, but reg_sense is 16-bits
>> and therefore needs to be moved down one notch.
>> This was apparently overlooked in the conversion to regmap, which only
>> updated the register locations for the 16-bit chips.
>>
>> Fixes: 6489677f86c3 ("pinctrl-sx150x: Replace sx150x_*_cfg by means of regmap API")
>> Signed-off-by: Peter Rosin <peda@...ntia.se>
>
> Patch applied.
Hi!
I'm just dubble-checking that the intention is to get this patch all
the way upstream in time for v4.10-rc1? Because right now there is a
regression regarding irq handling on sx1502/sx1508 in linux-next.
I see the patch in your devel branch, but it's not yet in the for-next
branch, which happened pretty quickly for my other pair of patches for
the sx150x driver. So, I worry that there might have been some for-next
deadline?
No rush, it's only been a week, I'm just asking...
Cheers,
Peter
Powered by blists - more mailing lists