lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 29 Sep 2022 12:02:24 +0300
From:   Dmitry Baryshkov <dmitry.baryshkov@...aro.org>
To:     Krishna Kurapati PSSNV <quic_kriskura@...cinc.com>
Cc:     Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
        Rob Herring <robh+dt@...nel.org>,
        Andy Gross <agross@...nel.org>,
        Bjorn Andersson <bjorn.andersson@...aro.org>,
        Konrad Dybcio <konrad.dybcio@...ainline.org>,
        devicetree@...r.kernel.org, linux-arm-msm@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] arm64: dts: qcom: sc7280: Update SNPS Phy params for SC7280

On Thu, 29 Sept 2022 at 11:54, Krishna Kurapati PSSNV
<quic_kriskura@...cinc.com> wrote:
>
>
> On 9/29/2022 1:29 PM, Dmitry Baryshkov wrote:
> > On Thu, 29 Sept 2022 at 10:14, Krishna Kurapati
> > <quic_kriskura@...cinc.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.

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.

>
> Regards,
> Krishna,
> >>
> >> Signed-off-by: Krishna Kurapati <quic_kriskura@...cinc.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@...9000 {
> >> --
> >> 2.7.4
> >>
> >
> >



-- 
With best wishes
Dmitry

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ