From: Krishna Kurapati PSSNV <quic_kriskura@quicinc.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh+dt@kernel.org>, Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Konrad Dybcio <konrad.dybcio@somainline.org>,
<devicetree@vger.kernel.org>, <linux-arm-msm@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm64: dts: qcom: sc7280: Update SNPS Phy params for SC7280
Date: Thu, 29 Sep 2022 15:14:24 +0530 [thread overview]
Message-ID: <270b0dfe-25fb-b5a1-e0cc-6a284367a173@quicinc.com> (raw)
In-Reply-To: <4d391a78-f524-5bb7-92e0-9778396ed0cb@linaro.org>
On 9/29/2022 2:44 PM, Krzysztof Kozlowski wrote:
> On 29/09/2022 11:02, Dmitry Baryshkov wrote:
>> On Thu, 29 Sept 2022 at 11:54, Krishna Kurapati PSSNV
>> <quic_kriskura@quicinc.com> wrote:
>>>
>>>
>>> On 9/29/2022 1:29 PM, Dmitry Baryshkov wrote:
>>>> On Thu, 29 Sept 2022 at 10:14, Krishna Kurapati
>>>> <quic_kriskura@quicinc.com> wrote:
>>>>>
>>>>> Override the SNPS Phy tuning parameters for SC7280 devices. These
>>>>> values are common for both trogdor and herobrine variants.
>>>>
>>>> They are common for trogdor and herobrine, but should these parameters
>>>> be a default? In other words, a random new device based on sc7280
>>>> would more likely use these overrides or the hardware defaults?
>>>>
>>> Hi Dmitry,
>>>
>>> Currently there are only two platforms, so I made these changes on
>>> common dtsi. If a new platform comes (mostly it won't) we can override
>>> them in platform specific file is what I thought.
>>
Hi Dmitry, Krzysztof,
>> This is not how it usually works. The 'sc7280.dtsi' is not a 'common
>> dtsi' for trogdor and herobrine. It describes the SoC.
>> Thus in my opinion if these overrides should be a default to all
>> sc7280 platforms, this patch is fine. If these overrides are
>> applicable only to the two mentioned platforms, they should go to
>> respective platform-specific DT files.
>
> Dmitry's conclusion is correct here. The true question is whether these
> are properties of the SoC itself (so do not depend on the board or board
> layout) or these depend on design of board.
>
> Best regards,
> Krzysztof
>
Thanks for the info. These parameters are per-board and not common to
SoC. I sent one patch previously for IDP platform [1]. I will let that
get merged and I will send a v2 of this patch adding parameters only for
herobrine platform.
[1] :
https://patchwork.kernel.org/project/linux-usb/patch/1662480933-12326-4-git-send-email-quic_kriskura@quicinc.com/
Thanks,
Krishna,
prev parent reply other threads:[~2022-09-29 9:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-29 7:13 Krishna Kurapati
2022-09-29 7:50 ` Krzysztof Kozlowski
2022-09-29 8:58 ` Krishna Kurapati PSSNV
2022-09-29 7:59 ` Dmitry Baryshkov
2022-09-29 8:54 ` Krishna Kurapati PSSNV
2022-09-29 9:02 ` Dmitry Baryshkov
2022-09-29 9:14 ` Krzysztof Kozlowski
2022-09-29 9:44 ` Krishna Kurapati PSSNV [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=270b0dfe-25fb-b5a1-e0cc-6a284367a173@quicinc.com \
--to=quic_kriskura@quicinc.com \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=konrad.dybcio@somainline.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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®