Message ID | 20230113150310.29709-5-quic_devipriy@quicinc.com |
---|---|
State | New |
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a5d:4e01:0:0:0:0:0 with SMTP id p1csp325210wrt; Fri, 13 Jan 2023 07:17:41 -0800 (PST) X-Google-Smtp-Source: AMrXdXvaFOVWyRIMzKlYj1Z4yXWl5QBJ/09yZkas5jRJeLXZu1I8FyAEgmU6EZrcYEWAxdiT9Kx9 X-Received: by 2002:aa7:9796:0:b0:58a:66a8:edf5 with SMTP id o22-20020aa79796000000b0058a66a8edf5mr15108120pfp.3.1673623060972; Fri, 13 Jan 2023 07:17:40 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1673623060; cv=none; d=google.com; s=arc-20160816; b=QXoli+z8zff4cKsCzNAgWp93EntZDVCyk7RhZW/QPGcFh3zDqs3xV7ilRcvkfves9/ rL6DEiqgdV6GqzK0FS/QvzSL/jDATNripDzZ4wdClmYAXmUqaqfUWL+QSGcDD0cYiLjk 2l9i0/EaFKZpf1WmqD4wSUw9vGs3VM3WOgkVS6i63I5+cM/xUxDTKhIBKK8AjNYEuYlG w2MZim5jtHe4r9eFM9OkHG6re3lGXgDIqm64Ywyd12H2Hginae+KFmMi497PTGhp2Upc WSDjPR4gQCC43EWYt+2pObCIHEvSSoUqcaQJks+uY/EqyXZ9TURaxWoI2lhYZ1JQcwBO 4zJg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:references:in-reply-to:message-id :date:subject:cc:to:from:dkim-signature; bh=0OFOo0CiZoLg9ISRG/zN8+crvn3Y/0Hq8FhVcw1gqQ4=; b=jO6+56TrZ+rUZ7z1FzhXmX/eqUjbyfpKwwoSUIjFnh/AgCLP8XjqtfluFxzT2VRfWt Io/V5WOdP91q+Nd2JtOKGDrivRPLb/Ic+fQJs0ME54Ms7vOcKNRBVwACHh4m5Nc/Nmos cg0kQ2BvCcqfkPsJggdf32c0caLxi+djhRbp8zoxtvMdufVgF/OSr69F/6etCYtMD45i oskdpdpJMS0i+lS1LvCNMPM6hWtOFMqmCH7ygmhvttRWH8FnPZ5pwJqJ2cob6VoR+8Rj TdL41IsmQjPfzzpj6i0vhvTpmF5n+S79cuiO/blToAmvxDi+rH3lkmpbqpohkVV5Zzc6 OSGw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@quicinc.com header.s=qcppdkim1 header.b=EkpndCnJ; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=quicinc.com Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id 207-20020a6216d8000000b0058802fab480si15160311pfw.324.2023.01.13.07.17.29; Fri, 13 Jan 2023 07:17:40 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@quicinc.com header.s=qcppdkim1 header.b=EkpndCnJ; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=quicinc.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229920AbjAMPOK (ORCPT <rfc822;callmefire3@gmail.com> + 99 others); Fri, 13 Jan 2023 10:14:10 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:34200 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229852AbjAMPNZ (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Fri, 13 Jan 2023 10:13:25 -0500 Received: from mx0b-0031df01.pphosted.com (mx0b-0031df01.pphosted.com [205.220.180.131]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5BF9132265; Fri, 13 Jan 2023 07:03:59 -0800 (PST) Received: from pps.filterd (m0279868.ppops.net [127.0.0.1]) by mx0a-0031df01.pphosted.com (8.17.1.19/8.17.1.19) with ESMTP id 30DCvgjn004106; Fri, 13 Jan 2023 15:03:53 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=quicinc.com; h=from : to : cc : subject : date : message-id : in-reply-to : references : mime-version : content-type; s=qcppdkim1; bh=0OFOo0CiZoLg9ISRG/zN8+crvn3Y/0Hq8FhVcw1gqQ4=; b=EkpndCnJK7H7hXLdmDgVGLKaJk+381B7HSLmdxd7mQ+V6At+lJrjAmmAgX7E2xnZ6ITh wv0qr8My6cIaJDz29YVdZxstZdYA4osdOySHb8/D66paI9TLm3T8RK5w5mh9kiZv6Szc 7+8TtwKyMBpgODTUoirczLlCgDFdWZpsWepmA4rsnhfSclCUeHEl3k8Qh0YlHVGjft7D Pj84bbeBjQMJkHvZ/9yuAxteRa+7eKdXQbwvIzRwglzJQdw7bHsC8JS96gqom/r0I95R 83qF7u/LedlCeXblpdAI4EiCXzWH2s6MwBfuANrcBZwmMQdljpAqgmbF/+gW2EoumMQP JA== Received: from nalasppmta01.qualcomm.com (Global_NAT1.qualcomm.com [129.46.96.20]) by mx0a-0031df01.pphosted.com (PPS) with ESMTPS id 3n2jghu1mp-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 13 Jan 2023 15:03:53 +0000 Received: from nalasex01a.na.qualcomm.com (nalasex01a.na.qualcomm.com [10.47.209.196]) by NALASPPMTA01.qualcomm.com (8.17.1.5/8.17.1.5) with ESMTPS id 30DF3psp027993 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 13 Jan 2023 15:03:51 GMT Received: from devipriy-linux.qualcomm.com (10.80.80.8) by nalasex01a.na.qualcomm.com (10.47.209.196) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.986.36; Fri, 13 Jan 2023 07:03:46 -0800 From: devi priya <quic_devipriy@quicinc.com> To: <agross@kernel.org>, <andersson@kernel.org>, <konrad.dybcio@linaro.org>, <lgirdwood@gmail.com>, <broonie@kernel.org>, <robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>, <linux-arm-msm@vger.kernel.org>, <linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org> CC: <quic_srichara@quicinc.com>, <quic_gokulsri@quicinc.com>, <quic_sjaganat@quicinc.com>, <quic_kathirav@quicinc.com>, <quic_arajkuma@quicinc.com>, <quic_anusha@quicinc.com>, <quic_poovendh@quicinc.com> Subject: [PATCH 4/6] regulator: qcom_smd: Add PMIC compatible for IPQ9574 Date: Fri, 13 Jan 2023 20:33:08 +0530 Message-ID: <20230113150310.29709-5-quic_devipriy@quicinc.com> X-Mailer: git-send-email 2.17.1 In-Reply-To: <20230113150310.29709-1-quic_devipriy@quicinc.com> References: <20230113150310.29709-1-quic_devipriy@quicinc.com> MIME-Version: 1.0 Content-Type: text/plain X-Originating-IP: [10.80.80.8] X-ClientProxiedBy: nasanex01a.na.qualcomm.com (10.52.223.231) To nalasex01a.na.qualcomm.com (10.47.209.196) X-QCInternal: smtphost X-Proofpoint-Virus-Version: vendor=nai engine=6200 definitions=5800 signatures=585085 X-Proofpoint-GUID: MTYOGwN7WXa5O-fqgnTqnbfY_1iTi5Ja X-Proofpoint-ORIG-GUID: MTYOGwN7WXa5O-fqgnTqnbfY_1iTi5Ja X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.219,Aquarius:18.0.923,Hydra:6.0.562,FMLib:17.11.122.1 definitions=2023-01-13_07,2023-01-13_01,2022-06-22_01 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 adultscore=0 spamscore=0 malwarescore=0 mlxscore=0 suspectscore=0 priorityscore=1501 phishscore=0 clxscore=1015 bulkscore=0 impostorscore=0 mlxlogscore=911 lowpriorityscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2212070000 definitions=main-2301130099 X-Spam-Status: No, score=1.2 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_SBL_CSS,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=3.4.6 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: <linux-kernel.vger.kernel.org> X-Mailing-List: linux-kernel@vger.kernel.org X-getmail-retrieved-from-mailbox: =?utf-8?q?INBOX?= X-GMAIL-THRID: =?utf-8?q?1754920974659329201?= X-GMAIL-MSGID: =?utf-8?q?1754920974659329201?= |
Series |
Add regulator support for IPQ9574 SoC
|
|
Commit Message
Devi Priya
Jan. 13, 2023, 3:03 p.m. UTC
Add mp5496 PMIC compatible string for IPQ9574 SoC Co-developed-by: Praveenkumar I <quic_ipkumar@quicinc.com> Signed-off-by: Praveenkumar I <quic_ipkumar@quicinc.com> Signed-off-by: devi priya <quic_devipriy@quicinc.com> --- .../devicetree/bindings/regulator/qcom,smd-rpm-regulator.yaml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
Comments
On Fri, Jan 13, 2023 at 08:33:08PM +0530, devi priya wrote: > Add mp5496 PMIC compatible string for IPQ9574 SoC > > Co-developed-by: Praveenkumar I <quic_ipkumar@quicinc.com> > Signed-off-by: Praveenkumar I <quic_ipkumar@quicinc.com> > Signed-off-by: devi priya <quic_devipriy@quicinc.com> > --- > .../devicetree/bindings/regulator/qcom,smd-rpm-regulator.yaml | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) > > diff --git a/Documentation/devicetree/bindings/regulator/qcom,smd-rpm-regulator.yaml b/Documentation/devicetree/bindings/regulator/qcom,smd-rpm-regulator.yaml > index 8c45f53212b1..7907d9385583 100644 > --- a/Documentation/devicetree/bindings/regulator/qcom,smd-rpm-regulator.yaml > +++ b/Documentation/devicetree/bindings/regulator/qcom,smd-rpm-regulator.yaml > @@ -22,7 +22,7 @@ description: > Each sub-node is identified using the node's name, with valid values listed > for each of the pmics below. > > - For mp5496, s2 > + For mp5496, s1, s2 > > For pm2250, s1, s2, s3, s4, l1, l2, l3, l4, l5, l6, l7, l8, l9, l10, l11, > l12, l13, l14, l15, l16, l17, l18, l19, l20, l21, l22 > @@ -84,6 +84,7 @@ properties: > compatible: > enum: > - qcom,rpm-mp5496-regulators > + - qcom,rpm-ipq9574-mp5496-regulators Is this a different part than just mp5496? Or used in a different, incompatible way? > - qcom,rpm-pm2250-regulators > - qcom,rpm-pm6125-regulators > - qcom,rpm-pm660-regulators > -- > 2.17.1 >
On 1/18/2023 12:08 AM, Rob Herring wrote: > On Fri, Jan 13, 2023 at 08:33:08PM +0530, devi priya wrote: >> Add mp5496 PMIC compatible string for IPQ9574 SoC >> >> Co-developed-by: Praveenkumar I <quic_ipkumar@quicinc.com> >> Signed-off-by: Praveenkumar I <quic_ipkumar@quicinc.com> >> Signed-off-by: devi priya <quic_devipriy@quicinc.com> >> --- >> .../devicetree/bindings/regulator/qcom,smd-rpm-regulator.yaml | 3 ++- >> 1 file changed, 2 insertions(+), 1 deletion(-) >> >> diff --git a/Documentation/devicetree/bindings/regulator/qcom,smd-rpm-regulator.yaml b/Documentation/devicetree/bindings/regulator/qcom,smd-rpm-regulator.yaml >> index 8c45f53212b1..7907d9385583 100644 >> --- a/Documentation/devicetree/bindings/regulator/qcom,smd-rpm-regulator.yaml >> +++ b/Documentation/devicetree/bindings/regulator/qcom,smd-rpm-regulator.yaml >> @@ -22,7 +22,7 @@ description: >> Each sub-node is identified using the node's name, with valid values listed >> for each of the pmics below. >> >> - For mp5496, s2 >> + For mp5496, s1, s2 >> >> For pm2250, s1, s2, s3, s4, l1, l2, l3, l4, l5, l6, l7, l8, l9, l10, l11, >> l12, l13, l14, l15, l16, l17, l18, l19, l20, l21, l22 >> @@ -84,6 +84,7 @@ properties: >> compatible: >> enum: >> - qcom,rpm-mp5496-regulators >> + - qcom,rpm-ipq9574-mp5496-regulators > > Is this a different part than just mp5496? Or used in a different, > incompatible way? IPQ6018 and IPQ9574 platforms use the same PMIC MP5496 but they have a different power layout.So, we plan to update the compatible: qcom,rpm-mp5496-regulators to qcom,rpm-ipq6018-mp5496-regulators(target-specific) in the next patchset as the regulators serve different purposes > >> - qcom,rpm-pm2250-regulators >> - qcom,rpm-pm6125-regulators >> - qcom,rpm-pm660-regulators >> -- >> 2.17.1 >> Best Regards, Devi Priya
On Fri, Jan 27, 2023 at 10:05 AM Devi Priya <quic_devipriy@quicinc.com> wrote: > > > > On 1/18/2023 12:08 AM, Rob Herring wrote: > > On Fri, Jan 13, 2023 at 08:33:08PM +0530, devi priya wrote: > >> Add mp5496 PMIC compatible string for IPQ9574 SoC > >> > >> Co-developed-by: Praveenkumar I <quic_ipkumar@quicinc.com> > >> Signed-off-by: Praveenkumar I <quic_ipkumar@quicinc.com> > >> Signed-off-by: devi priya <quic_devipriy@quicinc.com> > >> --- > >> .../devicetree/bindings/regulator/qcom,smd-rpm-regulator.yaml | 3 ++- > >> 1 file changed, 2 insertions(+), 1 deletion(-) > >> > >> diff --git a/Documentation/devicetree/bindings/regulator/qcom,smd-rpm-regulator.yaml b/Documentation/devicetree/bindings/regulator/qcom,smd-rpm-regulator.yaml > >> index 8c45f53212b1..7907d9385583 100644 > >> --- a/Documentation/devicetree/bindings/regulator/qcom,smd-rpm-regulator.yaml > >> +++ b/Documentation/devicetree/bindings/regulator/qcom,smd-rpm-regulator.yaml > >> @@ -22,7 +22,7 @@ description: > >> Each sub-node is identified using the node's name, with valid values listed > >> for each of the pmics below. > >> > >> - For mp5496, s2 > >> + For mp5496, s1, s2 > >> > >> For pm2250, s1, s2, s3, s4, l1, l2, l3, l4, l5, l6, l7, l8, l9, l10, l11, > >> l12, l13, l14, l15, l16, l17, l18, l19, l20, l21, l22 > >> @@ -84,6 +84,7 @@ properties: > >> compatible: > >> enum: > >> - qcom,rpm-mp5496-regulators > >> + - qcom,rpm-ipq9574-mp5496-regulators > > > > Is this a different part than just mp5496? Or used in a different, > > incompatible way? > IPQ6018 and IPQ9574 platforms use the same PMIC MP5496 but they have a > different power layout.So, we plan to update the compatible: > qcom,rpm-mp5496-regulators to > qcom,rpm-ipq6018-mp5496-regulators(target-specific) in the next patchset > as the regulators serve different purposes You can't just change compatibles. It is an ABI. This still doesn't make sense to me. The PMIC hasn't changed, so the binding shouldn't. It should be flexible enough to be hooked up to different platforms. That's why we have all the per regulator configuration. What are you missing? Rob
On 1/28/2023 1:42 AM, Rob Herring wrote: > On Fri, Jan 27, 2023 at 10:05 AM Devi Priya <quic_devipriy@quicinc.com> wrote: >> >> >> >> On 1/18/2023 12:08 AM, Rob Herring wrote: >>> On Fri, Jan 13, 2023 at 08:33:08PM +0530, devi priya wrote: >>>> Add mp5496 PMIC compatible string for IPQ9574 SoC >>>> >>>> Co-developed-by: Praveenkumar I <quic_ipkumar@quicinc.com> >>>> Signed-off-by: Praveenkumar I <quic_ipkumar@quicinc.com> >>>> Signed-off-by: devi priya <quic_devipriy@quicinc.com> >>>> --- >>>> .../devicetree/bindings/regulator/qcom,smd-rpm-regulator.yaml | 3 ++- >>>> 1 file changed, 2 insertions(+), 1 deletion(-) >>>> >>>> diff --git a/Documentation/devicetree/bindings/regulator/qcom,smd-rpm-regulator.yaml b/Documentation/devicetree/bindings/regulator/qcom,smd-rpm-regulator.yaml >>>> index 8c45f53212b1..7907d9385583 100644 >>>> --- a/Documentation/devicetree/bindings/regulator/qcom,smd-rpm-regulator.yaml >>>> +++ b/Documentation/devicetree/bindings/regulator/qcom,smd-rpm-regulator.yaml >>>> @@ -22,7 +22,7 @@ description: >>>> Each sub-node is identified using the node's name, with valid values listed >>>> for each of the pmics below. >>>> >>>> - For mp5496, s2 >>>> + For mp5496, s1, s2 >>>> >>>> For pm2250, s1, s2, s3, s4, l1, l2, l3, l4, l5, l6, l7, l8, l9, l10, l11, >>>> l12, l13, l14, l15, l16, l17, l18, l19, l20, l21, l22 >>>> @@ -84,6 +84,7 @@ properties: >>>> compatible: >>>> enum: >>>> - qcom,rpm-mp5496-regulators >>>> + - qcom,rpm-ipq9574-mp5496-regulators >>> >>> Is this a different part than just mp5496? Or used in a different, >>> incompatible way? >> IPQ6018 and IPQ9574 platforms use the same PMIC MP5496 but they have a >> different power layout.So, we plan to update the compatible: >> qcom,rpm-mp5496-regulators to >> qcom,rpm-ipq6018-mp5496-regulators(target-specific) in the next patchset >> as the regulators serve different purposes > > You can't just change compatibles. It is an ABI. > > This still doesn't make sense to me. The PMIC hasn't changed, so the > binding shouldn't. It should be flexible enough to be hooked up to > different platforms. That's why we have all the per regulator > configuration. What are you missing? > > Rob Sure got it! It should be fine to use the existing mp5496 compatible for IPQ9574 too. Will update this in V2 Best Regards, Devi Priya
diff --git a/Documentation/devicetree/bindings/regulator/qcom,smd-rpm-regulator.yaml b/Documentation/devicetree/bindings/regulator/qcom,smd-rpm-regulator.yaml index 8c45f53212b1..7907d9385583 100644 --- a/Documentation/devicetree/bindings/regulator/qcom,smd-rpm-regulator.yaml +++ b/Documentation/devicetree/bindings/regulator/qcom,smd-rpm-regulator.yaml @@ -22,7 +22,7 @@ description: Each sub-node is identified using the node's name, with valid values listed for each of the pmics below. - For mp5496, s2 + For mp5496, s1, s2 For pm2250, s1, s2, s3, s4, l1, l2, l3, l4, l5, l6, l7, l8, l9, l10, l11, l12, l13, l14, l15, l16, l17, l18, l19, l20, l21, l22 @@ -84,6 +84,7 @@ properties: compatible: enum: - qcom,rpm-mp5496-regulators + - qcom,rpm-ipq9574-mp5496-regulators - qcom,rpm-pm2250-regulators - qcom,rpm-pm6125-regulators - qcom,rpm-pm660-regulators