[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7941f5de-547c-4a92-9af1-a1c0add1ace4@quicinc.com>
Date: Thu, 3 Aug 2023 10:36:45 +0530
From: Pavan Kondeti <quic_pkondeti@...cinc.com>
To: Konrad Dybcio <konrad.dybcio@...aro.org>
CC: Rohit Agarwal <quic_rohiagar@...cinc.com>, <agross@...nel.org>,
<andersson@...nel.org>, <robh+dt@...nel.org>,
<krzysztof.kozlowski+dt@...aro.org>, <conor+dt@...nel.org>,
<linux-arm-msm@...r.kernel.org>, <devicetree@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <quic_jackp@...cinc.com>
Subject: Re: [PATCH 3/8] arm64: dts: qcom: Add PMIC pm7550ba dtsi
On Wed, Aug 02, 2023 at 03:14:19PM +0200, Konrad Dybcio wrote:
> On 2.08.2023 15:13, Rohit Agarwal wrote:
> >
> > On 8/2/2023 6:12 PM, Konrad Dybcio wrote:
> >> On 2.08.2023 11:59, Rohit Agarwal wrote:
> >>> Add dtsi for PMIC pm7550ba found in Qualcomm platforms.
> >>>
> >>> Signed-off-by: Rohit Agarwal <quic_rohiagar@...cinc.com>
> >>> ---
> >> Subject: "PMIC pm7550ba" -> "pm7550ba PMIC"
> >>
> >> [...]
> >>
> >>> +
> >>> + pm7550ba_eusb2_repeater: phy@...0 {
> >>> + compatible = "qcom,pm8550b-eusb2-repeater";
> >> A new compatible should be introduced, so that it goes like this:
> >>
> >> compatible = "qcom,pm7550ba-eusb2-repeater", "qcom,pm8550b-eusb2-repeater";
> > Just a doubt, Since the compatible can be same why we need to introduce a new compatible.
> > Should every soc have a compatible string?
> If it turns out that we need to add a quirk for PM7550BA 3 years down
> the line, this approach lets us fix it for users that never updated
> their device trees.
>
Trying to make my understanding clear.
eUSB repeater is a peripheral in the PMIC. Do we need a separate
compatible even if the peripheral is same in two different PMIC chips?
I believe eUSB peripheral has some identification registers to apply any
quirks in future.
Adding Jack who would know more about any deltas between the PMICs in
sdx75 and sm8550.
Thanks,
Pavan
Powered by blists - more mailing lists