From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 6ABAFC433F5 for ; Mon, 15 Nov 2021 06:38:40 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 52DE461B3D for ; Mon, 15 Nov 2021 06:38:40 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229733AbhKOGlb (ORCPT ); Mon, 15 Nov 2021 01:41:31 -0500 Received: from alexa-out.qualcomm.com ([129.46.98.28]:39526 "EHLO alexa-out.qualcomm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229648AbhKOGlb (ORCPT ); Mon, 15 Nov 2021 01:41:31 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=quicinc.com; i=@quicinc.com; q=dns/txt; s=qcdkim; t=1636958316; x=1668494316; h=message-id:date:mime-version:subject:from:to:cc: references:in-reply-to:content-transfer-encoding; bh=ZCdyBfPAycYXHOAPOEAo6conMb52KuZIsOmNlhXRFuI=; b=miRt6fTqv2Osk0dskAKsjeviUlkk1ikXfsBOCERP119AhuOzcwl/FSvG R/73/i5hVbUFFxNzYAYmu7PoO5UHyxG9m2y2jelu/1Xp3V7KrYW+aifR2 Vyqo71vs3kbHbiqFKUA7LPhrZYTp2wZyAbvXAptozNICW7q7iRGCDaeZs 4=; Received: from ironmsg09-lv.qualcomm.com ([10.47.202.153]) by alexa-out.qualcomm.com with ESMTP; 14 Nov 2021 22:38:36 -0800 X-QCInternal: smtphost Received: from nasanex01c.na.qualcomm.com ([10.47.97.222]) by ironmsg09-lv.qualcomm.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 14 Nov 2021 22:38:35 -0800 Received: from nalasex01c.na.qualcomm.com (10.47.97.35) by nasanex01c.na.qualcomm.com (10.47.97.222) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.922.19; Sun, 14 Nov 2021 22:38:34 -0800 Received: from [10.231.205.174] (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.922.19; Sun, 14 Nov 2021 22:38:30 -0800 Message-ID: Date: Mon, 15 Nov 2021 14:38:28 +0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.3.0 Subject: Re: [RESEND PATCH v2 11/11] dt-bindings: convert qcom,spmi-pmic-arb binding to YAML format Content-Language: en-US From: Fenglin Wu To: Rob Herring CC: Rob Herring , , Bjorn Andersson , , , Andy Gross , , , , , References: <1636691059-4305-1-git-send-email-quic_fenglinw@quicinc.com> <1636691059-4305-12-git-send-email-quic_fenglinw@quicinc.com> <1636724917.088909.2463363.nullmailer@robh.at.kernel.org> In-Reply-To: Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 8bit X-Originating-IP: [10.80.80.8] X-ClientProxiedBy: nasanex01b.na.qualcomm.com (10.46.141.250) To nalasex01c.na.qualcomm.com (10.47.97.35) Precedence: bulk List-ID: X-Mailing-List: linux-arm-msm@vger.kernel.org On 2021/11/15 8:16, Fenglin Wu wrote: > > On 2021/11/12 21:48, Rob Herring wrote: >> On Fri, 12 Nov 2021 12:24:19 +0800, Fenglin Wu wrote: >>> Convert the SPMI PMIC arbiter documentation to JSON/yaml. >>> >>> Signed-off-by: Fenglin Wu >>> --- >>>   .../bindings/spmi/qcom,spmi-pmic-arb.txt           |  67 ----------- >>>   .../bindings/spmi/qcom,spmi-pmic-arb.yaml          | 122 >>> +++++++++++++++++++++ >>>   2 files changed, 122 insertions(+), 67 deletions(-) >>>   delete mode 100644 >>> Documentation/devicetree/bindings/spmi/qcom,spmi-pmic-arb.txt >>>   create mode 100644 >>> Documentation/devicetree/bindings/spmi/qcom,spmi-pmic-arb.yaml >>> >> My bot found errors running 'make DT_CHECKER_FLAGS=-m dt_binding_check' >> on your patch (DT_CHECKER_FLAGS is new in v5.13): >> >> yamllint warnings/errors: >> >> dtschema/dtc warnings/errors: >> /builds/robherring/linux-dt-review/Documentation/devicetree/bindings/spmi/qcom,spmi-pmic-arb.yaml: >> properties:interrupt-names: 'const' should not be valid under >> {'enum': ['const', 'enum', 'exclusiveMaximum', 'exclusiveMinimum', >> 'minimum', 'maximum', 'multipleOf', 'pattern']} >>     hint: Scalar and array keywords cannot be mixed >>     from schema $id: http://devicetree.org/meta-schemas/keywords.yaml# >> /builds/robherring/linux-dt-review/Documentation/devicetree/bindings/spmi/qcom,spmi-pmic-arb.yaml: >> properties:reg-names: {'minItems': 3, 'maxItems': 5, 'items': >> [{'const': 'core'}, {'const': 'intr'}, {'const': 'cnfg'}, {'const': >> 'chnls'}, {'const': 'obsrvr'}]} should not be valid under >> {'required': ['maxItems']} >>     hint: "maxItems" is not needed with an "items" list >>     from schema $id: http://devicetree.org/meta-schemas/items.yaml# >> /builds/robherring/linux-dt-review/Documentation/devicetree/bindings/spmi/qcom,spmi-pmic-arb.yaml: >> ignoring, error in schema: properties: interrupt-names >> warning: no schema found in file: >> ./Documentation/devicetree/bindings/spmi/qcom,spmi-pmic-arb.yaml >> /builds/robherring/linux-dt-review/Documentation/devicetree/bindings/spmi/qcom,spmi-pmic-arb.example.dt.yaml: >> spmi@fc4cf000: reg: [[4232900608, 4096], [4232884224, 4096], >> [4232880128, 4096]] is too long >>     From schema: >> /builds/robherring/linux-dt-review/Documentation/devicetree/bindings/spmi/spmi.yaml >> Documentation/devicetree/bindings/spmi/qcom,spmi-pmic-arb.example.dt.yaml:0:0: >> /example-0/spmi@fc4cf000: failed to match any schema with compatible: >> ['qcom,spmi-pmic-arb'] >> >> doc reference errors (make refcheckdocs): >> Documentation/devicetree/bindings/mfd/qcom,spmi-pmic.txt: >> Documentation/devicetree/bindings/spmi/qcom,spmi-pmic-arb.txt >> >> See https://patchwork.ozlabs.org/patch/1554141 >> >> This check can fail if there are any dependencies. The base for a patch >> series is generally the most recent rc1. >> >> If you already ran 'make dt_binding_check' and didn't see the above >> error(s), then make sure 'yamllint' is installed and dt-schema is up to >> date: >> >> pip3 install dtschema --upgrade >> >> Please check and re-submit. > I actually ran "make dt-binding-check > DT_SCHEMA_FILES=Documentation/devicetree/bindings/qcom,spmi-pmic-arb.txt" > and confirmed there was no error or warning before pushing the change. > Anyway I will follow > your steps here andcheck it again, if any changes is required, I will > have them updated it > in next patchset. > Thanks I could see the same warning message after installed 'yamllint'. I will fix this and re-submit. Thanks