From nobody Tue Feb 10 19:47:51 2026 Received: from mx0a-0031df01.pphosted.com (mx0a-0031df01.pphosted.com [205.220.168.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 6B733369211 for ; Mon, 9 Feb 2026 10:55:50 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=205.220.168.131 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1770634550; cv=none; b=i4FNsTPei0cnnm5dgUZHBz24UI7AqdyFonIPG/Kh8RDurpLuNeQUgcyuyYnhyx+hVzSQ0OLStDoskJQHlVO0ikS4uDhr50rPYuweultd1JUsaFVPZHn+DkS+OP0+F5UskWdDPZlvSI8F6mAxrFIYyc6X6I41+4T/kOKxurUb/LM= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1770634550; c=relaxed/simple; bh=CbgzOaYDkc3bXhiSUZkzlP8DjhXVBP0eRFGEsmWlQbQ=; h=From:To:Cc:Subject:Date:Message-Id:In-Reply-To:References: MIME-Version; b=SCLAwrz5Om7qOcEUSI716o21kIwsXjuDFetjcNeWZytMy5UuqhxKf++jSFbvBYa0HTCSMLSorm2KYp9uKMr14qRabBjNPGbBd/Hbo9A3OyiYEoWSOQLNb7pU3qdKX4YZTvM6sa56sYGUw0G4SN8AGzxhfuZ2I5c7VGd6R4+z3sU= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=oss.qualcomm.com; spf=pass smtp.mailfrom=oss.qualcomm.com; dkim=pass (2048-bit key) header.d=qualcomm.com header.i=@qualcomm.com header.b=EaGnhjyn; dkim=pass (2048-bit key) header.d=oss.qualcomm.com header.i=@oss.qualcomm.com header.b=Iy1+d6bd; arc=none smtp.client-ip=205.220.168.131 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=oss.qualcomm.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=oss.qualcomm.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=qualcomm.com header.i=@qualcomm.com header.b="EaGnhjyn"; dkim=pass (2048-bit key) header.d=oss.qualcomm.com header.i=@oss.qualcomm.com header.b="Iy1+d6bd" Received: from pps.filterd (m0279866.ppops.net [127.0.0.1]) by mx0a-0031df01.pphosted.com (8.18.1.11/8.18.1.11) with ESMTP id 6199sG6I1656554 for ; Mon, 9 Feb 2026 10:55:49 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=qualcomm.com; h= cc:content-transfer-encoding:date:from:in-reply-to:message-id :mime-version:references:subject:to; s=qcppdkim1; bh=yRCNcS5A6Eu GBIPJ6FqXwxvOo4jjK2JrobpZz5iBr1c=; b=EaGnhjynxwxGDxaeTfIhd+3ucdy noXSA1xcorxYnDt4TTn1wyLkaVJsGzGr46Nu31R7f1W31YS53Qt/ylJRC8lz+kLF iUIbn1jYUDf4Cdf0kK4G6z/aBM41hekItoBkeT51Iqyf1W7veH5Ow5qK2yxKE7Tj oLR1GBHVZ3OHrtcY4kHHm1JTLXm6pNeZQkbKGuzdg11voJHIol/OuWK46AxCb/AL //jRqcPpn5zXDi8uC0gnMjyJrTMcvRya8/+4JGSnMLhdOouG6jVFsHS6jAJ+oBI5 3I0Pm9MB86OmJwcHhQUxskWjJYZ67V904CXQfKxVgClTEFPkpEOCqG80b9w== Received: from mail-pj1-f72.google.com (mail-pj1-f72.google.com [209.85.216.72]) by mx0a-0031df01.pphosted.com (PPS) with ESMTPS id 4c7862sbe3-1 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NOT) for ; Mon, 09 Feb 2026 10:55:49 +0000 (GMT) Received: by mail-pj1-f72.google.com with SMTP id 98e67ed59e1d1-352de7a89e1so3646920a91.1 for ; Mon, 09 Feb 2026 02:55:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oss.qualcomm.com; s=google; t=1770634549; x=1771239349; darn=vger.kernel.org; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:from:to:cc:subject:date :message-id:reply-to; bh=yRCNcS5A6EuGBIPJ6FqXwxvOo4jjK2JrobpZz5iBr1c=; b=Iy1+d6bdTS+3iC3TSfomerkTbSLl/0aLabPjVtLemE94kszvapxO53vt0qypqzl+WE ifB051ee9/0n47JWjHZCUH11Vomomi+oYnug4NHv2w5WOmPzPDuf19+DFsEiM1fPDeJp b4iA3nTBqfICyr0JstYNhAEMKqdNJ/gHbu9B0OG5WKxVQFfYmeFM/REVkWnjg1NvpEV6 auE/vePVyJnRnS+2FcHxc57CMtFu99n29um4R6g1PmtbBmsPUhiF4JZEevjEIBPkzs4L d6gqRyvb8R5MxaReHW6C2L9fRlP7/8C1w7RaqdROI1j1J1EWnToKCZEegqbK8Btxe6lz K/RA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1770634549; x=1771239349; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:x-gm-gg:x-gm-message-state:from :to:cc:subject:date:message-id:reply-to; bh=yRCNcS5A6EuGBIPJ6FqXwxvOo4jjK2JrobpZz5iBr1c=; b=bVgm/s2bS/VyBHnOr1SWWDLgzTaRI7Fouu+ekAv9fU1mYziCSpR2dkcyLw2s/+oGp0 yTBuEPnUt2dV+oJ9PohrEhf2ITxmdRb613IBwPG5Q7X92PMYiUBu9dljRhzsBueMyer3 qMU8wBhJRd8qZH70bQUc62uRG7ag4xzxUW720mtYpJIHSUe7VFAhnxLyJP3B6LD0jd5U Pp1IaWNPO1nlKcObXpIVge9eQswj5E1ewn80S5exjVqpUowuUt5sz60RDx75I/yrmQ2n paVHOE15B0YpFDpi3r2B5WR1hW3Yku9FezUXdc8q/+I8ryvppWya68vhT1CUStRuKQ0l RlZg== X-Forwarded-Encrypted: i=1; AJvYcCWgEXIu/B7vex70jet99JxkVId29RPMOsCy7trisOwHKzfY2YAfACJNStympjdQpMcRJmqETHe4EjCtMAk=@vger.kernel.org X-Gm-Message-State: AOJu0Yxha9N1/IWNQZbBb32Ltbmx2BF3QUfnLhR3xt0jSifR3DT7cqYG fmKInsKd13dCe+pfPPhIlZPXj55dfKsCctJNNVIqzUZwdqgOStDxz/7muBPlf+bMyJUsX8/0OeY F8FMRcc7huvIQRMd6GhdPFgiB7w6Ad7KAnTc8VWKaBbsM3HTGcoGh5H0taTaFu7ul3Bg= X-Gm-Gg: AZuq6aKUOfNP7juIRvAm+ttEO8+n9vgifQ3hbgW+LwSW21Fg/u1FSabPV30eN4usj7E HGJ9g4/2Bdyah3fcT3uAd11+vUiZuYgODoevddZuQzhWBsUGfgNBEKk4XvTHBidRkV5ZPP09un8 TzLXb9RW8f/YKgLWJkbGA1E9i9T+6f2mkyfM8PKfCz84VKdqwHs8i75zFQpQYtcAzFAe315eCjh T+drJg5O7OdbEPF6CXnUHbo3zZ7fecKcqB8B/1Ths+CkTWTFHveLPjJxhJWp0fybHRZe7GtDaPT lhRi4N021/K1m/lWDTKb+uZhDZMsAQkhGu7ygTFoxoNCc3PDNBZcarvW5ifc6cVVr/WmgsD47wq Xvz9rc1MygXBd077WKbOUVmmXleYQ8Tqc23KweyT8CwaZ X-Received: by 2002:a17:90b:2e90:b0:356:4ea0:e9e2 with SMTP id 98e67ed59e1d1-3564ea0fcb0mr1417732a91.34.1770634548830; Mon, 09 Feb 2026 02:55:48 -0800 (PST) X-Received: by 2002:a17:90b:2e90:b0:356:4ea0:e9e2 with SMTP id 98e67ed59e1d1-3564ea0fcb0mr1417700a91.34.1770634548246; Mon, 09 Feb 2026 02:55:48 -0800 (PST) Received: from hu-jprakash-hyd.qualcomm.com ([202.46.22.19]) by smtp.gmail.com with ESMTPSA id 41be03b00d2f7-c6dcb5e5f6bsm8358837a12.20.2026.02.09.02.55.38 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 09 Feb 2026 02:55:47 -0800 (PST) From: Jishnu Prakash To: jic23@kernel.org, robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org, agross@kernel.org, andersson@kernel.org, lumag@kernel.org, dmitry.baryshkov@oss.qualcomm.com, konradybcio@kernel.org, daniel.lezcano@linaro.org, sboyd@kernel.org, amitk@kernel.org, thara.gopinath@gmail.com, lee@kernel.org, rafael@kernel.org, subbaraman.narayanamurthy@oss.qualcomm.com, david.collins@oss.qualcomm.com, anjelique.melendez@oss.qualcomm.com, kamal.wadhwa@oss.qualcomm.com Cc: rui.zhang@intel.com, lukasz.luba@arm.com, devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org, linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org, cros-qcom-dts-watchers@chromium.org, jishnu.prakash@oss.qualcomm.com, quic_kotarake@quicinc.com, neil.armstrong@linaro.org, stephan.gerhold@linaro.org, Jonathan Cameron , Krzysztof Kozlowski Subject: [PATCH V11 2/4] dt-bindings: iio: adc: Add support for QCOM PMIC5 Gen3 ADC Date: Mon, 9 Feb 2026 16:24:36 +0530 Message-Id: <20260209105438.596339-3-jishnu.prakash@oss.qualcomm.com> X-Mailer: git-send-email 2.25.1 In-Reply-To: <20260209105438.596339-1-jishnu.prakash@oss.qualcomm.com> References: <20260209105438.596339-1-jishnu.prakash@oss.qualcomm.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable X-Proofpoint-Spam-Details-Enc: AW1haW4tMjYwMjA5MDA5MSBTYWx0ZWRfX5HD+VfOzs0TV gmg30Lx478Nr9et6MhTph42G2isGD/0L38CPL8WdBIB0J4yLwwYKRHnhTSCYIDdgOlIr9DjAHKH pz+cRqEd8WKQNtxl6WEWqhwzW+gYBSIsbwVf0mLOaBV+BFpPa8SBcIp9NCYvED2fnU09RM6d2eG KARsiwkMIxLYFQjxvmUTs1O5WvnNalO+RniEXoib+hekgSWW5f4gXOMug3hT+iJFz/Vr9BUZaNr eo/lD9bOnSFKAuR8xk1WOXah07NIOGBzqYboPXIZLoEl2kzqt2LvmwfS97HGxbhe3NLkuPITqiN tlKXy+NRNoxUhPiBUOZxbQsCoIx5YiCHEDn1yZ4HnFaOHK2OIZuEOsoi/O/ehSux02Do3wvlT53 is2xQt96B4Bdr5j1OkaXvZZiliXxwOBwwy8+WCMiWy3mCnM0UszAofo1Xv/TMnKpMcjh6tENL+r cXVhyjCGHuWNqkVW5Ug== X-Authority-Analysis: v=2.4 cv=bZhmkePB c=1 sm=1 tr=0 ts=6989bd35 cx=c_pps a=RP+M6JBNLl+fLTcSJhASfg==:117 a=fChuTYTh2wq5r3m49p7fHw==:17 a=HzLeVaNsDn8A:10 a=s4-Qcg_JpJYA:10 a=VkNPw1HP01LnGYTKEx00:22 a=Mpw57Om8IfrbqaoTuvik:22 a=GgsMoib0sEa3-_RKJdDe:22 a=VwQbUJbxAAAA:8 a=EUspDBNiAAAA:8 a=gEfo2CItAAAA:8 a=i0EeH86SAAAA:8 a=YrMGt2jeDSw4g2R_97MA:9 a=iS9zxrgQBfv6-_F4QbHw:22 a=sptkURWiP4Gy88Gu7hUp:22 X-Proofpoint-ORIG-GUID: SsflYSIKNbALHOAphNOqDb6R2U3wIbB0 X-Proofpoint-GUID: SsflYSIKNbALHOAphNOqDb6R2U3wIbB0 X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.293,Aquarius:18.0.1121,Hydra:6.1.51,FMLib:17.12.100.49 definitions=2026-02-08_05,2026-02-09_02,2025-10-01_01 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 adultscore=0 impostorscore=0 bulkscore=0 lowpriorityscore=0 malwarescore=0 spamscore=0 phishscore=0 suspectscore=0 clxscore=1015 classifier=typeunknown authscore=0 authtc= authcc= route=outbound adjust=0 reason=mlx scancount=1 engine=8.22.0-2601150000 definitions=main-2602090091 Content-Type: text/plain; charset="utf-8" For the PMIC5-Gen3 type PMICs, ADC peripheral is present in HW for the following PMICs: PMK8550, PM8550, PM8550B and PM8550VX PMICs. It is similar to PMIC5-Gen2, with SW communication to ADCs on all PMICs going through PBS(Programmable Boot Sequence) firmware through a single register interface. This interface is implemented on SDAM (Shared Direct Access Memory) peripherals on the master PMIC PMK8550 rather than a dedicated ADC peripheral. Add documentation for PMIC5 Gen3 ADC and update SPMI PMIC bindings to allow ADC5 Gen3 as adc@ subnode. Acked-by: Jonathan Cameron Reviewed-by: Krzysztof Kozlowski Signed-off-by: Jishnu Prakash --- Changes since v7: - Dropped ADC5 GEN3 channel macro definitions from bindings, based on discussion with Krzysztof concluded here:=20 https://lore.kernel.org/all/d10e2eea-4b86-4e1a-b7a0-54c55907a605@oss.qual= comm.com/, to be added separately in other patches. - Fixed quotes to use only double quotes for "#address-cells", "#size-cells" and "#io-channel-cells" properties, to address Krzysztof's comment. - Removed inclusion of ADC channel macro header files from ADC5 Gen3 example and replaced the macros used in the "reg" properties in channel nodes with the actual hex values. - Removed update made under `reg` property in Documentation/devicetree/bindings/iio/adc/qcom,spmi-vadc-common.yaml which referenced ADC macro binding files, to align with change made in patch 1 of this series. Changes since v6: - Updated SPMI PMIC bindings to allow ADC5 Gen3 as adc@ subnode, to address Neil's comment. - Replaced 2025 copyright in newly added files with yearless copyright, following new internal guidelines. - Collected Acked-by tag from Jonathan. Changes since v5: - Addressed following comments from Krzysztof: - Increased line wrap length for top-level device description. - Added more details in binding description explaining how number of SDAM peripherals used for ADC is allocated per SoC. - Dropped "interrupt-names" property. - Moved `required` block to after the list of all properties. - Dropped | from patternProperties description. - Renamed per-PMIC binding files listing ADC channel macro names. - Addressed following comments from Jonathan: - Moved ref before description, under patternProperties. - Arranged enum under qcom,hw-settle-time as groups of 8. Changes since v4: - Added ADC5 Gen3 documentation in a separate new file to avoid complicating existing VADC documentation file further to accomodate this device, as suggested by reviewers. Changes since v3: - Added ADC5 Gen3 documentation changes in existing qcom,spmi-vadc.yaml file instead of adding separate file and updated top-level constraints in docu= mentation file based on discussion with reviewers. - Dropped default SID definitions. - Addressed other reviewer comments. Changes since v2: - Moved ADC5 Gen3 documentation into a separate new file. Changes since v1: - Updated properties separately for all compatibles to clarify usage of new properties and updates in usage of old properties for ADC5 Gen3. - Avoided updating 'adc7' name to 'adc5 gen2' and just left a comment mentioning this convention. - Used predefined channel IDs in individual PMIC channel definitions instead of numeric IDs. - Addressed other comments from reviewers. .../bindings/iio/adc/qcom,spmi-adc5-gen3.yaml | 151 ++++++++++++++++++ .../bindings/iio/adc/qcom,spmi-vadc.yaml | 2 + .../bindings/mfd/qcom,spmi-pmic.yaml | 1 + 3 files changed, 154 insertions(+) create mode 100644 Documentation/devicetree/bindings/iio/adc/qcom,spmi-adc= 5-gen3.yaml diff --git a/Documentation/devicetree/bindings/iio/adc/qcom,spmi-adc5-gen3.= yaml b/Documentation/devicetree/bindings/iio/adc/qcom,spmi-adc5-gen3.yaml new file mode 100644 index 000000000000..149f4af8f4b8 --- /dev/null +++ b/Documentation/devicetree/bindings/iio/adc/qcom,spmi-adc5-gen3.yaml @@ -0,0 +1,151 @@ +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/iio/adc/qcom,spmi-adc5-gen3.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: Qualcomm's SPMI PMIC ADC5 Gen3 + +maintainers: + - Jishnu Prakash + +description: | + SPMI PMIC5 Gen3 voltage ADC (ADC) provides interface to clients to read + voltage. It is a 16-bit sigma-delta ADC. It also performs the same therm= al + monitoring function as the existing ADC_TM devices. + + The interface is implemented on SDAM (Shared Direct Access Memory) perip= herals + on the master PMIC rather than a dedicated ADC peripheral. The number of= PMIC + SDAM peripherals allocated for ADC is not correlated with the PMIC used,= it is + programmed in FW (PBS) and is fixed per SOC, based on the SOC requiremen= ts. + All boards using a particular (SOC + master PMIC) combination will have = the + same number of ADC SDAMs supported on that PMIC. + +properties: + compatible: + const: qcom,spmi-adc5-gen3 + + reg: + items: + - description: SDAM0 base address in the SPMI PMIC register map + - description: SDAM1 base address + minItems: 1 + + "#address-cells": + const: 1 + + "#size-cells": + const: 0 + + "#io-channel-cells": + const: 1 + + "#thermal-sensor-cells": + const: 1 + + interrupts: + items: + - description: SDAM0 end of conversion (EOC) interrupt + - description: SDAM1 EOC interrupt + minItems: 1 + +patternProperties: + "^channel@[0-9a-f]+$": + type: object + unevaluatedProperties: false + $ref: /schemas/iio/adc/qcom,spmi-vadc-common.yaml + description: + Represents the external channels which are connected to the ADC. + + properties: + qcom,decimation: + enum: [ 85, 340, 1360 ] + default: 1360 + + qcom,hw-settle-time: + enum: [ 15, 100, 200, 300, 400, 500, 600, 700, + 1000, 2000, 4000, 8000, 16000, 32000, 64000, 128000 ] + default: 15 + + qcom,avg-samples: + enum: [ 1, 2, 4, 8, 16 ] + default: 1 + + qcom,adc-tm: + description: + ADC_TM is a threshold monitoring feature in HW which can be enab= led + on any ADC channel, to trigger an IRQ for threshold violation. In + earlier ADC generations, it was implemented in a separate device + (documented in Documentation/devicetree/bindings/thermal/qcom-sp= mi-adc-tm5.yaml.) + In Gen3, this feature can be enabled in the same ADC device for = any + channel and threshold monitoring and IRQ triggering are handled = in FW + (PBS) instead of another dedicated HW block. + This property indicates ADC_TM monitoring is done on this channe= l. + type: boolean + +required: + - compatible + - reg + - "#address-cells" + - "#size-cells" + - "#io-channel-cells" + - interrupts + +additionalProperties: false + +examples: + - | + #include + + pmic { + #address-cells =3D <1>; + #size-cells =3D <0>; + + adc@9000 { + compatible =3D "qcom,spmi-adc5-gen3"; + reg =3D <0x9000>, <0x9100>; + interrupts =3D <0x0 0x90 0x1 IRQ_TYPE_EDGE_RISING>, + <0x0 0x91 0x1 IRQ_TYPE_EDGE_RISING>; + #address-cells =3D <1>; + #size-cells =3D <0>; + #io-channel-cells =3D <1>; + #thermal-sensor-cells =3D <1>; + + /* PMK8550 Channel nodes */ + channel@3 { + reg =3D <0x3>; + label =3D "pmk8550_die_temp"; + qcom,pre-scaling =3D <1 1>; + }; + + channel@44 { + reg =3D <0x44>; + label =3D "pmk8550_xo_therm"; + qcom,pre-scaling =3D <1 1>; + qcom,ratiometric; + qcom,hw-settle-time =3D <200>; + qcom,adc-tm; + }; + + /* PM8550 Channel nodes */ + channel@103 { + reg =3D <0x103>; + label =3D "pm8550_die_temp"; + qcom,pre-scaling =3D <1 1>; + }; + + /* PM8550B Channel nodes */ + channel@78f { + reg =3D <0x78f>; + label =3D "pm8550b_vbat_sns_qbg"; + qcom,pre-scaling =3D <1 3>; + }; + + /* PM8550VS_C Channel nodes */ + channel@203 { + reg =3D <0x203>; + label =3D "pm8550vs_c_die_temp"; + qcom,pre-scaling =3D <1 1>; + }; + }; + }; diff --git a/Documentation/devicetree/bindings/iio/adc/qcom,spmi-vadc.yaml = b/Documentation/devicetree/bindings/iio/adc/qcom,spmi-vadc.yaml index 16c80709a3ee..72188041e8b5 100644 --- a/Documentation/devicetree/bindings/iio/adc/qcom,spmi-vadc.yaml +++ b/Documentation/devicetree/bindings/iio/adc/qcom,spmi-vadc.yaml @@ -15,6 +15,8 @@ description: | voltage. The VADC is a 15-bit sigma-delta ADC. SPMI PMIC5/PMIC7 voltage ADC (ADC) provides interface to clients to read voltage. The VADC is a 16-bit sigma-delta ADC. + Note that PMIC7 ADC is the generation between PMIC5 and PMIC5 Gen3 ADC, + it can be considered like PMIC5 Gen2. =20 properties: compatible: diff --git a/Documentation/devicetree/bindings/mfd/qcom,spmi-pmic.yaml b/Do= cumentation/devicetree/bindings/mfd/qcom,spmi-pmic.yaml index 65c80e3b4500..cc5de26bbf57 100644 --- a/Documentation/devicetree/bindings/mfd/qcom,spmi-pmic.yaml +++ b/Documentation/devicetree/bindings/mfd/qcom,spmi-pmic.yaml @@ -129,6 +129,7 @@ patternProperties: "^adc@[0-9a-f]+$": type: object oneOf: + - $ref: /schemas/iio/adc/qcom,spmi-adc5-gen3.yaml# - $ref: /schemas/iio/adc/qcom,spmi-iadc.yaml# - $ref: /schemas/iio/adc/qcom,spmi-rradc.yaml# - $ref: /schemas/iio/adc/qcom,spmi-vadc.yaml# --=20 2.25.1