From: Marek Vasut <marek.vasut@mailbox.org>
To: Manivannan Sadhasivam <mani@kernel.org>
Cc: linux-pci@vger.kernel.org, stable@vger.kernel.org,
"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Geert Uytterhoeven" <geert+renesas@glider.be>,
"Koichiro Den" <den@valinux.co.jp>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Magnus Damm" <magnus.damm@gmail.com>,
"Rob Herring" <robh@kernel.org>,
"Yoshihiro Shimoda" <yoshihiro.shimoda.uh@renesas.com>,
linux-kernel@vger.kernel.org, linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH] PCI: rcar-gen4: Limit Max_Read_Request_Size and Max_Payload_Size to 256 Bytes
Date: Wed, 13 May 2026 00:57:18 +0200 [thread overview]
Message-ID: <e7078be5-4d95-4b85-9590-d1f0c76b653a@mailbox.org> (raw)
In-Reply-To: <dicudl6knlptqnscyqkedp5zrs4vyosjggysnqsaupxi3g3o4x@rngp35usnurb>
On 5/11/26 4:34 PM, Manivannan Sadhasivam wrote:
Hello Manivannan,
>> drivers/pci/controller/dwc/pcie-rcar-gen4.c | 56 +++++++++++++++++++++
>> 1 file changed, 56 insertions(+)
>>
>> diff --git a/drivers/pci/controller/dwc/pcie-rcar-gen4.c b/drivers/pci/controller/dwc/pcie-rcar-gen4.c
>> index 8b03c42f8c84c..82f0a074a71da 100644
>> --- a/drivers/pci/controller/dwc/pcie-rcar-gen4.c
>> +++ b/drivers/pci/controller/dwc/pcie-rcar-gen4.c
>> @@ -576,6 +576,7 @@ static int r8a779f0_pcie_ltssm_control(struct rcar_gen4_pcie *rcar, bool enable)
>> static void rcar_gen4_pcie_additional_common_init(struct rcar_gen4_pcie *rcar)
>> {
>> struct dw_pcie *dw = &rcar->dw;
>> + u16 offset = dw_pcie_find_capability(dw, PCI_CAP_ID_EXP);
>> u32 val;
>>
>> val = dw_pcie_readl_dbi(dw, PCIE_PORT_LANE_SKEW);
>> @@ -584,11 +585,66 @@ static void rcar_gen4_pcie_additional_common_init(struct rcar_gen4_pcie *rcar)
>> val |= BIT(6);
>> dw_pcie_writel_dbi(dw, PCIE_PORT_LANE_SKEW, val);
>>
>> + val = dw_pcie_readl_dbi(dw, offset + PCI_EXP_DEVCTL);
>> + val &= ~(PCI_EXP_DEVCTL_PAYLOAD | PCI_EXP_DEVCTL_READRQ);
>> + val |= PCI_EXP_DEVCTL_PAYLOAD_256B | PCI_EXP_DEVCTL_READRQ_256B;
>> + dw_pcie_writel_dbi(dw, offset + PCI_EXP_DEVCTL, val);
>
> Instead of limiting the MRRS/MPS values for all devices through quirks, why
> can't you just limit the Root Port's MPSS value in PCI_EXP_DEVCAP?
The root port MPSS is already 3'b001 = 256 Bytes and is read-only for
EXPCAP1F0 (PCI_EXP_DEVCAP) .
The controller is limited to MPS 256 Bytes according to V4H rev.1.30
documentation. There is no explicitly spelled out MRRS limitation in the
documentation to my knowledge, except for the DMA hint, but please read on.
The root port EXPCAP2F0 MPS is 128 Bytes and MRRS is 512 Bytes .
I now noticed that in V4H rev.1.30 documentation, the EXPCAP2F0 MRRS
field is default set to 3'b010 = 512 Bytes, but that value is "Reserved"
and only two non-reserved values are 3'b000 and 3'b001 which are MRRS
128 Bytes and 256 Bytes respectively. That means MRRS has to be trimmed
to maximum 256 Bytes in software to avoid "Reserved" settings. I will
also ask the hardware and documentation team about this.
As a result, I adjust EXPCAP2F0:
- I raise MPS from 128 Bytes to 256 Bytes
- I reduce MRRS from 512 Bytes to 256 Bytes (this is important to
prevent data corruption)
However, the downstream devices (in my case, PCIe SSD) can still be
configured with MRRS > 256 (in my case, Crucial P5 Plus 1 TiB has
MRRS=512 and MPS=128), which is where the quirk kicks in and
reconfigures MRRS for those downstream devices.
The pci_configure_mps() does propagate MPS from root port EXPCAP2F0 to
downstream devices, but there is no equivalent for MRRS as far as I can
find ?
Thank you for your help!
next prev parent reply other threads:[~2026-05-12 22:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-25 23:38 [PATCH] PCI: rcar-gen4: Limit Max_Read_Request_Size and Max_Payload_Size to 256 Bytes Marek Vasut
2026-04-28 7:00 ` Koichiro Den
2026-05-03 23:54 ` Marek Vasut
2026-05-11 14:20 ` Koichiro Den
2026-05-13 3:01 ` Marek Vasut
2026-05-11 14:34 ` Manivannan Sadhasivam
2026-05-12 22:57 ` Marek Vasut [this message]
2026-05-12 23:08 ` Marek Vasut
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=e7078be5-4d95-4b85-9590-d1f0c76b653a@mailbox.org \
--to=marek.vasut@mailbox.org \
--cc=bhelgaas@google.com \
--cc=den@valinux.co.jp \
--cc=geert+renesas@glider.be \
--cc=kwilczynski@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mani@kernel.org \
--cc=robh@kernel.org \
--cc=stable@vger.kernel.org \
--cc=yoshihiro.shimoda.uh@renesas.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