From: Mrinmay Sarkar <quic_msarkar@quicinc.com>
To: Konrad Dybcio <konrad.dybcio@linaro.org>,
Andrew Halaney <ahalaney@redhat.com>
Cc: <agross@kernel.org>, <andersson@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>, <conor+dt@kernel.org>,
<mani@kernel.org>, <robh+dt@kernel.org>,
<quic_shazhuss@quicinc.com>, <quic_nitegupt@quicinc.com>,
<quic_ramkri@quicinc.com>, <quic_nayiluri@quicinc.com>,
<dmitry.baryshkov@linaro.org>, <robh@kernel.org>,
<quic_krichai@quicinc.com>, <quic_vbadigan@quicinc.com>,
<quic_parass@quicinc.com>, <quic_schintav@quicinc.com>,
<quic_shijjose@quicinc.com>, Vinod Koul <vkoul@kernel.org>,
"Kishon Vijay Abraham I" <kishon@kernel.org>,
<linux-arm-msm@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-phy@lists.infradead.org>
Subject: Re: [PATCH v1 2/2] arm64: dts: qcom: sa8775p: Add ep pcie1 controller node
Date: Fri, 10 Nov 2023 10:33:08 +0530 [thread overview]
Message-ID: <b40a74f4-1605-d3a1-2c6a-845c41419442@quicinc.com> (raw)
In-Reply-To: <19f32f8e-dfe2-410b-9a4d-80e24a888d65@linaro.org>
On 11/8/2023 3:24 AM, Konrad Dybcio wrote:
>
>
> On 11/7/23 19:37, Andrew Halaney wrote:
>> On Tue, Nov 07, 2023 at 06:34:53PM +0530, Mrinmay Sarkar wrote:
>>> Add ep pcie dtsi node for pcie1 controller found on sa8775p platform.
>>> It supports gen4 and x4 link width. Limiting the speed to Gen3 due to
>>> stability issues.
>>
>> I wouldn't mind a bit more information on what "stability" issues
>> entails! I'm a sucker for details in a commit message.
> Yep, giving us a bit more than "doesnt work" may help us help you!
Actually if I enable gen4 some time I am getting link down and sometime
link getting establish at gen1. I am not getting stable gen4, may be we
need to program some register to get stable gen4 that I am checking.
>>> +
>>> + interrupts = <GIC_SPI 518 IRQ_TYPE_LEVEL_HIGH>,
>>> + <GIC_SPI 152 IRQ_TYPE_LEVEL_HIGH>,
>>> + <GIC_SPI 474 IRQ_TYPE_LEVEL_HIGH>;
> Looks like the indentation is off?
>
>>> +
>>> + interrupt-names = "global", "doorbell", "dma";
>>> +
>>> + interconnects = <&pcie_anoc MASTER_PCIE_1 0 &mc_virt
>>> SLAVE_EBI1 0>,
>>> + <&gem_noc MASTER_APPSS_PROC 0 &config_noc
>>> SLAVE_PCIE_1 0>;
>>
>> I keep seeing Konrad requesting that we use the #define instead of a raw
>> number 0, i.e. something like QCOM_ICC_TAG_ALWAYS (although if I'm
>> reading that correctly QCOM_ICC_TAG_ALWAYS doesn't evaluate to 0, so
>> make sure you pick the appropriate one).
> No it doesn't, but if you look at the code, tag being non-existent
> assigns QCOM_ICC_TAG_ALWAYS which is a workaround for DTBs from back
> when interconnect tags were not a thing
>
>>
>>> + interconnect-names = "pcie-mem", "cpu-pcie";
>>
>> This is nitpicky, but unless someone told you to do the whitespace
>> between some of these properties I'd get more consistent. i.e. reg and
>> reg-names has no newline between them, but clocks and clock-names does,
>> and then interconnects/interconnect-names does not.
> :)
I don't think there is any rule to add those white spaces, in next patch
I will align these white spaces with other pcie nodes.
>
> Konrad
Thanks,
Mrinmay
prev parent reply other threads:[~2023-11-10 18:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-07 13:04 [PATCH v1 0/2] arm64: qcom: sa8775p: add support for x4 EP PCIe controller Mrinmay Sarkar
2023-11-07 13:04 ` [PATCH v1 1/2] phy: qcom-qmp-pcie: add x4 lane EP support for sa8775p Mrinmay Sarkar
2023-11-07 13:10 ` Dmitry Baryshkov
2023-11-07 13:04 ` [PATCH v1 2/2] arm64: dts: qcom: sa8775p: Add ep pcie1 controller node Mrinmay Sarkar
2023-11-07 18:37 ` Andrew Halaney
2023-11-07 21:54 ` Konrad Dybcio
2023-11-10 5:03 ` Mrinmay Sarkar [this message]
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=b40a74f4-1605-d3a1-2c6a-845c41419442@quicinc.com \
--to=quic_msarkar@quicinc.com \
--cc=agross@kernel.org \
--cc=ahalaney@redhat.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=kishon@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=mani@kernel.org \
--cc=quic_krichai@quicinc.com \
--cc=quic_nayiluri@quicinc.com \
--cc=quic_nitegupt@quicinc.com \
--cc=quic_parass@quicinc.com \
--cc=quic_ramkri@quicinc.com \
--cc=quic_schintav@quicinc.com \
--cc=quic_shazhuss@quicinc.com \
--cc=quic_shijjose@quicinc.com \
--cc=quic_vbadigan@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--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®