From: Bjorn Helgaas <helgaas@kernel.org>
To: Tengfei Fan <quic_tengfan@quicinc.com>
Cc: "Manivannan Sadhasivam" <manivannan.sadhasivam@linaro.org>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Rob Herring" <robh@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
kernel@quicinc.com, linux-pci@vger.kernel.org,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: PCI: qcom-ep: Add support for QCS9100 SoC
Date: Tue, 9 Jul 2024 11:28:31 -0500 [thread overview]
Message-ID: <20240709162831.GA176079@bhelgaas> (raw)
In-Reply-To: <20240709-add_qcs9100_pcie_ep_compatible-v2-1-217742eac32b@quicinc.com>
On Tue, Jul 09, 2024 at 10:53:43PM +0800, Tengfei Fan wrote:
> Add devicetree bindings support for QCS9100 SoC. It has DMA register
> space and dma interrupt to support HDMA.
s/dma/DMA/ above for consistency.
Add blank line here if this is a paragraph break.
> QCS9100 is drived from SA8775p. Currently, both the QCS9100 and SA8775p
> platform use non-SCMI resource. In the future, the SA8775p platform will
> move to use SCMI resources and it will have new sa8775p-related device
> tree. Consequently, introduce "qcom,qcs9100-pcie-ep" to describe non-SCMI
> based PCIe.
s/drived/derived/
This patch doesn't add anything related to SCMI, so this paragraph
seems like a distraction.
The first paragraph seems a bit of a distraction too, since the patch
doesn't say anything about DMA register space or interrupt.
> Signed-off-by: Tengfei Fan <quic_tengfan@quicinc.com>
> ---
> Documentation/devicetree/bindings/pci/qcom,pcie-ep.yaml | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/pci/qcom,pcie-ep.yaml b/Documentation/devicetree/bindings/pci/qcom,pcie-ep.yaml
> index 46802f7d9482..8012663e7efc 100644
> --- a/Documentation/devicetree/bindings/pci/qcom,pcie-ep.yaml
> +++ b/Documentation/devicetree/bindings/pci/qcom,pcie-ep.yaml
> @@ -13,6 +13,7 @@ properties:
> compatible:
> oneOf:
> - enum:
> + - qcom,qcs9100-pcie-ep
> - qcom,sa8775p-pcie-ep
> - qcom,sdx55-pcie-ep
> - qcom,sm8450-pcie-ep
> @@ -203,6 +204,7 @@ allOf:
> compatible:
> contains:
> enum:
> + - qcom,qcs9100-pcie-ep
> - qcom,sa8775p-pcie-ep
> then:
> properties:
>
> --
> 2.25.1
>
next prev parent reply other threads:[~2024-07-09 16:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-09 14:53 [PATCH v2 0/2] PCI: qcom-ep: Add QCS9100 PCIe ep compatible Tengfei Fan
2024-07-09 14:53 ` [PATCH v2 1/2] dt-bindings: PCI: qcom-ep: Add support for QCS9100 SoC Tengfei Fan
2024-07-09 16:28 ` Bjorn Helgaas [this message]
2024-07-10 7:09 ` Tengfei Fan
2024-07-10 10:31 ` Aiqun Yu (Maria)
2024-07-29 10:08 ` Tengfei Fan
2024-07-09 14:53 ` [PATCH v2 2/2] PCI: qcom-ep: Add HDMA " Tengfei Fan
2024-07-09 16:26 ` Bjorn Helgaas
2024-07-10 7:18 ` Tengfei Fan
2024-07-10 10:40 ` Aiqun Yu (Maria)
2024-07-29 10:08 ` Tengfei Fan
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=20240709162831.GA176079@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@quicinc.com \
--cc=krzk+dt@kernel.org \
--cc=kw@linux.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=quic_tengfan@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