From: zhangsenchuan <zhangsenchuan@eswincomputing.com>
To: "Manivannan Sadhasivam" <mani@kernel.org>
Cc: "Min Lin" <linmin@eswincomputing.com>,
bhelgaas@google.com, krzk+dt@kernel.org, conor+dt@kernel.org,
lpieralisi@kernel.org, kwilczynski@kernel.org, robh@kernel.org,
p.zabel@pengutronix.de, linux-pci@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
christian.bruel@foss.st.com, shradha.t@samsung.com,
krishna.chundru@oss.qualcomm.com, thippeswamy.havalige@amd.com,
inochiama@gmail.com, Frank.li@nxp.com, ningyu@eswincomputing.com,
pinkesh.vaghela@einfochips.com, ouyanghui@eswincomputing.com
Subject: Re: Re: [PATCH v11 2/2] PCI: eic7700: Add Eswin PCIe host controller driver
Date: Mon, 16 Mar 2026 14:30:46 +0800 (GMT+08:00) [thread overview]
Message-ID: <6474f691.43fe.19cf5570586.Coremail.zhangsenchuan@eswincomputing.com> (raw)
In-Reply-To: <veqgbspu5fmm6f4dvrtz5s6xtibbglf6ejb4b6zzmzhgefksny@rzuobvk6jkt7>
> > > > > On Fri, Feb 27, 2026 at 07:18:08PM +0800, zhangsenchuan@eswincomputing.com wrote:
> > > > > > From: Senchuan Zhang <zhangsenchuan@eswincomputing.com>
> > > > > >
> > > > > > Add driver for the Eswin EIC7700 PCIe host controller, which is based on
> > > > > > the DesignWare PCIe core, IP revision 5.96a. The PCIe Gen.3 controller
> > > > > > supports a data rate of 8 GT/s and 4 channels, support INTx and MSI
> > > > > > interrupts.
> > > > > >
> > > > >
> > > > > Is the driver going to work only for the PCIe RC IP in EIC7700 SoC or for the
> > > > > upcoming Eswin SoCs as well? Just curious because, we don't name drivers based
> > > > > on one SoC name, but by the vendor so that the driver (if compatible) can be
> > > > > used across other SoCs from the vendor.
> > > > >
> > > > > If it can work across other SoCs, then I can change 'eic7700' to 'eswin', where
> > > > > applicable while applying.
> > > > >
> > > >
> > > > This PCIe RC IP in EIC7700 will only be used for EIC7700 SoC. One thing for sure
> > > > is our next SoC will use a higher IP revision of the DesignWare PCIe core.
> > > > In the future, there is no doubt that the use of IP from other manufacturers may
> > > > be considered.
> > > >
> > > > Based on this, may I ask which name do you think is better, eic7700' or 'eswin'?
> > > >
> > >
> > > I'd suggest going with just 'eswin'. If the future revisions come up with
> > > non-dwc based IPs, we can name them appropriately.
> > >
> > > > I found there is a commit on drivers/pci/controller/dwc/pcie-tegra194.c
> > > > It added Tegra234 PCIe support in pcie-tegra194.c
> > > > Is this naming approach no longer recommended?
> > > >
> > >
> > > Yes, that predates my time with host controller drivers. I strongly suggest
> > > naming the drivers based on vendors or family to avoid creating an impression
> > > that the driver only supports one SoC version.
> > >
> > > Since you agreed for renaming, I took the liberty to do the change myself and
> > > applied the patches. I also added the maintainers entry. Please take a look at
> > > the commits and confirm if everything is OK:
> > > https://git.kernel.org/pub/scm/linux/kernel/git/pci/pci.git/log/?h=controller/dwc-eswin
> >
> > Hi Mani,
> >
> > Thank you very much for helping me change 'eic7700' to 'eswin'.
> >
> > I have verified that the code functions are intact. However, there are a few areas
> > that require your assistance to incorporate and make necessary modifications.
> > After the modifications, I believe you can incorporate it.
> >
>
> Done:
> https://git.kernel.org/pub/scm/linux/kernel/git/pci/pci.git/commit/?h=controller/dwc-eswin&id=cbbe59fa04b5d9f8e11138df4591653f7d2f8351
>
> I also removed PROBE_PREFER_ASYNCHRONOUS flag since there appears to be a
> possibility of a race condition with some endpoint drivers. We will add it in
> some other form later.
Okey,thanks!
I have checked the code and everything is fine. I'm looking forward to your merge.
Kind regards,
Senchuan
next prev parent reply other threads:[~2026-03-16 6:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 11:15 [PATCH v11 0/2] Add driver support for Eswin EIC7700 SoC PCIe controller zhangsenchuan
2026-02-27 11:17 ` [PATCH v11 1/2] dt-bindings: PCI: eic7700: Add Eswin PCIe host controller zhangsenchuan
2026-02-27 11:18 ` [PATCH v11 2/2] PCI: eic7700: Add Eswin PCIe host controller driver zhangsenchuan
2026-02-27 17:15 ` Bjorn Helgaas
2026-02-28 7:53 ` zhangsenchuan
2026-02-28 15:06 ` Manivannan Sadhasivam
2026-03-05 6:07 ` Manivannan Sadhasivam
2026-03-05 8:01 ` Min Lin
2026-03-11 6:14 ` Manivannan Sadhasivam
2026-03-11 10:35 ` zhangsenchuan
2026-03-13 13:55 ` Manivannan Sadhasivam
2026-03-16 6:30 ` zhangsenchuan [this message]
2026-03-11 6:12 ` [PATCH v11 0/2] Add driver support for Eswin EIC7700 SoC PCIe controller Manivannan Sadhasivam
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=6474f691.43fe.19cf5570586.Coremail.zhangsenchuan@eswincomputing.com \
--to=zhangsenchuan@eswincomputing.com \
--cc=Frank.li@nxp.com \
--cc=bhelgaas@google.com \
--cc=christian.bruel@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=inochiama@gmail.com \
--cc=krishna.chundru@oss.qualcomm.com \
--cc=krzk+dt@kernel.org \
--cc=kwilczynski@kernel.org \
--cc=linmin@eswincomputing.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=ningyu@eswincomputing.com \
--cc=ouyanghui@eswincomputing.com \
--cc=p.zabel@pengutronix.de \
--cc=pinkesh.vaghela@einfochips.com \
--cc=robh@kernel.org \
--cc=shradha.t@samsung.com \
--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