mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: George Moussalem <george.moussalem@outlook.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-pci@vger.kernel.org, linux-phy@lists.infradead.org,
	andersson@kernel.org, bhelgaas@google.com, conor+dt@kernel.org,
	devicetree@vger.kernel.org, lumag@kernel.org, kishon@kernel.org,
	konradybcio@kernel.org, krzk+dt@kernel.org, kw@linux.com,
	lpieralisi@kernel.org, manivannan.sadhasivam@linaro.org,
	p.zabel@pengutronix.de, quic_nsekar@quicinc.com, robh@kernel.org,
	robimarko@gmail.com, vkoul@kernel.org, quic_srichara@quicinc.com
Subject: Re: [PATCH v4 3/6] dt-bindings: PCI: qcom: Add IPQ5018 SoC
Date: Mon, 17 Mar 2025 09:49:08 +0400	[thread overview]
Message-ID: <DS7PR19MB8883AB849DC21D7C43DDA78A9DDF2@DS7PR19MB8883.namprd19.prod.outlook.com> (raw)
In-Reply-To: <6843e66c-d85c-4af0-8b49-773803825381@kernel.org>



On 3/14/25 13:20, Krzysztof Kozlowski wrote:
> On 14/03/2025 09:42, George Moussalem wrote:
>>>> +        reg-names:
>>>> +          items:
>>>> +            - const: parf # Qualcomm specific registers
>>>> +            - const: dbi # DesignWare PCIe registers
>>>> +            - const: elbi # External local bus interface registers
>>>> +            - const: atu # ATU address space
>>>> +            - const: config # PCIe configuration space
>>>
>>> Keep the same order as other IPQ, so dbi+elbi+atu+parf+config. Same for
>>> everything else, so standard rule applies: devices are supposed to use
>>> ordering from existing variants.
>>>
>>> There is some huge mess with IPQ PCI bindings, including things on the
>>> list. Apparently it became my job to oversee Qualcomm PCI work... well,
>>> I do not have time for that, so rather I expect contributors to
>>> cooperate in this matter.
>>>
>>> Don't throw your patches over the wall.
>>>
>>> If you need to rework the patch, take the ownership and rework it.
>>>
>>>
>>
>> Thanks Krzysztof. I did reorder them deliberately based on unit
>> addresses as discussed also in other threads about IPQ9574 and IPQ5332
>> as I thought it would be neater that way. I'll change it back, reuse
> 
> Which discusses were that? What were the reasons to start with parf?
> 

I based the reordering on this patch so assumed that was the direction 
(at that time):
https://patchwork.kernel.org/project/linux-pci/patch/20250128062708.573662-5-quic_varada@quicinc.com/

This was then reverted in subsequent version so will reorder as suggested.

> 
>> other sections in the dt as much as possible, and follow your guidance
>> instead.
> 
> Best regards,
> Krzysztof

Best regards,
George

  reply	other threads:[~2025-03-17  5:49 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-14  5:55 [PATCH v4 0/6] Enable IPQ5018 PCI support George Moussalem
2025-03-14  5:56 ` [PATCH v4 1/6] dt-bindings: phy: qcom: uniphy-pcie: Add ipq5018 compatible George Moussalem
2025-03-14  8:15   ` Krzysztof Kozlowski
     [not found] ` <20250314055644.32705-1-george.moussalem@outlook.com>
2025-03-14  5:56   ` [PATCH v4 2/6] phy: qualcomm: qcom-uniphy-pcie 28LP add support for IPQ5018 George Moussalem
2025-03-14  5:56   ` [PATCH v4 3/6] dt-bindings: PCI: qcom: Add IPQ5018 SoC George Moussalem
2025-03-14  8:20     ` Krzysztof Kozlowski
2025-03-14  8:42       ` George Moussalem
2025-03-14  9:20         ` Krzysztof Kozlowski
2025-03-17  5:49           ` George Moussalem [this message]
2025-03-17  7:28             ` Krzysztof Kozlowski
2025-03-14  5:56   ` [PATCH v4 4/6] PCI: qcom: Add support for IPQ5018 George Moussalem
2025-03-14  5:56   ` [PATCH v4 5/6] arm64: dts: qcom: ipq5018: Add PCIe related nodes George Moussalem
2025-03-14  8:23     ` Krzysztof Kozlowski
2025-03-14  8:50       ` George Moussalem
2025-03-14 12:10         ` Krzysztof Kozlowski
2025-03-14  5:56   ` [PATCH v4 6/6] arm64: dts: qcom: ipq5018: Enable PCIe George Moussalem

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=DS7PR19MB8883AB849DC21D7C43DDA78A9DDF2@DS7PR19MB8883.namprd19.prod.outlook.com \
    --to=george.moussalem@outlook.com \
    --cc=andersson@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kishon@kernel.org \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@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=linux-phy@lists.infradead.org \
    --cc=lpieralisi@kernel.org \
    --cc=lumag@kernel.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=p.zabel@pengutronix.de \
    --cc=quic_nsekar@quicinc.com \
    --cc=quic_srichara@quicinc.com \
    --cc=robh@kernel.org \
    --cc=robimarko@gmail.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®