From: Krzysztof Kozlowski <krzk@kernel.org>
To: Mrinmay Sarkar <mrinmay.sarkar@oss.qualcomm.com>
Cc: "Bjorn Helgaas" <bhelgaas@google.com>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
"Manivannan Sadhasivam" <mani@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Philipp Zabel" <p.zabel@pengutronix.de>,
linux-arm-msm@vger.kernel.org, linux-pci@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel@oss.qualcomm.com,
"Manivannan Sadhasivam" <manivannan.sadhasivam@oss.qualcomm.com>,
"Krishna Chaitanya Chundru" <krishna.chundru@oss.qualcomm.com>,
quic_vbadigan@quicinc.com, quic_shazhuss@quicinc.com,
konrad.dybcio@oss.qualcomm.com,
"Rama Krishna" <quic_ramkri@quicinc.com>,
"Ayiluri Naga Rashmi" <quic_nayiluri@quicinc.com>,
"Nitesh Gupta" <quic_nitegupt@quicinc.com>
Subject: Re: [PATCH 1/2] dt-bindings: PCI: qcom,pcie-ep-sa8255p: Document firmware managed PCIe endpoint
Date: Fri, 5 Dec 2025 14:14:37 +0100 [thread overview]
Message-ID: <8bb852ac-1736-49db-be94-f6be9e500f74@kernel.org> (raw)
In-Reply-To: <CAMyL0qO2FPBe7N6Q=hW-ymeiGDhABsU+VCj25jzcoQRhBoWbDA@mail.gmail.com>
On 05/12/2025 13:58, Mrinmay Sarkar wrote:
>>> 1 file changed, 114 insertions(+)
>>>
>>> diff --git a/Documentation/devicetree/bindings/pci/qcom,pcie-ep-sa8255p.yaml b/Documentation/devicetree/bindings/pci/qcom,pcie-ep-sa8255p.yaml
>>> new file mode 100644
>>> index 0000000000000000000000000000000000000000..970f65d46c8e2fa4c44665cb7a346dea1dc9e06a
>>> --- /dev/null
>>> +++ b/Documentation/devicetree/bindings/pci/qcom,pcie-ep-sa8255p.yaml
>>> @@ -0,0 +1,114 @@
>>> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
>>> +%YAML 1.2
>>> +---
>>> +$id: http://devicetree.org/schemas/pci/qcom,pcie-ep-sa8255p.yaml#
>>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>>> +
>>> +title: Qualcomm firmware managed PCIe Endpoint Controller
>>> +
>>> +description:
>>> + Qualcomm SA8255p SoC PCIe endpoint controller is based on the Synopsys
>>> + DesignWare PCIe IP which is managed by firmware.
>>> +
>>> +maintainers:
>>> + - Manivannan Sadhasivam <mani@kernel.org>
>>> +
>>> +properties:
>>> + compatible:
>>> + const: qcom,sa8255p-pcie-ep
>>> +
>>> + reg:
>>> + minItems: 6
>>
>> Why is this flexible?
>
> The reason for `minItems: 6` is that the DMA register space can be
> skipped if DMA is not used.
But the hardware has this anyway, so this must be here. You do not write
bindings depending how drivers use them in your use case.
Either drop minItems (fixed size of array) or provide rationale in terms
of hardware in commit msg.
...
>>> +
>>> + dma-coherent: true
>>> +
>>> + num-lanes:
>>> + default: 2
>>
>> Isn't this deducible from the compatible? Do you have have different
>> PCIe controllers with different lanes?
>
> SA8255p has 2 pcie controllers(pcie0 and pcie1).
> pcie0 supports 2 lanes, and pcie1 supports 4 lanes.
That's ok, thanks.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-12-05 13:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-03 13:26 [PATCH 0/2] Add firmware-managed PCIe Endpoint support for SA8255P Mrinmay Sarkar
2025-12-03 13:26 ` [PATCH 1/2] dt-bindings: PCI: qcom,pcie-ep-sa8255p: Document firmware managed PCIe endpoint Mrinmay Sarkar
2025-12-05 9:10 ` Krzysztof Kozlowski
2025-12-05 12:58 ` Mrinmay Sarkar
2025-12-05 13:14 ` Krzysztof Kozlowski [this message]
2025-12-05 13:48 ` Mrinmay Sarkar
2025-12-03 13:26 ` [PATCH 2/2] PCI: qcom-ep: Add support for firmware-managed PCIe Endpoint Mrinmay Sarkar
2025-12-05 15:08 ` Jeff Johnson
2025-12-05 21:03 ` Bjorn Andersson
2025-12-09 12:26 ` Mrinmay Sarkar
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=8bb852ac-1736-49db-be94-f6be9e500f74@kernel.org \
--to=krzk@kernel.org \
--cc=bhelgaas@google.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@oss.qualcomm.com \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=krishna.chundru@oss.qualcomm.com \
--cc=krzk+dt@kernel.org \
--cc=kwilczynski@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=manivannan.sadhasivam@oss.qualcomm.com \
--cc=mrinmay.sarkar@oss.qualcomm.com \
--cc=p.zabel@pengutronix.de \
--cc=quic_nayiluri@quicinc.com \
--cc=quic_nitegupt@quicinc.com \
--cc=quic_ramkri@quicinc.com \
--cc=quic_shazhuss@quicinc.com \
--cc=quic_vbadigan@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
all inboxes | Powered by JetHome®