Message ID | 20230718062639.2339589-2-quic_fenglinw@quicinc.com |
---|---|
State | New |
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a59:c923:0:b0:3e4:2afc:c1 with SMTP id j3csp1542599vqt; Mon, 17 Jul 2023 23:32:25 -0700 (PDT) X-Google-Smtp-Source: APBJJlEvalS6k7Cw0RKMi0e4HaRAzC/ecXVLX4CdwUw6uqMmcMee/rvIRaQVf8Ia+8zCijrkSO7U X-Received: by 2002:a17:902:e749:b0:1b8:59f0:c748 with SMTP id p9-20020a170902e74900b001b859f0c748mr15892115plf.2.1689661945589; Mon, 17 Jul 2023 23:32:25 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1689661945; cv=none; d=google.com; s=arc-20160816; b=b2QdKfvbHat09Bpqqxn7VPqqxIi0jC4nTLEjboxGNWanlVfpD690p6rOVoWFjfgu0o t0cSEDAKi1Eb5TM4jXSe+VeuqM/4iS4V8lrPfrUEAyd4eTo5zWQdj1V8hnknlyO4XuYR /KXN4e6SHZnmTNONlXiEV8lv0zHpirXg5LErmHMXbmWULyjliiQGW0GNvRtvgJxTHe6r XTGzk4AoUW71haXpfdCQsXPGWLuy7eL4/j1olRhykz8doDjta9dPxc6klfIsmuCMKwcK Kagr4RNe6hY0DBtxNPlupZEYZu6KXaEn4+FVzyMVkJCrWkGIVfETk07wgycHLFNclkny MRPQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=DOiSuhikKILZQ3ltZPY7WPmQRpVQlaQy1lW6ywDJBds=; fh=LZBxhEbGTof0DRv3UaUcm/iZ+ppvVrOoyeskFWFcydg=; b=K/f/2VRW3BLjt3ecP8SuWuvtY7HJb3l++Ia3RL3tLsq1r+ApGj8xcboou6nmODCF6m 8FwZR4qKXIUce5Wxvjot5OjsbytWW1ts17xOjeZqtN+8Ri4RpNLxzgTJSdGNcewAw+mv cIi3JQupVZUO2dsajP/UAwaSsv3eITAZmrm/CbeLvVwxRzvmKEaeoz5YJ70nuasqR2rC kGUfF8PjaizYcA747mTUOIt4UV/zRIwK0sY6/Vzim/OOtX4J59GG9bb/rLfRWI9d7RD0 8WWgPz6PR6LBmMZgv7wbwQPwbLL8eM7ukKPVVtqAH0zLKVz3eDXxMOBTc0Nt14EjlkNm +SEg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@quicinc.com header.s=qcppdkim1 header.b=GEn6ym8A; 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 x2-20020a170902a38200b001b8955938ccsi1129874pla.331.2023.07.17.23.32.12; Mon, 17 Jul 2023 23:32:25 -0700 (PDT) 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=GEn6ym8A; 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 S230333AbjGRG1Y (ORCPT <rfc822;daweilics@gmail.com> + 99 others); Tue, 18 Jul 2023 02:27:24 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:34692 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231276AbjGRG1L (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Tue, 18 Jul 2023 02:27:11 -0400 Received: from mx0a-0031df01.pphosted.com (mx0a-0031df01.pphosted.com [205.220.168.131]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B1C121A5; Mon, 17 Jul 2023 23:27:05 -0700 (PDT) Received: from pps.filterd (m0279862.ppops.net [127.0.0.1]) by mx0a-0031df01.pphosted.com (8.17.1.19/8.17.1.19) with ESMTP id 36I483Sp015472; Tue, 18 Jul 2023 06:27:01 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-transfer-encoding : content-type; s=qcppdkim1; bh=DOiSuhikKILZQ3ltZPY7WPmQRpVQlaQy1lW6ywDJBds=; b=GEn6ym8ATePE++sRglounsmEvaeeFl8sM4gImdqP9QxXUlZEPq6Bvqe14SnmalX35VwP M0gHl4kgektqnpt8sSW7SC4ZuvJDu1hjHEEgB5GHvaDApjUUE/B+4ZXhrXnllWFObldq Wu4uAQVRPNk6K6vEn4LfVP0FX1MzhsXLAN9JBL1LqXcMBKZO7ST7lFeyQIMatJE46vQl 72Y4MHlk+x+qfJEuKfN6HiiSKzJOOAZfZAcmVyMbw9CsEkByrAkbb7et7VTWYjY9DiJr Hd7lKzQrmegegT3dRumzzbMxP5NCU4imBVMaISLYgfib1tnRBU9MGCXsu6kR+vzjW2TR 3A== Received: from nalasppmta04.qualcomm.com (Global_NAT1.qualcomm.com [129.46.96.20]) by mx0a-0031df01.pphosted.com (PPS) with ESMTPS id 3rwk5bg8vj-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 18 Jul 2023 06:27:01 +0000 Received: from nalasex01c.na.qualcomm.com (nalasex01c.na.qualcomm.com [10.47.97.35]) by NALASPPMTA04.qualcomm.com (8.17.1.5/8.17.1.5) with ESMTPS id 36I6R0KC000641 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 18 Jul 2023 06:27:00 GMT Received: from fenglinw2-gv.qualcomm.com (10.80.80.8) by nalasex01c.na.qualcomm.com (10.47.97.35) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1118.30; Mon, 17 Jul 2023 23:26:56 -0700 From: Fenglin Wu <quic_fenglinw@quicinc.com> To: <linux-arm-msm@vger.kernel.org>, <linux-kernel@vger.kernel.org>, "Andy Gross" <agross@kernel.org>, Bjorn Andersson <andersson@kernel.org>, "Konrad Dybcio" <konrad.dybcio@linaro.org>, Dmitry Torokhov <dmitry.torokhov@gmail.com>, Rob Herring <robh+dt@kernel.org>, "Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>, <linux-input@vger.kernel.org>, <devicetree@vger.kernel.org> CC: <quic_collinsd@quicinc.com>, <quic_subbaram@quicinc.com>, <quic_fenglinw@quicinc.com>, <quic_kamalw@quicinc.com>, <jestar@qti.qualcomm.com> Subject: [PATCH v2 1/2] dt-bindings: input: qcom,pm8xxx-vib: add more PMIC support Date: Tue, 18 Jul 2023 14:26:38 +0800 Message-ID: <20230718062639.2339589-2-quic_fenglinw@quicinc.com> X-Mailer: git-send-email 2.25.1 In-Reply-To: <20230718062639.2339589-1-quic_fenglinw@quicinc.com> References: <20230718062639.2339589-1-quic_fenglinw@quicinc.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain X-Originating-IP: [10.80.80.8] X-ClientProxiedBy: nasanex01a.na.qualcomm.com (10.52.223.231) To nalasex01c.na.qualcomm.com (10.47.97.35) X-QCInternal: smtphost X-Proofpoint-Virus-Version: vendor=nai engine=6200 definitions=5800 signatures=585085 X-Proofpoint-GUID: 6SmFWC8Ol-TziydCzrvxbvX-SCu3X1qU X-Proofpoint-ORIG-GUID: 6SmFWC8Ol-TziydCzrvxbvX-SCu3X1qU X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.254,Aquarius:18.0.957,Hydra:6.0.591,FMLib:17.11.176.26 definitions=2023-07-17_15,2023-07-13_01,2023-05-22_02 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 impostorscore=0 phishscore=0 spamscore=0 adultscore=0 mlxlogscore=832 priorityscore=1501 clxscore=1015 suspectscore=0 bulkscore=0 lowpriorityscore=0 malwarescore=0 mlxscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2306200000 definitions=main-2307180058 X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_BLOCKED, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 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: INBOX X-GMAIL-THRID: 1771738964496858977 X-GMAIL-MSGID: 1771738964496858977 |
Series |
Add support for vibrator in multiple PMICs
|
|
Commit Message
Fenglin Wu
July 18, 2023, 6:26 a.m. UTC
Add support for vibrator module inside Qualcomm PMI632, PM7250B, PM7325B
PMICs.
Signed-off-by: Fenglin Wu <quic_fenglinw@quicinc.com>
---
Documentation/devicetree/bindings/input/qcom,pm8xxx-vib.yaml | 3 +++
1 file changed, 3 insertions(+)
Comments
On 18/07/2023 08:26, Fenglin Wu wrote: > Add support for vibrator module inside Qualcomm PMI632, PM7250B, PM7325B > PMICs. > > Signed-off-by: Fenglin Wu <quic_fenglinw@quicinc.com> > --- I don't see changelog. No changes then? > Documentation/devicetree/bindings/input/qcom,pm8xxx-vib.yaml | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git a/Documentation/devicetree/bindings/input/qcom,pm8xxx-vib.yaml b/Documentation/devicetree/bindings/input/qcom,pm8xxx-vib.yaml > index c8832cd0d7da..481163105d24 100644 > --- a/Documentation/devicetree/bindings/input/qcom,pm8xxx-vib.yaml > +++ b/Documentation/devicetree/bindings/input/qcom,pm8xxx-vib.yaml > @@ -15,6 +15,9 @@ properties: > - qcom,pm8058-vib > - qcom,pm8916-vib > - qcom,pm8921-vib > + - qcom,pmi632-vib > + - qcom,pm7250b-vib > + - qcom,pm7325b-vib Not much improved. With missing changelog, it seems you ignored the feedback. Best regards, Krzysztof
On 7/18/2023 2:33 PM, Krzysztof Kozlowski wrote: > On 18/07/2023 08:26, Fenglin Wu wrote: >> Add support for vibrator module inside Qualcomm PMI632, PM7250B, PM7325B >> PMICs. >> >> Signed-off-by: Fenglin Wu <quic_fenglinw@quicinc.com> >> --- > > I don't see changelog. No changes then? > Sorry, I updated the change log in the cover letter which didn't seems to be sent to a wider audience, I will resend it by adding more receivers in the to list Fenglin >> Documentation/devicetree/bindings/input/qcom,pm8xxx-vib.yaml | 3 +++ >> 1 file changed, 3 insertions(+) >> >> diff --git a/Documentation/devicetree/bindings/input/qcom,pm8xxx-vib.yaml b/Documentation/devicetree/bindings/input/qcom,pm8xxx-vib.yaml >> index c8832cd0d7da..481163105d24 100644 >> --- a/Documentation/devicetree/bindings/input/qcom,pm8xxx-vib.yaml >> +++ b/Documentation/devicetree/bindings/input/qcom,pm8xxx-vib.yaml >> @@ -15,6 +15,9 @@ properties: >> - qcom,pm8058-vib >> - qcom,pm8916-vib >> - qcom,pm8921-vib >> + - qcom,pmi632-vib >> + - qcom,pm7250b-vib >> + - qcom,pm7325b-vib > > Not much improved. With missing changelog, it seems you ignored the > feedback. > > > Best regards, > Krzysztof >
On 7/18/2023 2:38 PM, Fenglin Wu wrote: > > > On 7/18/2023 2:33 PM, Krzysztof Kozlowski wrote: >> On 18/07/2023 08:26, Fenglin Wu wrote: >>> Add support for vibrator module inside Qualcomm PMI632, PM7250B, PM7325B >>> PMICs. >>> >>> Signed-off-by: Fenglin Wu <quic_fenglinw@quicinc.com> >>> --- >> >> I don't see changelog. No changes then? >> > Sorry, I updated the change log in the cover letter which didn't seems > to be sent to a wider audience, I will resend it by adding more > receivers in the to list > > Fenglin Just FYI,the change log was updated in the cover letter here: https://lore.kernel.org/linux-arm-msm/20230718062639.2339589-1-quic_fenglinw@quicinc.com/T/#m3819b50503ef19e0933a10bf797351a4af35537f Also the commit text and the driver change were also updated accordingly to address your review comment by removing 'pm7550ba-vib' compatible string. Since the changes are receiving review comments, I will not resend it. I will add a larger to-list when pushing the next patchset. >>> Documentation/devicetree/bindings/input/qcom,pm8xxx-vib.yaml | 3 +++ >>> 1 file changed, 3 insertions(+) >>> >>> diff --git >>> a/Documentation/devicetree/bindings/input/qcom,pm8xxx-vib.yaml >>> b/Documentation/devicetree/bindings/input/qcom,pm8xxx-vib.yaml >>> index c8832cd0d7da..481163105d24 100644 >>> --- a/Documentation/devicetree/bindings/input/qcom,pm8xxx-vib.yaml >>> +++ b/Documentation/devicetree/bindings/input/qcom,pm8xxx-vib.yaml >>> @@ -15,6 +15,9 @@ properties: >>> - qcom,pm8058-vib >>> - qcom,pm8916-vib >>> - qcom,pm8921-vib >>> + - qcom,pmi632-vib >>> + - qcom,pm7250b-vib >>> + - qcom,pm7325b-vib >> >> Not much improved. With missing changelog, it seems you ignored the >> feedback. >> >> >> Best regards, >> Krzysztof >>
On 18/07/2023 09:06, Fenglin Wu wrote: > > > On 7/18/2023 2:38 PM, Fenglin Wu wrote: >> >> >> On 7/18/2023 2:33 PM, Krzysztof Kozlowski wrote: >>> On 18/07/2023 08:26, Fenglin Wu wrote: >>>> Add support for vibrator module inside Qualcomm PMI632, PM7250B, PM7325B >>>> PMICs. >>>> >>>> Signed-off-by: Fenglin Wu <quic_fenglinw@quicinc.com> >>>> --- >>> >>> I don't see changelog. No changes then? >>> >> Sorry, I updated the change log in the cover letter which didn't seems >> to be sent to a wider audience, I will resend it by adding more >> receivers in the to list >> >> Fenglin > > Just FYI,the change log was updated in the cover letter here: > https://lore.kernel.org/linux-arm-msm/20230718062639.2339589-1-quic_fenglinw@quicinc.com/T/#m3819b50503ef19e0933a10bf797351a4af35537f > > Also the commit text and the driver change were also updated accordingly > to address your review comment by removing 'pm7550ba-vib' compatible string. Removing compatible was never my feedback. Did you read: https://elixir.bootlin.com/linux/v6.1-rc1/source/Documentation/devicetree/bindings/writing-bindings.rst#L42 ? Best regards, Krzysztof
On 7/18/2023 3:20 PM, Krzysztof Kozlowski wrote: > On 18/07/2023 09:06, Fenglin Wu wrote: >> >> >> On 7/18/2023 2:38 PM, Fenglin Wu wrote: >>> >>> >>> On 7/18/2023 2:33 PM, Krzysztof Kozlowski wrote: >>>> On 18/07/2023 08:26, Fenglin Wu wrote: >>>>> Add support for vibrator module inside Qualcomm PMI632, PM7250B, PM7325B >>>>> PMICs. >>>>> >>>>> Signed-off-by: Fenglin Wu <quic_fenglinw@quicinc.com> >>>>> --- >>>> >>>> I don't see changelog. No changes then? >>>> >>> Sorry, I updated the change log in the cover letter which didn't seems >>> to be sent to a wider audience, I will resend it by adding more >>> receivers in the to list >>> >>> Fenglin >> >> Just FYI,the change log was updated in the cover letter here: >> https://lore.kernel.org/linux-arm-msm/20230718062639.2339589-1-quic_fenglinw@quicinc.com/T/#m3819b50503ef19e0933a10bf797351a4af35537f >> >> Also the commit text and the driver change were also updated accordingly >> to address your review comment by removing 'pm7550ba-vib' compatible string. > > Removing compatible was never my feedback. Did you read: > https://elixir.bootlin.com/linux/v6.1-rc1/source/Documentation/devicetree/bindings/writing-bindings.rst#L42 > ? > Okay, so do you want me to add 'pm7550ba-vib' as a fallback compatible like this? properties: compatible: - enum: - - qcom,pm8058-vib - - qcom,pm8916-vib - - qcom,pm8921-vib - - qcom,pmi632-vib - - qcom,pm7250b-vib - - qcom,pm7325b-vib + oneOf: + - enum: + - qcom,pm8058-vib + - qcom,pm8916-vib + - qcom,pm8921-vib + - qcom,pmi632-vib + - qcom,pm7250b-vib + - qcom,pm7325b-vib + - items: + - enum: + - qcom,pm7550ba-vib + - const: qcom,pm7325b-vib > Best regards, > Krzysztof >
On 18/07/2023 09:59, Fenglin Wu wrote: >>> Just FYI,the change log was updated in the cover letter here: >>> https://lore.kernel.org/linux-arm-msm/20230718062639.2339589-1-quic_fenglinw@quicinc.com/T/#m3819b50503ef19e0933a10bf797351a4af35537f >>> >>> Also the commit text and the driver change were also updated accordingly >>> to address your review comment by removing 'pm7550ba-vib' compatible string. >> >> Removing compatible was never my feedback. Did you read: >> https://elixir.bootlin.com/linux/v6.1-rc1/source/Documentation/devicetree/bindings/writing-bindings.rst#L42 >> ? >> > Okay, so do you want me to add 'pm7550ba-vib' as a fallback compatible > like this? > > properties: > compatible: > - enum: > - - qcom,pm8058-vib > - - qcom,pm8916-vib > - - qcom,pm8921-vib > - - qcom,pmi632-vib > - - qcom,pm7250b-vib > - - qcom,pm7325b-vib > + oneOf: > + - enum: > + - qcom,pm8058-vib > + - qcom,pm8916-vib > + - qcom,pm8921-vib > + - qcom,pmi632-vib > + - qcom,pm7250b-vib > + - qcom,pm7325b-vib > + - items: > + - enum: > + - qcom,pm7550ba-vib > + - const: qcom,pm7325b-vib > Yes Best regards, Krzysztof
On 18.07.2023 08:38, Fenglin Wu wrote: > > > On 7/18/2023 2:33 PM, Krzysztof Kozlowski wrote: >> On 18/07/2023 08:26, Fenglin Wu wrote: >>> Add support for vibrator module inside Qualcomm PMI632, PM7250B, PM7325B >>> PMICs. >>> >>> Signed-off-by: Fenglin Wu <quic_fenglinw@quicinc.com> >>> --- >> >> I don't see changelog. No changes then? >> > Sorry, I updated the change log in the cover letter which didn't seems to be sent to a wider audience, I will resend it by adding more receivers in the to list Please consider using the b4 tool which takes care of all that https://b4.docs.kernel.org/en/latest/index.html Konrad
On 7/18/2023 6:51 PM, Konrad Dybcio wrote: > On 18.07.2023 08:38, Fenglin Wu wrote: >> >> >> On 7/18/2023 2:33 PM, Krzysztof Kozlowski wrote: >>> On 18/07/2023 08:26, Fenglin Wu wrote: >>>> Add support for vibrator module inside Qualcomm PMI632, PM7250B, PM7325B >>>> PMICs. >>>> >>>> Signed-off-by: Fenglin Wu <quic_fenglinw@quicinc.com> >>>> --- >>> >>> I don't see changelog. No changes then? >>> >> Sorry, I updated the change log in the cover letter which didn't seems to be sent to a wider audience, I will resend it by adding more receivers in the to list > Please consider using the b4 tool which takes care of all that > > https://b4.docs.kernel.org/en/latest/index.html > Thanks Konrad, I will check and update at my side. > Konrad
On 18/07/2023 10:02, Krzysztof Kozlowski wrote: > On 18/07/2023 09:59, Fenglin Wu wrote: > >>>> Just FYI,the change log was updated in the cover letter here: >>>> https://lore.kernel.org/linux-arm-msm/20230718062639.2339589-1-quic_fenglinw@quicinc.com/T/#m3819b50503ef19e0933a10bf797351a4af35537f >>>> >>>> Also the commit text and the driver change were also updated accordingly >>>> to address your review comment by removing 'pm7550ba-vib' compatible string. >>> >>> Removing compatible was never my feedback. Did you read: >>> https://elixir.bootlin.com/linux/v6.1-rc1/source/Documentation/devicetree/bindings/writing-bindings.rst#L42 >>> ? >>> >> Okay, so do you want me to add 'pm7550ba-vib' as a fallback compatible >> like this? >> >> properties: >> compatible: >> - enum: >> - - qcom,pm8058-vib >> - - qcom,pm8916-vib >> - - qcom,pm8921-vib >> - - qcom,pmi632-vib >> - - qcom,pm7250b-vib >> - - qcom,pm7325b-vib >> + oneOf: >> + - enum: >> + - qcom,pm8058-vib >> + - qcom,pm8916-vib >> + - qcom,pm8921-vib >> + - qcom,pmi632-vib >> + - qcom,pm7250b-vib >> + - qcom,pm7325b-vib >> + - items: >> + - enum: >> + - qcom,pm7550ba-vib >> + - const: qcom,pm7325b-vib >> > > Yes I wonder why this approved change turned out to something incorrect in your v3 patch... Best regards, Krzysztof
On 7/27/2023 3:10 PM, Krzysztof Kozlowski wrote: > On 18/07/2023 10:02, Krzysztof Kozlowski wrote: >> On 18/07/2023 09:59, Fenglin Wu wrote: >> >>>>> Just FYI,the change log was updated in the cover letter here: >>>>> https://lore.kernel.org/linux-arm-msm/20230718062639.2339589-1-quic_fenglinw@quicinc.com/T/#m3819b50503ef19e0933a10bf797351a4af35537f >>>>> >>>>> Also the commit text and the driver change were also updated accordingly >>>>> to address your review comment by removing 'pm7550ba-vib' compatible string. >>>> >>>> Removing compatible was never my feedback. Did you read: >>>> https://elixir.bootlin.com/linux/v6.1-rc1/source/Documentation/devicetree/bindings/writing-bindings.rst#L42 >>>> ? >>>> >>> Okay, so do you want me to add 'pm7550ba-vib' as a fallback compatible >>> like this? >>> >>> properties: >>> compatible: >>> - enum: >>> - - qcom,pm8058-vib >>> - - qcom,pm8916-vib >>> - - qcom,pm8921-vib >>> - - qcom,pmi632-vib >>> - - qcom,pm7250b-vib >>> - - qcom,pm7325b-vib >>> + oneOf: >>> + - enum: >>> + - qcom,pm8058-vib >>> + - qcom,pm8916-vib >>> + - qcom,pm8921-vib >>> + - qcom,pmi632-vib >>> + - qcom,pm7250b-vib >>> + - qcom,pm7325b-vib >>> + - items: >>> + - enum: >>> + - qcom,pm7550ba-vib >>> + - const: qcom,pm7325b-vib >>> >> >> Yes > > I wonder why this approved change turned out to something incorrect in > your v3 patch... > Since I got review comments in the driver change and I was told to refactor the driver before adding new HW support. I added the HW type logic in the driver and I was thinking it might be good to add some generic compatible strings to match with the HW type introduced in the driver change. Anyway, I will update it to what you suggested in next patch. > Best regards, > Krzysztof >
On 27/07/2023 09:54, Fenglin Wu wrote: >>>> + - enum: >>>> + - qcom,pm7550ba-vib >>>> + - const: qcom,pm7325b-vib >>>> >>> >>> Yes >> >> I wonder why this approved change turned out to something incorrect in >> your v3 patch... >> > Since I got review comments in the driver change and I was told to > refactor the driver before adding new HW support. I added the HW type > logic in the driver and I was thinking it might be good to add some > generic compatible strings to match with the HW type introduced in the > driver change. > > Anyway, I will update it to what you suggested in next patch. Drivers are not really related to bindings, so whatever HW type you add in driver, is not a reason to change bindings. Reason to change bindings could be for example: because hardware is like that. Best regards, Krzysztof
On 7/27/2023 4:29 PM, Krzysztof Kozlowski wrote: > On 27/07/2023 09:54, Fenglin Wu wrote: >>>>> + - enum: >>>>> + - qcom,pm7550ba-vib >>>>> + - const: qcom,pm7325b-vib >>>>> >>>> >>>> Yes >>> >>> I wonder why this approved change turned out to something incorrect in >>> your v3 patch... >>> >> Since I got review comments in the driver change and I was told to >> refactor the driver before adding new HW support. I added the HW type >> logic in the driver and I was thinking it might be good to add some >> generic compatible strings to match with the HW type introduced in the >> driver change. >> >> Anyway, I will update it to what you suggested in next patch. > > Drivers are not really related to bindings, so whatever HW type you add > in driver, is not a reason to change bindings. Reason to change bindings > could be for example: because hardware is like that. > Understood. Sorry, I forgot to mention, in v3, I added the 'reg' value to the register offset and no longer hard code the 16-bit register address, that makes the vibrators inside PMI632/PM7250B/PM7325B/PM7550BA all compatible, and that was another motivation of adding a generic compatible string and make the others as the fallback. This will be still the case in v4, I might keep it similar in v3 but just drop "qcom,spmi-vib-gen1" > Best regards, > Krzysztof >
diff --git a/Documentation/devicetree/bindings/input/qcom,pm8xxx-vib.yaml b/Documentation/devicetree/bindings/input/qcom,pm8xxx-vib.yaml index c8832cd0d7da..481163105d24 100644 --- a/Documentation/devicetree/bindings/input/qcom,pm8xxx-vib.yaml +++ b/Documentation/devicetree/bindings/input/qcom,pm8xxx-vib.yaml @@ -15,6 +15,9 @@ properties: - qcom,pm8058-vib - qcom,pm8916-vib - qcom,pm8921-vib + - qcom,pmi632-vib + - qcom,pm7250b-vib + - qcom,pm7325b-vib reg: maxItems: 1