From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: Mrinmay Sarkar <quic_msarkar@quicinc.com>,
andersson@kernel.org, krzysztof.kozlowski+dt@linaro.org,
conor+dt@kernel.org, manivannan.sadhasivam@linaro.org
Cc: quic_shazhuss@quicinc.com, quic_nitegupt@quicinc.com,
quic_ramkri@quicinc.com, quic_nayiluri@quicinc.com,
quic_krichai@quicinc.com, quic_vbadigan@quicinc.com,
quic_schintav@quicinc.com, "Bjorn Helgaas" <bhelgaas@google.com>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Rob Herring" <robh@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-pci@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v10 2/3] PCI: qcom-ep: Add support for SA8775P SOC
Date: Tue, 23 Apr 2024 15:08:06 +0200 [thread overview]
Message-ID: <8cdcfa2f-7a8f-4f63-b919-df0afde7d9de@linaro.org> (raw)
In-Reply-To: <1711725718-6362-3-git-send-email-quic_msarkar@quicinc.com>
On 3/29/24 16:21, Mrinmay Sarkar wrote:
> Add support for SA8775P SoC to the Qualcomm PCIe Endpoint Controller
> driver. Adding new compatible string as it has different set of clocks
> compared to other SoCs.
So is it the only change after all? What did we conclude on the NO_SNOOP
saga?
If the difference is only in the consumed clocks (and they're only supposed
to be "on" with no special handling), I don't think a separate compatible
is necessary at all
Konrad
next prev parent reply other threads:[~2024-04-23 13:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-29 15:21 [PATCH v10 0/3] arm64: qcom: sa8775p: add support for EP PCIe Mrinmay Sarkar
2024-03-29 15:21 ` [PATCH v10 1/3] dt-bindings: PCI: qcom-ep: Add support for SA8775P SoC Mrinmay Sarkar
2024-03-29 15:21 ` [PATCH v10 2/3] PCI: qcom-ep: Add support for SA8775P SOC Mrinmay Sarkar
2024-04-23 13:08 ` Konrad Dybcio [this message]
2024-04-23 13:30 ` Mrinmay Sarkar
2024-03-29 15:21 ` [PATCH v10 3/3] arm64: dts: qcom: sa8775p: Add ep pcie0 controller node 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=8cdcfa2f-7a8f-4f63-b919-df0afde7d9de@linaro.org \
--to=konrad.dybcio@linaro.org \
--cc=andersson@kernel.org \
--cc=bhelgaas@google.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.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_krichai@quicinc.com \
--cc=quic_msarkar@quicinc.com \
--cc=quic_nayiluri@quicinc.com \
--cc=quic_nitegupt@quicinc.com \
--cc=quic_ramkri@quicinc.com \
--cc=quic_schintav@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®