From: "Chanho Park" <chanho61.park@samsung.com>
To: "'Saravana Kannan'" <saravanak@google.com>,
"'Tomasz Figa'" <tomasz.figa@gmail.com>,
"'Krzysztof Kozlowski'" <krzysztof.kozlowski@linaro.org>,
"'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: Wed, 27 Jul 2022 11:01:58 +0900 [thread overview]
Message-ID: <000001d8a15c$da89d980$8f9d8c80$@samsung.com> (raw)
In-Reply-To: <20220727013349.3056826-1-saravanak@google.com>
> Subject: [PATCH v1] pinctrl: samsung: Finish initializing the gpios before
> registering them
>
> 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>
Make sense for me and I tested this on my Exynos Auto v9 SADK board.
Reviewed-by: Chanho Park <chanho61.park@samsung.com>
Tested-by: Chanho Park <chanho61.park@samsung.com>
Best Regards,
Chanho Park
next prev parent reply other threads:[~2022-07-27 2:02 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 [this message]
2022-07-27 2:15 ` Saravana Kannan
2022-07-27 13:54 ` Sam Protsenko
2022-07-28 8:32 ` Krzysztof Kozlowski
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='000001d8a15c$da89d980$8f9d8c80$@samsung.com' \
--to=chanho61.park@samsung.com \
--cc=alim.akhtar@samsung.com \
--cc=kernel-team@android.com \
--cc=krzysztof.kozlowski@linaro.org \
--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).