linux-kernel - Re: [PATCH] pinctrl: xway: fix gpio-hog related boot issues

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <aaa1ff6b4b6c18168fc9caf803aa253b@dev.tdt.de>
Date:   Tue, 18 Dec 2018 07:43:11 +0100
From:   Martin Schiller <ms@....tdt.de>
To:     John Crispin <john@...ozen.org>,
        Linus Walleij <linus.walleij@...aro.org>
Cc:     "open list:GPIO SUBSYSTEM" <linux-gpio@...r.kernel.org>,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] pinctrl: xway: fix gpio-hog related boot issues

On 2018-12-17 17:45, John Crispin wrote:
> On 17/12/2018 15:32, Linus Walleij wrote:
>> On Fri, Dec 14, 2018 at 8:48 AM Martin Schiller <ms@....tdt.de> wrote:
>> 
>>> This patch is based on commit a86caa9ba5d7 ("pinctrl: msm: fix 
>>> gpio-hog
>>> related boot issues").
>>> 
>>> It fixes the issue that the gpio ranges needs to be defined before
>>> gpiochip_add().
>>> 
>>> Therefore, we also have to swap the order of registering the pinctrl
>>> driver and registering the gpio chip.
>>> 
>>> You also have to add the "gpio-ranges" property to the pinctrl device
>>> node to get it finally working.
>>> 
>>> Signed-off-by: Martin Schiller <ms@....tdt.de>
>> Patch applied unless John Crispin has objections, it looks
>> good to me!
>> 
>> Yours,
>> Linus Walleij
> 
> 
> sorry did not see the patch in my inbox
> 

Sorry, that was my fault.
I've added everyone from getmaintainers.pl output, but forgot to also 
add you.

Regards,
Martin