From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
To: Zhang Zekun <zhangzekun11@huawei.com>
Cc: songxiaowei@hisilicon.com, wangbinghui@hisilicon.com,
lpieralisi@kernel.org, kw@linux.com, robh@kernel.org,
bhelgaas@google.com, linux-pci@vger.kernel.org,
ryder.lee@mediatek.com, jianjun.wang@mediatek.com,
sergio.paracuellos@gmail.com,
angelogioacchino.delregno@collabora.com, matthias.bgg@gmail.com,
alyssa@rosenzweig.io, maz@kernel.org, thierry.reding@gmail.com,
Jonathan.Cameron@Huawei.com
Subject: Re: [PATCH v3 2/6] PCI: kirin: Tidy up _probe() related function with dev_err_probe()
Date: Wed, 5 Mar 2025 11:24:31 +0530 [thread overview]
Message-ID: <20250305055431.ugiwvydrdw4rszte@thinkpad> (raw)
In-Reply-To: <20240831040413.126417-3-zhangzekun11@huawei.com>
On Sat, Aug 31, 2024 at 12:04:09PM +0800, Zhang Zekun wrote:
> The combination of dev_err() and the returned error code could be
> replaced by dev_err_probe() in driver's probe function. Let's,
> converting to dev_err_probe() to make code more simple.
>
> Suggested-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> Signed-off-by: Zhang Zekun <zhangzekun11@huawei.com>
> Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> ---
> v3: Wrap the line which is too long.
>
> drivers/pci/controller/dwc/pcie-kirin.c | 40 ++++++++++---------------
> 1 file changed, 16 insertions(+), 24 deletions(-)
>
> diff --git a/drivers/pci/controller/dwc/pcie-kirin.c b/drivers/pci/controller/dwc/pcie-kirin.c
> index e9bda1746ca5..3c9d8da3a241 100644
> --- a/drivers/pci/controller/dwc/pcie-kirin.c
> +++ b/drivers/pci/controller/dwc/pcie-kirin.c
> @@ -216,10 +216,9 @@ static int hi3660_pcie_phy_start(struct hi3660_pcie_phy *phy)
>
> usleep_range(PIPE_CLK_WAIT_MIN, PIPE_CLK_WAIT_MAX);
> reg_val = kirin_apb_phy_readl(phy, PCIE_APB_PHY_STATUS0);
> - if (reg_val & PIPE_CLK_STABLE) {
> - dev_err(dev, "PIPE clk is not stable\n");
> - return -EINVAL;
> - }
> + if (reg_val & PIPE_CLK_STABLE)
> + return dev_err_probe(dev, -EINVAL,
> + "PIPE clk is not stable\n");
I guess this is a timeout issue, so -ETIMEDOUT.
>
> return 0;
> }
> @@ -371,10 +370,9 @@ static int kirin_pcie_get_gpio_enable(struct kirin_pcie *pcie,
> if (ret < 0)
> return 0;
>
> - if (ret > MAX_PCI_SLOTS) {
> - dev_err(dev, "Too many GPIO clock requests!\n");
> - return -EINVAL;
> - }
> + if (ret > MAX_PCI_SLOTS)
> + return dev_err_probe(dev, -EINVAL,
> + "Too many GPIO clock requests!\n");
>
> pcie->n_gpio_clkreq = ret;
>
> @@ -421,16 +419,14 @@ static int kirin_pcie_parse_port(struct kirin_pcie *pcie,
> }
>
> pcie->num_slots++;
> - if (pcie->num_slots > MAX_PCI_SLOTS) {
> - dev_err(dev, "Too many PCI slots!\n");
> - return -EINVAL;
> - }
> + if (pcie->num_slots > MAX_PCI_SLOTS)
> + return dev_err_probe(dev, -EINVAL,
> + "Too many PCI slots!\n");
>
> ret = of_pci_get_devfn(child);
> - if (ret < 0) {
> - dev_err(dev, "failed to parse devfn: %d\n", ret);
> - return ret;
> - }
> + if (ret < 0)
> + return dev_err_probe(dev, ret,
> + "failed to parse devfn\n");
>
> slot = PCI_SLOT(ret);
>
> @@ -725,16 +721,12 @@ static int kirin_pcie_probe(struct platform_device *pdev)
> struct dw_pcie *pci;
> int ret;
>
> - if (!dev->of_node) {
> - dev_err(dev, "NULL node\n");
> - return -EINVAL;
> - }
> + if (!dev->of_node)
> + return dev_err_probe(dev, -EINVAL, "NULL node\n");
This check is pointless, so you should drop it.
>
> data = of_device_get_match_data(dev);
> - if (!data) {
> - dev_err(dev, "OF data missing\n");
> - return -EINVAL;
> - }
> + if (!data)
> + return dev_err_probe(dev, -EINVAL, "OF data missing\n");
-ENODATA
- Mani
--
மணிவண்ணன் சதாசிவம்
next prev parent reply other threads:[~2025-03-05 5:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-31 4:04 [PATCH v3 0/6] Simplify code with _scoped() helper functions Zhang Zekun
2024-08-31 4:04 ` [PATCH v3 1/6] PCI: kirin: Use helper function for_each_available_child_of_node_scoped() Zhang Zekun
2025-03-05 5:49 ` Manivannan Sadhasivam
2024-08-31 4:04 ` [PATCH v3 2/6] PCI: kirin: Tidy up _probe() related function with dev_err_probe() Zhang Zekun
2025-03-05 5:54 ` Manivannan Sadhasivam [this message]
2025-03-05 11:24 ` Krzysztof Wilczyński
2025-03-06 9:45 ` Krzysztof Wilczyński
2024-08-31 4:04 ` [PATCH v3 3/6] PCI: mediatek: Use helper function for_each_available_child_of_node_scoped() Zhang Zekun
2025-03-05 5:55 ` Manivannan Sadhasivam
2024-08-31 4:04 ` [PATCH v3 4/6] PCI: mt7621: " Zhang Zekun
2025-03-05 5:56 ` Manivannan Sadhasivam
2024-08-31 4:04 ` [PATCH v3 5/6] PCI: apple: Use helper function for_each_child_of_node_scoped() Zhang Zekun
2025-03-05 5:57 ` Manivannan Sadhasivam
2024-08-31 4:04 ` [PATCH v3 6/6] PCI: tegra: " Zhang Zekun
2025-03-05 5:59 ` Manivannan Sadhasivam
2025-03-02 18:32 ` [PATCH v3 0/6] Simplify code with _scoped() helper functions Krzysztof Wilczyński
2025-03-05 11:25 ` Krzysztof Wilczyński
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=20250305055431.ugiwvydrdw4rszte@thinkpad \
--to=manivannan.sadhasivam@linaro.org \
--cc=Jonathan.Cameron@Huawei.com \
--cc=alyssa@rosenzweig.io \
--cc=angelogioacchino.delregno@collabora.com \
--cc=bhelgaas@google.com \
--cc=jianjun.wang@mediatek.com \
--cc=kw@linux.com \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=maz@kernel.org \
--cc=robh@kernel.org \
--cc=ryder.lee@mediatek.com \
--cc=sergio.paracuellos@gmail.com \
--cc=songxiaowei@hisilicon.com \
--cc=thierry.reding@gmail.com \
--cc=wangbinghui@hisilicon.com \
--cc=zhangzekun11@huawei.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