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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 55B4DECAAD5 for ; Fri, 2 Sep 2022 18:52:32 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230114AbiIBSwa (ORCPT ); Fri, 2 Sep 2022 14:52:30 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40778 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230018AbiIBSw1 (ORCPT ); Fri, 2 Sep 2022 14:52:27 -0400 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 39756E193A for ; Fri, 2 Sep 2022 11:52:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1662144741; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=FKifGkwx3P3TuJMAxmYdMT5EsvE4i26RC7LZW8MiN3w=; b=RqCMxc7A6M+WQliWySVrQMBkWOpMMXEtut8hQ2xbmSNOseu39QWalPt1LjrZ88EPzsYvX9 gUpMJMHF778qXRVdOwq4chtMiRhUTTi7xFIZK9FX8cYKdPfNjfQBojxTHb4bwZlTXi8E0t hvjKOCOzNtZhKLExhrfZw+lPJfYK8sQ= Received: from mail-qv1-f72.google.com (mail-qv1-f72.google.com [209.85.219.72]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_128_GCM_SHA256) id us-mta-457-97ftozHLOqGz0_TmfMOtGQ-1; Fri, 02 Sep 2022 14:52:20 -0400 X-MC-Unique: 97ftozHLOqGz0_TmfMOtGQ-1 Received: by mail-qv1-f72.google.com with SMTP id o6-20020ad443c6000000b00495d04028a6so1809822qvs.18 for ; Fri, 02 Sep 2022 11:52:20 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:x-gm-message-state:from:to:cc:subject:date; bh=FKifGkwx3P3TuJMAxmYdMT5EsvE4i26RC7LZW8MiN3w=; b=V0tsPzMqnvjOQRp9tD2KLkOHgk3HxwubljM38xiC8MDBncMygLwTA5jGqb4bxOOHc/ qj9WW8pEFNeWktvyljsWJnYC6Z25Efw9/K9rN1ZY2x2YGLAGNqmhdaXg/jwRboQ5p/NE CosuGfyenNWlYg3l98ssgxLbHyGZJ25dP4+nUvb9m4mjs1/raPBHShhvF7C79HZM4jc0 EibvqE62S+JtVQsPl6R1wk9xxpAob3pKFGInqgxDJGyv1Y7PkmrJ20AnOwOmYxLYza+Q VaXj+qbNrdEpzN1yxQGhPcuEaFJadpC4AwQbAt5N7pkhSFeW0j8hxvgdAYrzRVRgktkO wN9g== X-Gm-Message-State: ACgBeo2AU+D/BBpVLf9Jc0lErKrwf+Bo5tZitpTAQ3Lthlmbw9NfT19f ysioV8VFESm1tash9FbpyUUnyfO2rLmUET4pAQIn1JSGchuKOGQ1vQKcXYhZhfGXT8zPnVYU3qA Fa2lWiUFIeBBE5evzBovH5Mdi X-Received: by 2002:a05:622a:347:b0:343:602e:d1eb with SMTP id r7-20020a05622a034700b00343602ed1ebmr30532910qtw.78.1662144739952; Fri, 02 Sep 2022 11:52:19 -0700 (PDT) X-Google-Smtp-Source: AA6agR7tr9tS9qizyb79IxvlKkdB/Ye4dB5nps3mXFW4VQaBEhppeQgaHWU/cJf5tnPkK9ymaGO74g== X-Received: by 2002:a05:622a:347:b0:343:602e:d1eb with SMTP id r7-20020a05622a034700b00343602ed1ebmr30532895qtw.78.1662144739744; Fri, 02 Sep 2022 11:52:19 -0700 (PDT) Received: from halaneylaptop.redhat.com ([2600:1700:1ff0:d0e0::48]) by smtp.gmail.com with ESMTPSA id j4-20020ac874c4000000b0031ef0081d77sm1403168qtr.79.2022.09.02.11.52.18 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 02 Sep 2022 11:52:19 -0700 (PDT) From: Andrew Halaney To: agross@kernel.org, andersson@kernel.org, konrad.dybcio@somainline.org, lgirdwood@gmail.com, broonie@kernel.org, robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org Cc: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, dianders@chromium.org, johan@kernel.org, Andrew Halaney Subject: [PATCH 0/3] regulator: dt-bindings: qcom,rpmh: dt-binding fixups Date: Fri, 2 Sep 2022 13:51:45 -0500 Message-Id: <20220902185148.635292-1-ahalaney@redhat.com> X-Mailer: git-send-email 2.37.2 MIME-Version: 1.0 Content-type: text/plain Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, This is my poor attempt at getting devicetree validation into a better state for qcom,rpmh-regulator.yaml. This is a follow-up to Johan's request for this over here: https://lore.kernel.org/linux-arm-msm/Yw8EE%2FESDUnIRf8P@hovoldconsulting.com/ In particular, I'm not certain patch 1 is the correct way to handle things, and patch 2 makes validation too wide for the *-supply nodes. I'd love any feedback here as I'm really not experienced in any of the spaces (regulator, rpmh, or dt schema) so nit picking is welcomed. Thanks in advance, Andrew Andrew Halaney (3): regulator: dt-bindings: qcom,rpmh: Use additionalProperties regulator: dt-bindings: qcom,rpmh: Specify supply property regulator: dt-bindings: qcom,rpmh: Indicate regulator-allow-set-load dependencies .../bindings/regulator/qcom,rpmh-regulator.yaml | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) -- 2.37.2