From: Donghui Zhao <zhaodonghui@eswincomputing.com>
To: linux-pci@vger.kernel.org, "Bjorn Helgaas" <bhelgaas@google.com>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
"Manivannan Sadhasivam" <mani@kernel.org>
Cc: Rob Herring <robh@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
zhengyu@eswincomputing.com
Subject: [RFC] PCI: dwc: eswin: proposal for a separate EGC-series driver
Date: Wed, 18 Nov 2026 18:57:17 +0800 [thread overview]
Message-ID: <20261118105717.1364-1-zhaodonghui@eswincomputing.com> (raw)
Hello PCI maintainers,
ESWIN Computing is preparing support for a new EGC series of SoCs. The
PCIe controllers in these SoCs are still based on the Synopsys DesignWare
core, but the SoC integration around the core differs considerably from
the EIC7700 controller supported by
drivers/pci/controller/dwc/pcie-eswin.c. Reusing the existing driver
would require a large amount of per-SoC conditional code, so we would
prefer to keep the new support in a separate driver.
Before posting the full series, could you confirm the preferred upstream
structure?
a) Add a new host-only driver in
drivers/pci/controller/dwc/pcie-eswin-egc.c, with a separate
CONFIG_PCIE_ESWIN_EGC Kconfig symbol and Makefile entry, while
reusing the common DesignWare host code.
b) Extend pcie-eswin.c with additional of_device_id data and per-SoC
operations, so that a single ESWIN driver covers both controller
generations.
If (a) is acceptable, is pcie-eswin-egc.c the preferred file name? The
differences from EIC7700 are at the SoC-integration level rather than in
the DesignWare core programming; a detailed list will be included in the
cover letter of the full series.
We will follow up with the driver, the DT binding and the MAINTAINERS
update as a complete series once the direction is agreed.
Thanks,
Donghui Zhao
reply other threads:[~2026-11-18 10:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20261118105717.1364-1-zhaodonghui@eswincomputing.com \
--to=zhaodonghui@eswincomputing.com \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=kwilczynski@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=robh@kernel.org \
--cc=zhengyu@eswincomputing.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