Re: [PATCH v2 3/4] dt-bindings: iio: adc: qcom,pm8018-adc: allow specifying MPP channels

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sun,  4 Dec 2022 08:15:54 +0200
Dmitry Baryshkov <dmitry.baryshkov@xxxxxxxxxx> wrote:

> Several ADC channels are bound to the Multi Purpose Pins (MPPs). Allow
> specifying such channels using the mppN device node (as used on apq8060
> dragonboard).
> 
> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@xxxxxxxxxx>

So I understand this more, why do the node names have to have anything to
do with the particular pin? I'm assuming the reg value provides that
relationship.

> ---
>  Documentation/devicetree/bindings/iio/adc/qcom,pm8018-adc.yaml | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/Documentation/devicetree/bindings/iio/adc/qcom,pm8018-adc.yaml b/Documentation/devicetree/bindings/iio/adc/qcom,pm8018-adc.yaml
> index d186b713d6a7..fee30e6ddd62 100644
> --- a/Documentation/devicetree/bindings/iio/adc/qcom,pm8018-adc.yaml
> +++ b/Documentation/devicetree/bindings/iio/adc/qcom,pm8018-adc.yaml
> @@ -64,7 +64,7 @@ required:
>    - adc-channel@f
>  
>  patternProperties:
> -  "^(adc-channel@)[0-9a-f]$":
> +  "^(adc-channel|mpp[0-9]+)@[0-9a-f]$":
>      type: object
>      description: |
>        ADC channel specific configuration.




[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux