From: Krishna Kurapati PSSNV <quic_kriskura@quicinc.com>
To: 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 14:24:23 +0530 [thread overview]
Message-ID: <0cc382cb-b76e-a5a5-3480-47a451bdc958@quicinc.com> (raw)
In-Reply-To: <CAA8EJpr9pcN-SG-yQNUGEoHCmv74prChprj4f42PKpSAzGzVKQ@mail.gmail.com>
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.
Regards,
Krishna,
>>
>> Signed-off-by: Krishna Kurapati <quic_kriskura@quicinc.com>
>> ---
>> arch/arm64/boot/dts/qcom/sc7280.dtsi | 7 +++++++
>> 1 file changed, 7 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/qcom/sc7280.dtsi b/arch/arm64/boot/dts/qcom/sc7280.dtsi
>> index 2125803..ae2c23e 100644
>> --- a/arch/arm64/boot/dts/qcom/sc7280.dtsi
>> +++ b/arch/arm64/boot/dts/qcom/sc7280.dtsi
>> @@ -3310,6 +3310,13 @@
>> clock-names = "ref";
>>
>> resets = <&gcc GCC_QUSB2PHY_SEC_BCR>;
>> +
>> + qcom,hs-rise-fall-time-bp = <0>;
>> + qcom,squelch-detector-bp = <(-2090)>;
>> + qcom,hs-disconnect-bp = <1743>;
>> + qcom,hs-amplitude-bp = <1780>;
>> + qcom,hs-crossover-voltage-microvolt = <(-31000)>;
>> + qcom,hs-output-impedance-micro-ohms = <2600000>;
>> };
>>
>> usb_1_qmpphy: phy-wrapper@88e9000 {
>> --
>> 2.7.4
>>
>
>
next prev parent reply other threads:[~2022-09-29 8:55 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 [this message]
2022-09-29 9:02 ` Dmitry Baryshkov
2022-09-29 9:14 ` Krzysztof Kozlowski
2022-09-29 9:44 ` Krishna Kurapati PSSNV
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=0cc382cb-b76e-a5a5-3480-47a451bdc958@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=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®