From: Alex Elder <elder@riscstar.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: lpieralisi@kernel.org, kwilczynski@kernel.org, mani@kernel.org,
robh@kernel.org, bhelgaas@google.com, 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 v4 5/7] PCI: spacemit: introduce SpacemiT PCIe host driver
Date: Thu, 30 Oct 2025 20:16:17 -0500 [thread overview]
Message-ID: <f1bec6f4-bf44-4cbf-a676-fa81d81531d4@riscstar.com> (raw)
In-Reply-To: <20251030230801.GA1660222@bhelgaas>
On 10/30/25 6:08 PM, Bjorn Helgaas wrote:
> In subject, capitalize "introduce" to match history. Or you could
> just use "Add ...", which has the advantage of being shorter.
OK. I'll capitalize all of them in this series.
> On Thu, Oct 30, 2025 at 05:02:56PM -0500, Alex Elder wrote:
>> 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.
>> ...
>
> I guess this doesn't support INTx interrupts at all?
It can, but I removed that support first to simplify the task
of converting the original code, and second because I had no way
to test it. I planned for it to be added at a future date.
>> +++ b/drivers/pci/controller/dwc/Kconfig
>> @@ -509,6 +509,17 @@ config PCI_KEYSTONE_EP
>> on DesignWare hardware and therefore the driver re-uses the
>> DesignWare core functions to implement the driver.
>>
>> +config PCIE_SPACEMIT_K1
>> + tristate "SpacemiT K1 PCIe controller (host mode)"
>
> Move this to keep the menu items alphabetized by vendor.
OK. I was going by Kconfig option name, but now I see
what you mean.
I'll put it between PCIE_SOPHGO_DW and PCIE_SPEAR13XX.
>> + depends on ARCH_SPACEMIT || COMPILE_TEST
>> + depends on PCI && OF && HAS_IOMEM
>
> I don't think you need PCI or OF.
You're right. PCI for sure, but it doesn't look like I make
an direct OF calls either. I'll drop them both.
>> + select PCIE_DW_HOST
>> + select PCI_PWRCTRL_SLOT
>> + default ARCH_SPACEMIT
>> + help
>> + Enables support for the PCIe controller in the K1 SoC operating
>> + in host mode.
>
> Most help text includes both the vendor and the product line names.
I guess I didn't include "SpacemiT". I'll add that, and will try
to come up with a few more words in the description.
Thanks for your quick response.
-Alex
next prev parent reply other threads:[~2025-10-31 1:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 22:02 [PATCH v4 0/7] Introduce SpacemiT K1 PCIe phy and host controller Alex Elder
2025-10-30 22:02 ` [PATCH v4 3/7] dt-bindings: pci: spacemit: introduce PCIe " Alex Elder
2025-10-31 0:58 ` Rob Herring
2025-10-31 1:37 ` Alex Elder
2025-10-30 22:02 ` [PATCH v4 5/7] PCI: spacemit: introduce SpacemiT PCIe host driver Alex Elder
2025-10-30 23:08 ` Bjorn Helgaas
2025-10-31 1:16 ` Alex Elder [this message]
2025-10-31 22:31 ` Aurelien Jarno
2025-11-03 16:51 ` 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=f1bec6f4-bf44-4cbf-a676-fa81d81531d4@riscstar.com \
--to=elder@riscstar.com \
--cc=aurelien@aurel32.net \
--cc=bhelgaas@google.com \
--cc=christian.bruel@foss.st.com \
--cc=dlan@gentoo.org \
--cc=guodong@riscstar.com \
--cc=helgaas@kernel.org \
--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