From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Saravana Kannan <saravanak@google.com>,
Tomasz Figa <tomasz.figa@gmail.com>,
Sylwester Nawrocki <s.nawrocki@samsung.com>,
Alim Akhtar <alim.akhtar@samsung.com>,
Linus Walleij <linus.walleij@linaro.org>
Cc: kernel-team@android.com, linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-gpio@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] pinctrl: samsung: Finish initializing the gpios before registering them
Date: Thu, 28 Jul 2022 10:32:24 +0200 [thread overview]
Message-ID: <49e4f45a-51da-ec4c-9ebb-dfa022bf8a88@linaro.org> (raw)
In-Reply-To: <20220727013349.3056826-1-saravanak@google.com>
On 27/07/2022 03:33, Saravana Kannan wrote:
> As soon as a gpio is registered, it should be usable by a consumer. So,
> do all the initialization before registering the gpios. Without this
> change, a consumer can request a GPIO IRQ and have the gpio to IRQ
> mapping fail.
>
> Signed-off-by: Saravana Kannan <saravanak@google.com>
Looks good.
Linus,
It's too late for me to pick it up, so make you could grab it directly?
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Otherwise it will wait for merge window to finish.
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-07-28 8:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20220727013403epcas2p452b5f66597b4298b7a573393927ac96e@epcas2p4.samsung.com>
2022-07-27 1:33 ` [PATCH v1] pinctrl: samsung: Finish initializing the gpios before registering them Saravana Kannan
2022-07-27 2:01 ` Chanho Park
2022-07-27 2:15 ` Saravana Kannan
2022-07-27 13:54 ` Sam Protsenko
2022-07-28 8:32 ` Krzysztof Kozlowski [this message]
2022-08-16 9:23 ` Krzysztof Kozlowski
2022-08-25 12:08 ` Linus Walleij
2022-08-25 12:11 ` Krzysztof Kozlowski
2022-08-25 17:05 ` Saravana Kannan
2022-08-16 9:24 ` Krzysztof Kozlowski
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=49e4f45a-51da-ec4c-9ebb-dfa022bf8a88@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=alim.akhtar@samsung.com \
--cc=kernel-team@android.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=s.nawrocki@samsung.com \
--cc=saravanak@google.com \
--cc=tomasz.figa@gmail.com \
/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).