Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Chen Wang <unicorn_wang@outlook.com>
Cc: Inochi Amaoto <inochiama@gmail.com>,
	Bjorn Helgaas <bhelgaas@google.com>,
	Han Gao <rabenda.cn@gmail.com>,
	Manivannan Sadhasivam <mani@kernel.org>,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
	Yixun Lan <dlan@gentoo.org>, Longbin Li <looong.bin@gmail.com>
Subject: Re: [PATCH 0/2] PCI/ASPM: Avoid L0s and L1 on Sophgo 2042/2044 PCIe Root Ports
Date: Mon, 29 Dec 2025 09:11:52 -0600	[thread overview]
Message-ID: <20251229151152.GA57954@bhelgaas> (raw)
In-Reply-To: <MA5PR01MB1250074A97978ACB5C88D1363FEBFA@MA5PR01MB12500.INDPRD01.PROD.OUTLOOK.COM>

On Mon, Dec 29, 2025 at 08:17:40AM +0800, Chen Wang wrote:
> On 12/27/2025 12:30 AM, Bjorn Helgaas wrote:
> > On Thu, Dec 25, 2025 at 06:05:27PM +0800, Inochi Amaoto wrote:
> > > Since commit f3ac2ff14834 ("PCI/ASPM: Enable all ClockPM and ASPM
> > > states for devicetree platforms") force enable ASPM on all device tree
> > > platform, the SG2042/SG2044 PCIe Root Ports breaks as it advertises L0s
> > > and L1 capabilities without supporting it.
> > > 
> > > Override the L0s and L1 Support advertised in Link Capabilities by the
> > > SG2042/SG2044 Root Ports so we don't try to enable those states.
> > > 
> > > Inochi Amaoto (2):
> > >    PCI/ASPM: Avoid L0s and L1 on Sophgo 2042 PCIe [1f1c:2042] Root Ports
> > >    PCI/ASPM: Avoid L0s and L1 on Sophgo 2044 PCIe [1f1c:2044] Root Ports
> > > 
> > >   drivers/pci/quirks.c    | 2 ++
> > >   include/linux/pci_ids.h | 2 ++
> > >   2 files changed, 4 insertions(+)
> ...

> > 2) Why don't we have a MAINTAINERS entry for this driver?  I failed to
> > notice that the series we applied
> > (https://lore.kernel.org/all/cover.1757643388.git.unicorn_wang@outlook.com/)
> > does not include a maintainer.  Chen, since you posted that series,
> > are you willing to sign up to maintain it?
>
> Sorry, I didn't realize I needed to submit maintainer information
> separately for each driver when I submitted the PCIe driver code.
> 
> Yes, I will be maintaining the SG2042 PCIe driver. Do I need to add
> an entry to the MAINTAINERS file?

Yes, please.

  $ ./scripts/get_maintainer.pl drivers/pci/controller/cadence/pcie-sg2042.c
  Lorenzo Pieralisi <lpieralisi@kernel.org> (maintainer:PCI NATIVE HOST BRIDGE AND ENDPOINT DRIVERS)
  "Krzysztof Wilczyński" <kwilczynski@kernel.org> (maintainer:PCI NATIVE HOST BRIDGE AND ENDPOINT DRIVERS)
  Manivannan Sadhasivam <mani@kernel.org> (maintainer:PCI NATIVE HOST BRIDGE AND ENDPOINT DRIVERS,commit_signer:2/2=100%)
  ...
  Chen Wang <unicorn_wang@outlook.com> (commit_signer:2/2=100%,authored:1/2=50%,added_lines:134/134=100%)

This does list you, but only as a commit signer.  It should list you
as a maintainer of the driver so people know to send patches to you
(and cc linux-pci, of course).

Bjorn

  reply	other threads:[~2025-12-29 15:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-25 10:05 [PATCH 0/2] PCI/ASPM: Avoid L0s and L1 on Sophgo 2042/2044 PCIe Root Ports Inochi Amaoto
2025-12-25 10:05 ` [PATCH 1/2] PCI/ASPM: Avoid L0s and L1 on Sophgo 2042 PCIe [1f1c:2042] " Inochi Amaoto
2025-12-26  1:24   ` Chen Wang
2025-12-25 10:05 ` [PATCH 2/2] PCI/ASPM: Avoid L0s and L1 on Sophgo 2044 PCIe [1f1c:2044] " Inochi Amaoto
2025-12-26 16:30 ` [PATCH 0/2] PCI/ASPM: Avoid L0s and L1 on Sophgo 2042/2044 PCIe " Bjorn Helgaas
2025-12-29  0:17   ` Chen Wang
2025-12-29 15:11     ` Bjorn Helgaas [this message]
2025-12-30  9:45   ` Inochi Amaoto
2025-12-30 10:08     ` Manivannan Sadhasivam
2025-12-30 11:08       ` Inochi Amaoto

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=20251229151152.GA57954@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=dlan@gentoo.org \
    --cc=inochiama@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=looong.bin@gmail.com \
    --cc=mani@kernel.org \
    --cc=rabenda.cn@gmail.com \
    --cc=unicorn_wang@outlook.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