From: Bjorn Helgaas <helgaas@kernel.org>
To: Frank Li <Frank.Li@nxp.com>, Jon Mason <jdmason@kudzu.us>
Cc: maz@kernel.org, tglx@linutronix.de, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, shawnguo@kernel.org,
s.hauer@pengutronix.de, kw@linux.com, bhelgaas@google.com,
kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-pci@vger.kernel.org,
peng.fan@nxp.com, aisheng.dong@nxp.com, kernel@pengutronix.de,
festevam@gmail.com, linux-imx@nxp.com, kishon@ti.com,
lorenzo.pieralisi@arm.com, ntb@lists.linux.dev
Subject: Re: [PATCH v2 4/4] pcie: endpoint: pci-epf-vntb: add endpoint msi support
Date: Fri, 15 Jul 2022 16:06:19 -0500 [thread overview]
Message-ID: <20220715210619.GA1190861@bhelgaas> (raw)
In-Reply-To: <20220715192219.1489403-5-Frank.Li@nxp.com>
[+to Jon, since I guess he will apply or at least review this, not me]
On Fri, Jul 15, 2022 at 02:22:19PM -0500, Frank Li wrote:
> This patch add msi support for ntb endpoint(EP) side.
> EP side driver query if system have msi controller.
> Setup doorbell address according to struct msi_msg.
>
> So PCIe host can write this doorbell address to EP
> side's irq.
>
> If no msi controller exist, failback software polling.
s/This patch add/Add/
s/msi/MSI/ (several)
s/ntb/NTB/
s/irq/IRQ/
s/failback/fall back to/
Rewrap commit log to fill 75 columns to make it easier to read.
> +static int epf_ntb_db_size(struct epf_ntb *ntb)
> +{
> + const struct pci_epc_features *epc_features;
> + size_t size = 4 * ntb->db_count;
> + u32 align;
Replace tabs with spaces in these declarations , since that's what
code below does, e.g., in epf_ntb_db_bar_init(), etc.
> + dev_info(dev, "Can't allocate MSI, failure back to poll mode\n");
s/failure/fall/
> + return;
> + }
> +
> + dev_info(dev, "vntb use MSI as doorbell\n");
> + ret = devm_request_irq(dev, virq,
> + epf_ntb_interrupt_handler, 0,
> + "ntb", ntb);
> +
> + if (ret)
> + dev_err(dev, "request irq failure\n");
s/irq/IRQ/ (or spell out "devm_request_irq()").
Capitalize all messages or none of them. Match the prevailing style
of the file.
next prev parent reply other threads:[~2022-07-15 21:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-15 19:22 [PATCH v2 0/4] PCI EP driver support MSI doorbell from host Frank Li
2022-07-15 19:22 ` [PATCH v2 1/4] irqchip: allow pass down .pm field at IRQCHIP_PLATFORM_DRIVER_END Frank Li
2022-07-15 19:22 ` [PATCH v2 2/4] irqchip: imx mu worked as msi controller Frank Li
2022-07-15 19:22 ` [PATCH v2 3/4] dt-bindings: irqchip: imx mu work " Frank Li
2022-07-15 23:06 ` Rob Herring
2022-07-15 19:22 ` [PATCH v2 4/4] pcie: endpoint: pci-epf-vntb: add endpoint msi support Frank Li
2022-07-15 21:06 ` Bjorn Helgaas [this message]
2022-07-15 21:14 ` [PATCH v2 0/4] PCI EP driver support MSI doorbell from host Bjorn Helgaas
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=20220715210619.GA1190861@bhelgaas \
--to=helgaas@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=aisheng.dong@nxp.com \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=jdmason@kudzu.us \
--cc=kernel@pengutronix.de \
--cc=kernel@vger.kernel.org \
--cc=kishon@ti.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kw@linux.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=maz@kernel.org \
--cc=ntb@lists.linux.dev \
--cc=peng.fan@nxp.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=tglx@linutronix.de \
/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).