Message ID | 20230727113136.98037-1-antoniu.miclaus@analog.com |
---|---|
State | New |
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a59:a985:0:b0:3e4:2afc:c1 with SMTP id t5csp1048537vqo; Thu, 27 Jul 2023 05:07:19 -0700 (PDT) X-Google-Smtp-Source: APBJJlHOhQqLtaw4vysY6vt6vy8MSB2OpEWzCzG3Ph3ruSjd18zNjCQCKQCUVgFKNw0swPO4D3it X-Received: by 2002:a17:902:6b0c:b0:1bb:a4db:9466 with SMTP id o12-20020a1709026b0c00b001bba4db9466mr3842098plk.4.1690459639086; Thu, 27 Jul 2023 05:07:19 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1690459639; cv=none; d=google.com; s=arc-20160816; b=D/FyraoQsNF37bZeNWnfZ3vvOrBdL9IAvaCIK6I5iiLyzkDTjc9c4906zjhE618bqY GA/gr0NT6p4f+4QyS0cFmSNJ66jEJYztUAuSaxJ52Hk49HMZABUPHThfOGuEF3/UIUgx 3CkSnx+cfEtxWleOJ62eKMTQ0EdPYBQHeAPM9rmI+FJve74sRDeW1zzk9FByrsv8Xilk BXTlpKUuws1Nzt1D1VngRDhmJroiUFhXhjvZWL/o4tdRP45knVsUN45HpuxmEr0duslP 3vjjGO/it5/nt61NgvWcpdX899lGhfZpGbLy+K1mHPE4S8l5CJcFFDDbbt3o5WIKxHBq QvxA== 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 :message-id:date:subject:cc:to:from; bh=vrRw4IlOkXDBI/FSP8CSeBGm0VrMi3JMbaH4vvojZco=; fh=UzJefE9RYbLi18kqdyRDF9Ifql1AQscxes0LCEBfz7A=; b=jYzVwaPJ79elPVnj445rF6KDRolFrDzU4dlA0R7Mue3CKI6KVRqaIO2N9I205ruQuC Qkjxxa7P9TImQwcFvSIcVHj+5eGbGgSZKICkeKIdE6yrixZw8ddVeGp6cmbgvw4aVAsk Bf0ZTUkWxDWAYFS3vhLTwm8y7gU95KcM/e8KDbl3EeDMptsA96fsHJO80Wjmi3L/IwCJ lcKfjDM+whP2HqhEVLLU0x3WqOBagsvttxQaNA7ehu7LYRbl7vP+mGy37O/rg5uF3ZEu P9RbTahPEpl/G+4dXcGBy/CmURlkOvehOoyNuGD0SOJcAd8zjwE13lCPZ7f8fJu2kNiq urUQ== ARC-Authentication-Results: i=1; mx.google.com; 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=fail (p=NONE sp=NONE dis=NONE) header.from=analog.com Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id q1-20020a170902f34100b001b8698149f2si1110202ple.588.2023.07.27.05.07.05; Thu, 27 Jul 2023 05:07:19 -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; 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=fail (p=NONE sp=NONE dis=NONE) header.from=analog.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232704AbjG0Ld4 (ORCPT <rfc822;hanasaki@gmail.com> + 99 others); Thu, 27 Jul 2023 07:33:56 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:59150 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232688AbjG0Ldw (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Thu, 27 Jul 2023 07:33:52 -0400 Received: from mx0a-00128a01.pphosted.com (mx0a-00128a01.pphosted.com [148.163.135.77]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D7FC930D2; Thu, 27 Jul 2023 04:33:22 -0700 (PDT) Received: from pps.filterd (m0167088.ppops.net [127.0.0.1]) by mx0a-00128a01.pphosted.com (8.17.1.19/8.17.1.19) with ESMTP id 36RAS5dU027907; Thu, 27 Jul 2023 07:32:47 -0400 Received: from nwd2mta3.analog.com ([137.71.173.56]) by mx0a-00128a01.pphosted.com (PPS) with ESMTPS id 3s36afnwne-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 27 Jul 2023 07:32:47 -0400 Received: from ASHBMBX9.ad.analog.com (ASHBMBX9.ad.analog.com [10.64.17.10]) by nwd2mta3.analog.com (8.14.7/8.14.7) with ESMTP id 36RBWjQW020585 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Thu, 27 Jul 2023 07:32:45 -0400 Received: from ASHBCASHYB5.ad.analog.com (10.64.17.133) by ASHBMBX9.ad.analog.com (10.64.17.10) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.986.14; Thu, 27 Jul 2023 07:32:45 -0400 Received: from ASHBMBX9.ad.analog.com (10.64.17.10) by ASHBCASHYB5.ad.analog.com (10.64.17.133) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.986.14; Thu, 27 Jul 2023 07:32:44 -0400 Received: from zeus.spd.analog.com (10.66.68.11) by ashbmbx9.ad.analog.com (10.64.17.10) with Microsoft SMTP Server id 15.2.986.14 via Frontend Transport; Thu, 27 Jul 2023 07:32:44 -0400 Received: from amiclaus-VirtualBox.ad.analog.com (AMICLAUS-L02.ad.analog.com [10.48.65.194]) by zeus.spd.analog.com (8.15.1/8.15.1) with ESMTP id 36RBWW9v002437; Thu, 27 Jul 2023 07:32:35 -0400 From: Antoniu Miclaus <antoniu.miclaus@analog.com> To: <jic23@kernel.org>, <robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>, <conor+dt@kernel.org>, <linux-iio@vger.kernel.org>, <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org> CC: Antoniu Miclaus <antoniu.miclaus@analog.com> Subject: [PATCH] dt-bindings: iio: admv1014: make all regs required Date: Thu, 27 Jul 2023 14:31:36 +0300 Message-ID: <20230727113136.98037-1-antoniu.miclaus@analog.com> X-Mailer: git-send-email 2.41.0 MIME-Version: 1.0 Content-Transfer-Encoding: 7BIT Content-Type: text/plain; charset=US-ASCII X-ADIRuleOP-NewSCL: Rule Triggered X-Proofpoint-GUID: 9hsAOHESWceFUClmJ-0KWETFK0YDujT2 X-Proofpoint-ORIG-GUID: 9hsAOHESWceFUClmJ-0KWETFK0YDujT2 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-27_06,2023-07-26_01,2023-05-22_02 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 phishscore=0 suspectscore=0 mlxscore=0 bulkscore=0 mlxlogscore=935 clxscore=1015 spamscore=0 impostorscore=0 adultscore=0 lowpriorityscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2306200000 definitions=main-2307270102 X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE 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: 1772575406644373877 X-GMAIL-MSGID: 1772575406644373877 |
Series |
dt-bindings: iio: admv1014: make all regs required
|
|
Commit Message
Antoniu Miclaus
July 27, 2023, 11:31 a.m. UTC
Since the regulators are required in the driver implementation, make
them required also in the bindings.
Signed-off-by: Antoniu Miclaus <antoniu.miclaus@analog.com>
---
.../devicetree/bindings/iio/frequency/adi,admv1014.yaml | 8 ++++++++
1 file changed, 8 insertions(+)
Comments
On 27/07/2023 13:31, Antoniu Miclaus wrote: > Since the regulators are required in the driver implementation, make > them required also in the bindings. > The true reason should be whether the hardware requires them. Because if hardware does not need some, the driver should be fixed. Best regards, Krzysztof
> -----Original Message----- > From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> > Sent: Thursday, July 27, 2023 2:47 PM > To: Miclaus, Antoniu <Antoniu.Miclaus@analog.com>; jic23@kernel.org; > robh+dt@kernel.org; krzysztof.kozlowski+dt@linaro.org; > conor+dt@kernel.org; linux-iio@vger.kernel.org; > devicetree@vger.kernel.org; linux-kernel@vger.kernel.org > Subject: Re: [PATCH] dt-bindings: iio: admv1014: make all regs required > > [External] > > On 27/07/2023 13:31, Antoniu Miclaus wrote: > > Since the regulators are required in the driver implementation, make > > them required also in the bindings. > > > > The true reason should be whether the hardware requires them. Because if > hardware does not need some, the driver should be fixed. The datasheet is not very explicit on this topic, but all the specifications of the part are built around these pins being supplied. Moreover, the evaluation board or the part comes with all VCC pins connected to fixed supplies. > Best regards, > Krzysztof
On Thu, 27 Jul 2023 12:02:04 +0000 "Miclaus, Antoniu" <Antoniu.Miclaus@analog.com> wrote: > > -----Original Message----- > > From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> > > Sent: Thursday, July 27, 2023 2:47 PM > > To: Miclaus, Antoniu <Antoniu.Miclaus@analog.com>; jic23@kernel.org; > > robh+dt@kernel.org; krzysztof.kozlowski+dt@linaro.org; > > conor+dt@kernel.org; linux-iio@vger.kernel.org; > > devicetree@vger.kernel.org; linux-kernel@vger.kernel.org > > Subject: Re: [PATCH] dt-bindings: iio: admv1014: make all regs required > > > > [External] > > > > On 27/07/2023 13:31, Antoniu Miclaus wrote: > > > Since the regulators are required in the driver implementation, make > > > them required also in the bindings. This bit is probably not strictly true. Try no providing them and you will probably find stub regulators created on assumption they are fixed regs that we aren't interested in controlling. > > > > > > > The true reason should be whether the hardware requires them. Because if > > hardware does not need some, the driver should be fixed. > The datasheet is not very explicit on this topic, but all the specifications of the > part are built around these pins being supplied. > Moreover, the evaluation board or the part comes with all VCC pins connected > to fixed supplies. Agreed - these should be required in the binding. There was an old disagreement on this in which it they were not marked required in some bindings because the regulator subsystem would assume they were fixed supplies that were just missing in the DT and so provides stub regulators. My understanding at least has changed and now we mark the required even if the driver works fine on some boards without them being supplied. Note though that this means the whole of trivial-devices.yaml is garbage as very few devices actually work without any power :) Jonathan > > Best regards, > > Krzysztof >
> -----Original Message----- > From: Jonathan Cameron <jic23@kernel.org> > Sent: Saturday, July 29, 2023 2:55 PM > To: Miclaus, Antoniu <Antoniu.Miclaus@analog.com> > Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>; > robh+dt@kernel.org; krzysztof.kozlowski+dt@linaro.org; > conor+dt@kernel.org; linux-iio@vger.kernel.org; > devicetree@vger.kernel.org; linux-kernel@vger.kernel.org > Subject: Re: [PATCH] dt-bindings: iio: admv1014: make all regs required > > [External] > > On Thu, 27 Jul 2023 12:02:04 +0000 > "Miclaus, Antoniu" <Antoniu.Miclaus@analog.com> wrote: > > > > -----Original Message----- > > > From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> > > > Sent: Thursday, July 27, 2023 2:47 PM > > > To: Miclaus, Antoniu <Antoniu.Miclaus@analog.com>; jic23@kernel.org; > > > robh+dt@kernel.org; krzysztof.kozlowski+dt@linaro.org; > > > conor+dt@kernel.org; linux-iio@vger.kernel.org; > > > devicetree@vger.kernel.org; linux-kernel@vger.kernel.org > > > Subject: Re: [PATCH] dt-bindings: iio: admv1014: make all regs required > > > > > > [External] > > > > > > On 27/07/2023 13:31, Antoniu Miclaus wrote: > > > > Since the regulators are required in the driver implementation, make > > > > them required also in the bindings. > > This bit is probably not strictly true. Try no providing them and you will > probably find stub regulators created on assumption they are fixed regs > that we aren't interested in controlling. > > > > > > > > > > > The true reason should be whether the hardware requires them. > Because if > > > hardware does not need some, the driver should be fixed. > > The datasheet is not very explicit on this topic, but all the specifications of > the > > part are built around these pins being supplied. > > Moreover, the evaluation board or the part comes with all VCC pins > connected > > to fixed supplies. > > Agreed - these should be required in the binding. > Hello Jonathan, Not sure if I fully understand. Should I drop this patch? And also drop the "required" of the regulators in the admv1013 patch? https://patchwork.kernel.org/project/linux-iio/patch/20230727110121.93546-1-antoniu.miclaus@analog.com/ Thanks, > There was an old disagreement on this in which it they were not marked > required in some bindings because the regulator subsystem would assume > they > were fixed supplies that were just missing in the DT and so provides stub > regulators. > My understanding at least has changed and now we mark the required even > if > the driver works fine on some boards without them being supplied. > > Note though that this means the whole of trivial-devices.yaml is garbage > as very few devices actually work without any power :) > > Jonathan > > > > > > Best regards, > > > Krzysztof > >
On Mon, 31 Jul 2023 07:40:14 +0000 "Miclaus, Antoniu" <Antoniu.Miclaus@analog.com> wrote: > > -----Original Message----- > > From: Jonathan Cameron <jic23@kernel.org> > > Sent: Saturday, July 29, 2023 2:55 PM > > To: Miclaus, Antoniu <Antoniu.Miclaus@analog.com> > > Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>; > > robh+dt@kernel.org; krzysztof.kozlowski+dt@linaro.org; > > conor+dt@kernel.org; linux-iio@vger.kernel.org; > > devicetree@vger.kernel.org; linux-kernel@vger.kernel.org > > Subject: Re: [PATCH] dt-bindings: iio: admv1014: make all regs required > > > > [External] > > > > On Thu, 27 Jul 2023 12:02:04 +0000 > > "Miclaus, Antoniu" <Antoniu.Miclaus@analog.com> wrote: > > > > > > -----Original Message----- > > > > From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> > > > > Sent: Thursday, July 27, 2023 2:47 PM > > > > To: Miclaus, Antoniu <Antoniu.Miclaus@analog.com>; jic23@kernel.org; > > > > robh+dt@kernel.org; krzysztof.kozlowski+dt@linaro.org; > > > > conor+dt@kernel.org; linux-iio@vger.kernel.org; > > > > devicetree@vger.kernel.org; linux-kernel@vger.kernel.org > > > > Subject: Re: [PATCH] dt-bindings: iio: admv1014: make all regs required > > > > > > > > [External] > > > > > > > > On 27/07/2023 13:31, Antoniu Miclaus wrote: > > > > > Since the regulators are required in the driver implementation, make > > > > > them required also in the bindings. > > > > This bit is probably not strictly true. Try no providing them and you will > > probably find stub regulators created on assumption they are fixed regs > > that we aren't interested in controlling. > > > > > > > > > > > > > > > The true reason should be whether the hardware requires them. > > Because if > > > > hardware does not need some, the driver should be fixed. > > > The datasheet is not very explicit on this topic, but all the specifications of > > the > > > part are built around these pins being supplied. > > > Moreover, the evaluation board or the part comes with all VCC pins > > connected > > > to fixed supplies. > > > > Agreed - these should be required in the binding. > > > Hello Jonathan, > > Not sure if I fully understand. Should I drop this patch? Patch is good. The binding should state these are required - it doesn't mean that the driver will fail to probe on systems that doesn't provide them. It does encourage any new DTS files to incorporate them which is good to have. Only thing that needs changing is the patch should not justify the addition of these to the binding because they 'are required in the driver implementation'. Just drop that statement and the patch is fine. > And also drop the "required" of the regulators in the admv1013 patch? > https://patchwork.kernel.org/project/linux-iio/patch/20230727110121.93546-1-antoniu.miclaus@analog.com/ As long as the patch doesn't say anything about what the driver does then it is fine. Note DT bindings and patch descriptions for them should never mention the driver. Jonathan > > Thanks, > > There was an old disagreement on this in which it they were not marked > > required in some bindings because the regulator subsystem would assume > > they > > were fixed supplies that were just missing in the DT and so provides stub > > regulators. > > My understanding at least has changed and now we mark the required even > > if > > the driver works fine on some boards without them being supplied. > > > > Note though that this means the whole of trivial-devices.yaml is garbage > > as very few devices actually work without any power :) > > > > Jonathan > > > > > > > > > > Best regards, > > > > Krzysztof > > > >
> -----Original Message----- > From: Jonathan Cameron <Jonathan.Cameron@Huawei.com> > Sent: Monday, July 31, 2023 1:13 PM > To: Miclaus, Antoniu <Antoniu.Miclaus@analog.com> > Cc: Jonathan Cameron <jic23@kernel.org>; Krzysztof Kozlowski > <krzysztof.kozlowski@linaro.org>; robh+dt@kernel.org; > krzysztof.kozlowski+dt@linaro.org; conor+dt@kernel.org; linux- > iio@vger.kernel.org; devicetree@vger.kernel.org; linux- > kernel@vger.kernel.org > Subject: Re: [PATCH] dt-bindings: iio: admv1014: make all regs required > > [External] > > On Mon, 31 Jul 2023 07:40:14 +0000 > "Miclaus, Antoniu" <Antoniu.Miclaus@analog.com> wrote: > > > > -----Original Message----- > > > From: Jonathan Cameron <jic23@kernel.org> > > > Sent: Saturday, July 29, 2023 2:55 PM > > > To: Miclaus, Antoniu <Antoniu.Miclaus@analog.com> > > > Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>; > > > robh+dt@kernel.org; krzysztof.kozlowski+dt@linaro.org; > > > conor+dt@kernel.org; linux-iio@vger.kernel.org; > > > devicetree@vger.kernel.org; linux-kernel@vger.kernel.org > > > Subject: Re: [PATCH] dt-bindings: iio: admv1014: make all regs required > > > > > > [External] > > > > > > On Thu, 27 Jul 2023 12:02:04 +0000 > > > "Miclaus, Antoniu" <Antoniu.Miclaus@analog.com> wrote: > > > > > > > > -----Original Message----- > > > > > From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> > > > > > Sent: Thursday, July 27, 2023 2:47 PM > > > > > To: Miclaus, Antoniu <Antoniu.Miclaus@analog.com>; > jic23@kernel.org; > > > > > robh+dt@kernel.org; krzysztof.kozlowski+dt@linaro.org; > > > > > conor+dt@kernel.org; linux-iio@vger.kernel.org; > > > > > devicetree@vger.kernel.org; linux-kernel@vger.kernel.org > > > > > Subject: Re: [PATCH] dt-bindings: iio: admv1014: make all regs > required > > > > > > > > > > [External] > > > > > > > > > > On 27/07/2023 13:31, Antoniu Miclaus wrote: > > > > > > Since the regulators are required in the driver implementation, > make > > > > > > them required also in the bindings. > > > > > > This bit is probably not strictly true. Try no providing them and you will > > > probably find stub regulators created on assumption they are fixed regs > > > that we aren't interested in controlling. > > > > > > > > > > > > > > > > > > > The true reason should be whether the hardware requires them. > > > Because if > > > > > hardware does not need some, the driver should be fixed. > > > > The datasheet is not very explicit on this topic, but all the specifications > of > > > the > > > > part are built around these pins being supplied. > > > > Moreover, the evaluation board or the part comes with all VCC pins > > > connected > > > > to fixed supplies. > > > > > > Agreed - these should be required in the binding. > > > > > Hello Jonathan, > > > > Not sure if I fully understand. Should I drop this patch? > > Patch is good. The binding should state these are required - it doesn't > mean that the driver will fail to probe on systems that doesn't provide > them. It does encourage any new DTS files to incorporate them which is > good to have. > > Only thing that needs changing is the patch should not justify the > addition of these to the binding because they 'are required in the > driver implementation'. Just drop that statement and the patch is > fine. Great, thanks a lot for the clarification. > > > > > And also drop the "required" of the regulators in the admv1013 patch? > > https://urldefense.com/v3/__https://patchwork.kernel.org/project/linux- > iio/patch/20230727110121.93546-1- > antoniu.miclaus@analog.com/__;!!A3Ni8CS0y2Y!8dQigVuPYwGwS53vsq2RO > CJx3RgfeZW4GZks5EFWhfUlJZTdAvsCr5MGlrWUVHXwqRKoASc4UBEFE8h6N > KO6jrfSQ-oKjKtS$ > > As long as the patch doesn't say anything about what the driver does > then it is fine. Note DT bindings and patch descriptions for them should > never mention the driver. > > Jonathan > > > > > Thanks, > > > There was an old disagreement on this in which it they were not marked > > > required in some bindings because the regulator subsystem would > assume > > > they > > > were fixed supplies that were just missing in the DT and so provides stub > > > regulators. > > > My understanding at least has changed and now we mark the required > even > > > if > > > the driver works fine on some boards without them being supplied. > > > > > > Note though that this means the whole of trivial-devices.yaml is garbage > > > as very few devices actually work without any power :) > > > > > > Jonathan > > > > > > > > > > > > > > Best regards, > > > > > Krzysztof > > > > > >
diff --git a/Documentation/devicetree/bindings/iio/frequency/adi,admv1014.yaml b/Documentation/devicetree/bindings/iio/frequency/adi,admv1014.yaml index ab86daa2c56e..8e4c5ff0da14 100644 --- a/Documentation/devicetree/bindings/iio/frequency/adi,admv1014.yaml +++ b/Documentation/devicetree/bindings/iio/frequency/adi,admv1014.yaml @@ -103,6 +103,14 @@ required: - clocks - clock-names - vcm-supply + - vcc-if-bb-supply + - vcc-vga-supply + - vcc-vva-supply + - vcc-lna-3p3-supply + - vcc-lna-1p5-supply + - vcc-bg-supply + - vcc-quad-supply + - vcc-mixer-supply allOf: - $ref: /schemas/spi/spi-peripheral-props.yaml#