From: Bjorn Helgaas <helgaas@kernel.org>
To: Christian Bruel <christian.bruel@foss.st.com>
Cc: lpieralisi@kernel.org, kw@linux.com,
manivannan.sadhasivam@linaro.org, robh@kernel.org,
bhelgaas@google.com, krzk+dt@kernel.org, conor+dt@kernel.org,
mcoquelin.stm32@gmail.com, alexandre.torgue@foss.st.com,
p.zabel@pengutronix.de, cassel@kernel.org,
quic_schintav@quicinc.com, fabrice.gasnier@foss.st.com,
linux-pci@vger.kernel.org, devicetree@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/5] dt-bindings: PCI: Add STM32MP25 PCIe root complex bindings
Date: Tue, 12 Nov 2024 12:28:09 -0600 [thread overview]
Message-ID: <20241112182809.GA1853254@bhelgaas> (raw)
In-Reply-To: <20241112161925.999196-2-christian.bruel@foss.st.com>
On Tue, Nov 12, 2024 at 05:19:21PM +0100, Christian Bruel wrote:
> Document the bindings for STM32MP25 PCIe Controller configured in
> root complex mode.
> Supports 4 legacy interrupts and MSI interrupts from the ARM
> GICv2m controller.
>
> Allow tuning to change payload (default 128B) thanks to the
> st,max-payload-size entry.
> Can also limit the Maximum Read Request Size on downstream devices to the
> minimum possible value between 128B and 256B.
>
> STM32 PCIE may be in a power domain which is the case for the STM32MP25
> based boards.
> Supports wake# from wake-gpios
> + st,limit-mrrs:
> + description: If present limit downstream MRRS to 256B
> + type: boolean
> +
> + st,max-payload-size:
> + description: Maximum Payload size to use
> + $ref: /schemas/types.yaml#/definitions/uint32
> + enum: [128, 256]
> + default: 128
MRRS and MPS are not specific to this device. Not sure why you need
them, but if you do need them, I think they should be generic.
next prev parent reply other threads:[~2024-11-12 18:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-12 16:19 [PATCH 0/5] Add STM32MP25 PCIe drivers Christian Bruel
2024-11-12 16:19 ` [PATCH 1/5] dt-bindings: PCI: Add STM32MP25 PCIe root complex bindings Christian Bruel
2024-11-12 18:28 ` Bjorn Helgaas [this message]
2024-11-15 8:27 ` Christian Bruel
2024-11-15 16:36 ` Rob Herring
2024-11-25 15:23 ` Christian Bruel
2024-11-12 16:19 ` [PATCH 2/5] PCI: stm32: Add PCIe host support for STM32MP25 Christian Bruel
2024-11-12 19:32 ` Bjorn Helgaas
2024-11-25 15:00 ` Christian Bruel
2024-11-12 16:19 ` [PATCH 3/5] dt-bindings: PCI: Add STM32MP25 PCIe endpoint bindings Christian Bruel
2024-11-15 16:39 ` Rob Herring
2024-11-12 16:19 ` [PATCH 4/5] PCI: stm32: Add PCIe endpoint support for STM32MP25 Christian Bruel
2024-11-12 20:38 ` Bjorn Helgaas
2024-11-25 15:28 ` Christian Bruel
2024-11-12 16:19 ` [PATCH 5/5] MAINTAINERS: add entry for ST STM32MP25 PCIe drivers Christian Bruel
2024-11-12 20:39 ` Bjorn Helgaas
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=20241112182809.GA1853254@bhelgaas \
--to=helgaas@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=bhelgaas@google.com \
--cc=cassel@kernel.org \
--cc=christian.bruel@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=fabrice.gasnier@foss.st.com \
--cc=krzk+dt@kernel.org \
--cc=kw@linux.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=lpieralisi@kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=mcoquelin.stm32@gmail.com \
--cc=p.zabel@pengutronix.de \
--cc=quic_schintav@quicinc.com \
--cc=robh@kernel.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