From: Bjorn Helgaas <helgaas@kernel.org>
To: Yao Chen <chenyao11@huawei.com>
Cc: songxiaowei@hisilicon.com, wangbinghui@hisilicon.com,
lorenzo.pieralisi@arm.com, bhelgaas@google.com,
xuwei5@hisilicon.com, robh+dt@kernel.org, mark.rutland@arm.com,
catalin.marinas@arm.com, will.deacon@arm.com,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
suzhuangluan@hisilicon.com, kongfei@hisilicon.com,
dimitrysh@google.com, guodong.xu@linaro.org,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
Tejun Heo <tj@kernel.org>
Subject: Re: [PATCH v2 1/2] PCI: kirin: Add MSI support
Date: Thu, 10 May 2018 09:04:31 -0500 [thread overview]
Message-ID: <20180510140431.GJ173327@bhelgaas-glaptop.roam.corp.google.com> (raw)
In-Reply-To: <1525854012-24228-2-git-send-email-chenyao11@huawei.com>
[+cc Tejun, Wolfram]
On Wed, May 09, 2018 at 04:20:11PM +0800, Yao Chen wrote:
> Add support for MSI.
> ...
> @@ -448,6 +467,26 @@ static int kirin_pcie_host_init(struct pcie_port *pp)
> static int __init kirin_add_pcie_port(struct dw_pcie *pci,
> struct platform_device *pdev)
> {
> + int ret;
> +
> + if (IS_ENABLED(CONFIG_PCI_MSI)) {
> + pci->pp.msi_irq = platform_get_irq(pdev, 0);
> + if (!pci->pp.msi_irq) {
I think this test is incorrect. platform_get_irq() returns a negative
errno value when it fails. Most calls test "irq < 0" to check for failure.
There's a lot of duplicated code like this, so maybe we should consider
putting that check into devm_request_irq(), similar to what
devm_ioremap_resource() does, so the driver code could look like this:
pci->pp.msi_irq = platform_get_irq(pdev, 0);
ret = devm_request_irq(&pdev->dev, pci->pp.msi_irq, ...);
if (ret) {
dev_err(&pdev->dev, "failed to request MSI IRQ\n");
return ret;
}
The basic devm_ioremap_resource() motivation is here: 72f8c0bfa0de ("lib:
devres: add convenience function to remap a resource") and the same
considerations seem to apply here.
But that's more than you need to do for *this* series. So for now, I would
simply fix the test to check for "irq < 0" and update the messages as I
mention below.
> + dev_err(&pdev->dev, "failed to get msi irq[%d]\n",
> + pci->pp.msi_irq);
> + return -ENODEV;
> + }
> + ret = devm_request_irq(&pdev->dev, pci->pp.msi_irq,
> + kirin_pcie_msi_irq_handler,
> + IRQF_SHARED | IRQF_NO_THREAD,
> + "kirin_pcie_msi", &pci->pp);
> + if (ret) {
> + dev_err(&pdev->dev, "failed to request msi irq[%d]\n",
s/msi irq/MSI IRQ/ in both dev_err() messages above. This is because the
message is English text (not code), and the convention is that non-words
like these initialisms written in all caps.
I would style the first one as "failed to get MSI IRQ (%d)" because the %d
there is a return code, probably -ENXIO.
The second one should be "failed to request MSI IRQ %d" because here the %d
is the actual IRQ.
> + pci->pp.msi_irq);
> + return ret;
> + }
> + }
> +
> pci->pp.ops = &kirin_pcie_host_ops;
>
> return dw_pcie_host_init(&pci->pp);
> --
> 1.9.1
>
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2018-05-10 14:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-09 8:20 [PATCH v2 0/2] Add MSI support Yao Chen
2018-05-09 8:20 ` [PATCH v2 1/2] PCI: kirin: " Yao Chen
2018-05-10 14:04 ` Bjorn Helgaas [this message]
2018-05-11 8:30 ` chenyao (F)
2018-05-09 8:20 ` [PATCH v2 2/2] arm64: dts: hi3660: Add pcie msi interrupt attribute Yao Chen
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=20180510140431.GJ173327@bhelgaas-glaptop.roam.corp.google.com \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=catalin.marinas@arm.com \
--cc=chenyao11@huawei.com \
--cc=devicetree@vger.kernel.org \
--cc=dimitrysh@google.com \
--cc=guodong.xu@linaro.org \
--cc=kongfei@hisilicon.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=songxiaowei@hisilicon.com \
--cc=suzhuangluan@hisilicon.com \
--cc=tj@kernel.org \
--cc=wangbinghui@hisilicon.com \
--cc=will.deacon@arm.com \
--cc=wsa+renesas@sang-engineering.com \
--cc=xuwei5@hisilicon.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).