From: Bjorn Helgaas <helgaas@kernel.org>
To: phucduc.bui@gmail.com
Cc: Lorenzo Pieralisi <lpieralisi@kernel.org>,
kwilczynski@kernel.org, Manivannan Sadhasivam <mani@kernel.org>,
Rob Herring <robh@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
Thierry Reding <thierry.reding@kernel.org>,
Jonathan Hunter <jonathanh@nvidia.com>,
Vidya Sagar <vidyas@nvidia.com>,
Manikanta Maddireddy <mmaddireddy@nvidia.com>,
Niklas Cassel <cassel@kernel.org>,
linux-pci@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] PCI: tegra194: use dev_err_probe() for PERST GPIO
Date: Wed, 7 Oct 2026 15:46:38 -0500 [thread overview]
Message-ID: <20261007204638.GA785135@bhelgaas> (raw)
In-Reply-To: <20261007104847.507776-1-phucduc.bui@gmail.com>
On Wed, Oct 07, 2026 at 05:48:46PM +0700, phucduc.bui@gmail.com wrote:
> From: bui duc phuc <phucduc.bui@gmail.com>
>
> Use dev_err_probe() when getting the PERST GPIO to simplify error
> handling and properly handle -EPROBE_DEFER.
>
> Signed-off-by: bui duc phuc <phucduc.bui@gmail.com>
For future posts, please match the subject line capitalization style:
PCI: tegra194: Use ...
And style as "PERST#" in the subject, commit log, and dmesg text to
match spec usage.
No need to repost just for this; we can tweak these when applying.
> ---
> drivers/pci/controller/dwc/pcie-tegra194.c | 15 +++------------
> 1 file changed, 3 insertions(+), 12 deletions(-)
>
> diff --git a/drivers/pci/controller/dwc/pcie-tegra194.c b/drivers/pci/controller/dwc/pcie-tegra194.c
> index 63a0f56cad8e..767e11216196 100644
> --- a/drivers/pci/controller/dwc/pcie-tegra194.c
> +++ b/drivers/pci/controller/dwc/pcie-tegra194.c
> @@ -1200,18 +1200,9 @@ static int tegra_pcie_dw_parse_dt(struct tegra_pcie_dw *pcie)
>
> /* Endpoint mode specific DT entries */
> pcie->pex_rst_gpiod = devm_gpiod_get(pcie->dev, "reset", GPIOD_IN);
> - if (IS_ERR(pcie->pex_rst_gpiod)) {
> - int err = PTR_ERR(pcie->pex_rst_gpiod);
> - const char *level = KERN_ERR;
> -
> - if (err == -EPROBE_DEFER)
> - level = KERN_DEBUG;
> -
> - dev_printk(level, pcie->dev,
> - dev_fmt("Failed to get PERST GPIO: %d\n"),
> - err);
> - return err;
> - }
> + if (IS_ERR(pcie->pex_rst_gpiod))
> + return dev_err_probe(pcie->dev, PTR_ERR(pcie->pex_rst_gpiod),
> + "Failed to get PERST GPIO\n");
>
> pcie->pex_refclk_sel_gpiod = devm_gpiod_get_optional(pcie->dev,
> "nvidia,refclk-select",
> --
> 2.43.0
>
next prev parent reply other threads:[~2026-10-07 20:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-07 10:48 [PATCH 1/2] PCI: tegra194: use dev_err_probe() for PERST GPIO phucduc.bui
2026-10-07 10:48 ` [PATCH 2/2] PCI: tegra194: propagate REFCLK select GPIO errors phucduc.bui
2026-10-07 10:58 ` sashiko-bot
2026-10-12 8:36 ` Manikanta Maddireddy
2026-10-12 9:41 ` Bui Duc Phuc
2026-10-07 10:56 ` [PATCH 1/2] PCI: tegra194: use dev_err_probe() for PERST GPIO sashiko-bot
2026-10-07 20:46 ` Bjorn Helgaas [this message]
2026-10-08 11:08 ` Bui Duc Phuc
2026-10-12 8:38 ` Manikanta Maddireddy
2026-10-12 9:38 ` Bui Duc Phuc
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=20261007204638.GA785135@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=cassel@kernel.org \
--cc=jonathanh@nvidia.com \
--cc=kwilczynski@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=mmaddireddy@nvidia.com \
--cc=phucduc.bui@gmail.com \
--cc=robh@kernel.org \
--cc=thierry.reding@kernel.org \
--cc=vidyas@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.