From: Jon Hunter <jonathanh@nvidia.com>
To: Prathamesh Shete <pshete@nvidia.com>,
linus.walleij@linaro.org, brgl@bgdev.pl,
thierry.reding@gmail.com, linux-tegra@vger.kernel.org,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: smangipudi@nvidia.com, Manish Bhardwaj <mbhardwaj@nvidia.com>
Subject: Re: [PATCH v2] gpio: tegra186: Check PMC driver status before any request
Date: Wed, 7 Jun 2023 12:46:42 +0100 [thread overview]
Message-ID: <51d00894-301f-6e0f-785e-3ff3a17a635f@nvidia.com> (raw)
In-Reply-To: <20230607113104.11761-1-pshete@nvidia.com>
On 07/06/2023 12:31, Prathamesh Shete wrote:
> When the PMC device is disabled, probing of the Tegra186 GPIO driver
> fails because the IRQ domain that is registered by the PMC driver is
> not found. The PMC IRQ domain is only used for wake-up and does not
> impact GPIO functionality in general. Therefore, if the PMC device is
> disabled, skip looking up the PMC IRQ domain to allow the GPIO driver
> to be probed.
>
> Signed-off-by: Manish Bhardwaj <mbhardwaj@nvidia.com>
> Signed-off-by: Prathamesh Shete <pshete@nvidia.com>
> ---
> drivers/gpio/gpio-tegra186.c | 14 +++++++++-----
> 1 file changed, 9 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/gpio/gpio-tegra186.c b/drivers/gpio/gpio-tegra186.c
> index 464b0ea3b6f1..80d08ddde40e 100644
> --- a/drivers/gpio/gpio-tegra186.c
> +++ b/drivers/gpio/gpio-tegra186.c
> @@ -964,11 +964,15 @@ static int tegra186_gpio_probe(struct platform_device *pdev)
>
> np = of_find_matching_node(NULL, tegra186_pmc_of_match);
> if (np) {
> - irq->parent_domain = irq_find_host(np);
> - of_node_put(np);
> -
> - if (!irq->parent_domain)
> - return -EPROBE_DEFER;
> + if (of_device_is_available(np)) {
> + irq->parent_domain = irq_find_host(np);
> + of_node_put(np);
> +
> + if (!irq->parent_domain)
> + return -EPROBE_DEFER;
> + } else {
> + of_node_put(np);
> + }
> }
>
> irq->map = devm_kcalloc(&pdev->dev, gpio->gpio.ngpio,
Thanks!
Reviewed-by: Jon Hunter <jonathanh@nvidia.com>
Jon
--
nvpublic
next prev parent reply other threads:[~2023-06-07 11:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 7:17 [PATCH] " Prathamesh Shete
2023-06-06 8:53 ` Jon Hunter
2023-06-07 10:55 ` Jon Hunter
2023-06-07 11:31 ` [PATCH v2] " Prathamesh Shete
2023-06-07 11:46 ` Jon Hunter [this message]
2023-06-08 16:02 ` Thierry Reding
2023-06-06 9:48 ` [PATCH] " andy.shevchenko
2023-06-09 7:18 ` Linus Walleij
-- strict thread matches above, loose matches on Subject: below --
2022-10-24 14:02 Thierry Reding
2022-10-26 7:06 ` [PATCH v2] " Prathamesh Shete
2022-11-08 10:34 ` Linus Walleij
2022-11-08 13:29 ` Thierry Reding
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=51d00894-301f-6e0f-785e-3ff3a17a635f@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mbhardwaj@nvidia.com \
--cc=pshete@nvidia.com \
--cc=smangipudi@nvidia.com \
--cc=thierry.reding@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
all inboxes | Powered by JetHome®