From: Alex Elder <elder@riscstar.com>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
lpieralisi@kernel.org, kwilczynski@kernel.org, mani@kernel.org,
robh@kernel.org, bhelgaas@google.com
Cc: dlan@gentoo.org, aurelien@aurel32.net, johannes@erdfelt.com,
p.zabel@pengutronix.de, christian.bruel@foss.st.com,
thippeswamy.havalige@amd.com, krishna.chundru@oss.qualcomm.com,
mayank.rana@oss.qualcomm.com, qiang.yu@oss.qualcomm.com,
shradha.t@samsung.com, inochiama@gmail.com, guodong@riscstar.com,
linux-pci@vger.kernel.org, spacemit@lists.linux.dev,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 5/7] PCI: spacemit: Add SpacemiT PCIe host driver
Date: Mon, 10 Nov 2025 09:05:35 -0600 [thread overview]
Message-ID: <4a7d6e07-82f8-437f-bccb-cf294974a53e@riscstar.com> (raw)
In-Reply-To: <120b2f62-25e6-4ea3-9907-230080c61f70@wanadoo.fr>
On 11/8/25 7:00 AM, Christophe JAILLET wrote:
> Le 07/11/2025 à 20:15, Alex Elder a écrit :
>> Introduce a driver for the PCIe host controller found in the SpacemiT
>> K1 SoC. The hardware is derived from the Synopsys DesignWare PCIe IP.
>> The driver supports three PCIe ports that operate at PCIe gen2 transfer
>> rates (5 GT/sec). The first port uses a combo PHY, which may be
>> configured for use for USB 3 instead.
>>
>> Signed-off-by: Alex Elder <elder@riscstar.com>
>> ---
>
> ...
>
>> +static int k1_pcie_probe(struct platform_device *pdev)
>> +{
>> + struct device *dev = &pdev->dev;
>> + struct k1_pcie *k1;
>> + int ret;
>> +
>> + k1 = devm_kzalloc(dev, sizeof(*k1), GFP_KERNEL);
>> + if (!k1)
>> + return -ENOMEM;
>> +
>> + k1->pmu = syscon_regmap_lookup_by_phandle_args(dev_of_node(dev),
>> + SYSCON_APMU, 1,
>> + &k1->pmu_off);
>> + if (IS_ERR(k1->pmu))
>> + return dev_err_probe(dev, PTR_ERR(k1->pmu),
>> + "failed to lookup PMU registers\n");
>> +
>> + k1->link = devm_platform_ioremap_resource_byname(pdev, "link");
>> + if (!k1->link)
>
> if (IS_ERR(k1->link)) ?
Yes, you're right. I'll fix this in the next version.
>
>> + return dev_err_probe(dev, -ENOMEM,
>> + "failed to map \"link\" registers\n");
>
> Message with -ENOMEM are ignored, so a direct return -ENOMEM is less
> verbose and will bhave the same. See [1].
>
> But in this case, I think it should be PTR_ERR(k1->link).
Yes, that's what it will be.
> [1]: https://elixir.bootlin.com/linux/v6.18-rc2/source/drivers/base/
> core.c#L5015
>
>> +
>> + k1->pci.dev = dev;
>> + k1->pci.ops = &k1_pcie_ops;
>> + dw_pcie_cap_set(&k1->pci, REQ_RES);
>> +
>> + k1->pci.pp.ops = &k1_pcie_host_ops;
>> +
>> + /* Hold the PHY in reset until we start the link */
>> + regmap_set_bits(k1->pmu, k1->pmu_off + PCIE_CLK_RESET_CONTROL,
>> + APP_HOLD_PHY_RST);
>> +
>> + ret = devm_regulator_get_enable(dev, "vpcie3v3");
>> + if (ret)
>> + return dev_err_probe(dev, ret,
>> + "failed to get \"vpcie3v3\" supply\n");
>> +
>> + pm_runtime_set_active(dev);
>> + pm_runtime_no_callbacks(dev);
>> + devm_pm_runtime_enable(dev);
>> +
>> + platform_set_drvdata(pdev, k1);
>> +
>> + ret = k1_pcie_parse_port(k1);
>> + if (ret)
>> + return dev_err_probe(dev, ret, "failed to parse root port\n");
>> +
>> + ret = dw_pcie_host_init(&k1->pci.pp);
>> + if (ret)
>> + return dev_err_probe(dev, ret, "failed to initialize host\n");
>> +
>> + return 0;
>> +}
>
> ...
>
>> +static const struct of_device_id k1_pcie_of_match_table[] = {
>> + { .compatible = "spacemit,k1-pcie", },
>> + { },
>
> Unneeded trainling comma after a terminator.
Unneeded, but not erroneous. In any case, I'll drop it based
on your preference.
Thank you for your review.
-Alex
>
>> +};
>> +
>> +static struct platform_driver k1_pcie_driver = {
>> + .probe = k1_pcie_probe,
>> + .remove = k1_pcie_remove,
>> + .driver = {
>> + .name = "spacemit-k1-pcie",
>> + .of_match_table = k1_pcie_of_match_table,
>> + .probe_type = PROBE_PREFER_ASYNCHRONOUS,
>> + },
>> +};
>> +module_platform_driver(k1_pcie_driver);
>
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2025-11-10 15:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-07 19:15 [PATCH v5 0/7] Introduce SpacemiT K1 PCIe phy and host controller Alex Elder
2025-11-07 19:15 ` [PATCH v5 1/7] dt-bindings: phy: spacemit: Add SpacemiT PCIe/combo PHY Alex Elder
2025-11-07 19:15 ` [PATCH v5 2/7] dt-bindings: phy: spacemit: Introduce PCIe PHY Alex Elder
2025-11-07 19:15 ` [PATCH v5 3/7] dt-bindings: pci: spacemit: Introduce PCIe host controller Alex Elder
2025-11-07 19:15 ` [PATCH v5 4/7] phy: spacemit: Introduce PCIe/combo PHY Alex Elder
2025-11-07 19:15 ` [PATCH v5 5/7] PCI: spacemit: Add SpacemiT PCIe host driver Alex Elder
2025-11-08 13:00 ` Christophe JAILLET
2025-11-10 15:05 ` Alex Elder [this message]
2025-11-07 19:15 ` [PATCH v5 6/7] riscv: dts: spacemit: Add a PCIe regulator Alex Elder
2025-11-07 19:15 ` [PATCH v5 7/7] riscv: dts: spacemit: PCIe and PHY-related updates Alex Elder
2025-11-08 11:08 ` [PATCH v5 0/7] Introduce SpacemiT K1 PCIe phy and host controller Aurelien Jarno
2025-11-10 15:20 ` Alex Elder
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=4a7d6e07-82f8-437f-bccb-cf294974a53e@riscstar.com \
--to=elder@riscstar.com \
--cc=aurelien@aurel32.net \
--cc=bhelgaas@google.com \
--cc=christian.bruel@foss.st.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=dlan@gentoo.org \
--cc=guodong@riscstar.com \
--cc=inochiama@gmail.com \
--cc=johannes@erdfelt.com \
--cc=krishna.chundru@oss.qualcomm.com \
--cc=kwilczynski@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=mayank.rana@oss.qualcomm.com \
--cc=p.zabel@pengutronix.de \
--cc=qiang.yu@oss.qualcomm.com \
--cc=robh@kernel.org \
--cc=shradha.t@samsung.com \
--cc=spacemit@lists.linux.dev \
--cc=thippeswamy.havalige@amd.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).