From: Martin Schiller <ms@dev.tdt.de>
To: John Crispin <john@phrozen.org>,
Linus Walleij <linus.walleij@linaro.org>
Cc: "open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] pinctrl: xway: fix gpio-hog related boot issues
Date: Tue, 18 Dec 2018 07:43:11 +0100 [thread overview]
Message-ID: <aaa1ff6b4b6c18168fc9caf803aa253b@dev.tdt.de> (raw)
In-Reply-To: <f84d3544-417d-182e-2dd1-8a79585c40e5@phrozen.org>
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@dev.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@dev.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
prev parent reply other threads:[~2018-12-18 6:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-14 7:48 [PATCH] pinctrl: xway: fix gpio-hog related boot issues Martin Schiller
2018-12-17 14:32 ` Linus Walleij
2018-12-17 16:45 ` John Crispin
2018-12-18 6:43 ` Martin Schiller [this message]
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=aaa1ff6b4b6c18168fc9caf803aa253b@dev.tdt.de \
--to=ms@dev.tdt.de \
--cc=john@phrozen.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).