From: Niklas Cassel <cassel@kernel.org>
To: Vincent Guittot <vincent.guittot@linaro.org>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
chester62515@gmail.com, mbrugger@suse.com,
ghennadi.procopciuc@oss.nxp.com, s32@nxp.com,
bhelgaas@google.com, jingoohan1@gmail.com, lpieralisi@kernel.org,
kwilczynski@kernel.org, mani@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, Ionut.Vicovan@nxp.com,
larisa.grigore@nxp.com, Ghennadi.Procopciuc@nxp.com,
ciprianmarian.costea@nxp.com, bogdan.hamciuc@nxp.com,
Frank.li@nxp.com, linux-arm-kernel@lists.infradead.org,
linux-pci@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, imx@lists.linux.dev
Subject: Re: [PATCH 3/4 v3] PCI: s32g: Add initial PCIe support (RC)
Date: Wed, 5 Nov 2025 11:28:04 +0100 [thread overview]
Message-ID: <aQsmtKsTEmf7e7Sd@ryzen> (raw)
In-Reply-To: <CAKfTPtCtHquxtK=Zx2WSNm15MmqeUXO8XXi8FkS4EpuP80PP7g@mail.gmail.com>
On Fri, Oct 24, 2025 at 08:50:46AM +0200, Vincent Guittot wrote:
> On Wed, 22 Oct 2025 at 21:04, Bjorn Helgaas <helgaas@kernel.org> wrote:
> > > + dw_pcie_dbi_ro_wr_en(pci);
> > > +
> > > + val = dw_pcie_readl_dbi(pci, PCIE_PORT_FORCE);
> > > + val |= PORT_FORCE_DO_DESKEW_FOR_SRIS;
> > > + dw_pcie_writel_dbi(pci, PCIE_PORT_FORCE, val);
> > > +
> > > + /*
> > > + * Set max payload supported, 256 bytes and
> > > + * relaxed ordering.
> > > + */
> > > + val = dw_pcie_readl_dbi(pci, offset + PCI_EXP_DEVCTL);
> > > + val &= ~(PCI_EXP_DEVCTL_RELAX_EN |
> > > + PCI_EXP_DEVCTL_PAYLOAD |
> > > + PCI_EXP_DEVCTL_READRQ);
> > > + val |= PCI_EXP_DEVCTL_RELAX_EN |
> > > + PCI_EXP_DEVCTL_PAYLOAD_256B |
> > > + PCI_EXP_DEVCTL_READRQ_256B;
> > > + dw_pcie_writel_dbi(pci, offset + PCI_EXP_DEVCTL, val);
> >
> > MPS and relaxed ordering should be configured by the PCI core. Is
> > there some s32g-specific restriction about these?
>
> I will check with the team why they did that
Most likely, the reason is that, the PCI core does not set the MPS to the
maximum supported MPS for the root port.
So without that change, the port will use use 128B instead of 256B.
I assume that you should be able to drop (at least the MPS part) if this
change gets accepted:
https://lore.kernel.org/linux-pci/20251104165125.174168-1-18255117159@163.com/
Kind regards,
Niklas
next prev parent reply other threads:[~2025-11-05 10:28 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-22 17:43 [PATCH 0/4 v3] PCI: s32g: Add support for PCIe controller Vincent Guittot
2025-10-22 17:43 ` [PATCH 1/4 v3] dt-bindings: PCI: s32g: Add NXP " Vincent Guittot
2025-10-22 19:17 ` Frank Li
2025-10-24 6:58 ` Vincent Guittot
2025-11-06 0:00 ` Bjorn Helgaas
2025-11-06 7:51 ` Vincent Guittot
2025-11-06 7:12 ` Manivannan Sadhasivam
2025-11-06 8:09 ` Vincent Guittot
2025-11-06 17:38 ` Bjorn Helgaas
2025-11-10 9:14 ` Vincent Guittot
2025-10-22 17:43 ` [PATCH 2/4 v3] PCI: dw: Add more registers and bitfield definition Vincent Guittot
2025-10-22 17:43 ` [PATCH 3/4 v3] PCI: s32g: Add initial PCIe support (RC) Vincent Guittot
2025-10-22 19:04 ` Bjorn Helgaas
2025-10-24 6:50 ` Vincent Guittot
2025-11-05 10:28 ` Niklas Cassel [this message]
2025-11-05 10:43 ` Ilpo Järvinen
2025-11-05 11:00 ` Niklas Cassel
2025-11-06 0:05 ` Bjorn Helgaas
2025-11-06 6:24 ` Manivannan Sadhasivam
2025-11-06 7:50 ` Vincent Guittot
2025-11-14 10:05 ` Christian Bruel
2025-11-14 21:35 ` Bjorn Helgaas
2025-11-06 7:46 ` Vincent Guittot
2025-10-22 19:44 ` Frank Li
2025-10-24 6:53 ` Vincent Guittot
2025-11-05 7:58 ` Vincent Guittot
2025-11-06 17:23 ` Bjorn Helgaas
2025-11-06 17:33 ` Vincent Guittot
2025-10-22 17:43 ` [PATCH 4/4 v3] MAINTAINERS: Add MAINTAINER for NXP S32G PCIe driver Vincent Guittot
2025-10-22 19:20 ` Frank Li
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=aQsmtKsTEmf7e7Sd@ryzen \
--to=cassel@kernel.org \
--cc=Frank.li@nxp.com \
--cc=Ghennadi.Procopciuc@nxp.com \
--cc=Ionut.Vicovan@nxp.com \
--cc=bhelgaas@google.com \
--cc=bogdan.hamciuc@nxp.com \
--cc=chester62515@gmail.com \
--cc=ciprianmarian.costea@nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=ghennadi.procopciuc@oss.nxp.com \
--cc=helgaas@kernel.org \
--cc=imx@lists.linux.dev \
--cc=jingoohan1@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=kwilczynski@kernel.org \
--cc=larisa.grigore@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=mbrugger@suse.com \
--cc=robh@kernel.org \
--cc=s32@nxp.com \
--cc=vincent.guittot@linaro.org \
/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).