mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Sushrut Shree Trivedi <sushrut.trivedi@oss.qualcomm.com>
Cc: "Vinod Koul" <vkoul@kernel.org>,
	"Neil Armstrong" <neil.armstrong@linaro.org>,
	"Rob Herring" <robh@kernel.org>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
	"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
	"Manivannan Sadhasivam" <mani@kernel.org>,
	"Bjorn Andersson" <andersson@kernel.org>,
	"Chaitanya Chundru" <krishna.chundru@oss.qualcomm.com>,
	"Bartosz Golaszewski" <brgl@kernel.org>,
	"Konrad Dybcio" <konradybcio@kernel.org>,
	linux-arm-msm@vger.kernel.org, linux-phy@lists.infradead.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-pci@vger.kernel.org
Subject: Re: [PATCH v2 2/5] dt-bindings: PCI: qcom,shikra-pcie: Document the Shikra PCIe Controller
Date: Mon, 21 Sep 2026 16:21:55 +0200	[thread overview]
Message-ID: <ebca2e35-6c4f-45ed-a9de-d9b52651717d@kernel.org> (raw)
In-Reply-To: <7b5bec8a-87ed-4363-ac62-3e14f7619f13@oss.qualcomm.com>

On 21/09/2026 15:47, Sushrut Shree Trivedi wrote:
> 
> On 9/1/2026 2:12 PM, Krzysztof Kozlowski wrote:
>> On Mon, Aug 31, 2026 at 12:56:02PM +0530, Sushrut Shree Trivedi wrote:
>>> Add a dedicated schema for the PCIe controller found on the Shikra
>>> platform.
>>>
>>> Shikra controller supports upto PCIe Gen3 but the PHY is
>>> only capable of Gen2, hence the max link speed  is limited
>>> to Gen2 to avoid link-up failures.
>>>
>>> Signed-off-by: Sushrut Shree Trivedi <sushrut.trivedi@oss.qualcomm.com>
>>> ---
>>>   .../devicetree/bindings/pci/qcom,shikra-pcie.yaml  | 218 +++++++++++++++++++++
>>>   1 file changed, 218 insertions(+)
>>>
>> What is the difference in the binding against Eliza? IOW, why does this
>> need a separate file unlike Eliza?
> Shikra does not have the Config NoC AXI clock unlike sm8550 / eliza. Apart
> from that, minItems for reg  and interrupts need to be updated. I actually

Really? Did you even check? I looked at Eliza and it has 6 minItems for
reg. Your patch defines how many exactly?

I did not check the rest of the arguments because it is not a game "I
will say whatever and maintainer will need to verify each of my claims".
I find one false claim and that drops this from Patchwork.

Best regards,
Krzysztof

  reply	other threads:[~2026-09-21 14:22 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-31  7:26 [PATCH v2 0/5] PCI: qcom: Add PCIe support for Shikra SoC Sushrut Shree Trivedi
2026-08-31  7:26 ` [PATCH v2 1/5] dt-bindings: phy: sc8280xp-qmp-pcie: Document Shikra PCIe phy Sushrut Shree Trivedi
2026-09-01  8:35   ` Krzysztof Kozlowski
2026-09-10 14:53   ` Manivannan Sadhasivam
2026-09-11  7:52   ` Bartosz Golaszewski
2026-08-31  7:26 ` [PATCH v2 2/5] dt-bindings: PCI: qcom,shikra-pcie: Document the Shikra PCIe Controller Sushrut Shree Trivedi
2026-09-01  8:42   ` Krzysztof Kozlowski
2026-09-21 13:47     ` Sushrut Shree Trivedi
2026-09-21 14:21       ` Krzysztof Kozlowski [this message]
2026-08-31  7:26 ` [PATCH v2 3/5] PCI: qcom: Add support for Shikra Sushrut Shree Trivedi
2026-08-31  7:26 ` [PATCH v2 4/5] phy: qcom: qmp-pcie: Add QMP PCIe PHY " Sushrut Shree Trivedi
2026-09-10 14:54   ` Manivannan Sadhasivam
2026-09-11  7:52   ` Bartosz Golaszewski
2026-08-31  7:26 ` [PATCH v2 5/5] arm64: dts: qcom: shikra: Add PCIe PHY and controller nodes Sushrut Shree Trivedi
2026-09-02  8:46 ` [PATCH v2 0/5] PCI: qcom: Add PCIe support for Shikra SoC Konrad Dybcio
2026-09-21 13:52   ` Sushrut Shree Trivedi
2026-09-13 10:56 ` (subset) " Vinod Koul

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=ebca2e35-6c4f-45ed-a9de-d9b52651717d@kernel.org \
    --to=krzk@kernel.org \
    --cc=andersson@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=brgl@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konradybcio@kernel.org \
    --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=linux-phy@lists.infradead.org \
    --cc=lpieralisi@kernel.org \
    --cc=mani@kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=robh@kernel.org \
    --cc=sushrut.trivedi@oss.qualcomm.com \
    --cc=vkoul@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®