lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20230116152135.0000175c@Huawei.com>
Date:   Mon, 16 Jan 2023 15:21:35 +0000
From:   Jonathan Cameron <Jonathan.Cameron@...wei.com>
To:     Hugo Villeneuve <hugo@...ovil.com>
CC:     Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
        Jonathan Cameron <jic23@...nel.org>,
        <hvilleneuve@...onoff.com>, <lars@...afoo.de>,
        <robh+dt@...nel.org>, <krzysztof.kozlowski+dt@...aro.org>,
        <linux-iio@...r.kernel.org>, <devicetree@...r.kernel.org>,
        <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 2/2] dt-bindings: iio: adc: add Texas Instruments
 ADS7924

On Sun, 15 Jan 2023 15:11:39 -0500
Hugo Villeneuve <hugo@...ovil.com> wrote:

> On Sun, 15 Jan 2023 20:17:24 +0100
> Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org> wrote:
> 
> > On 15/01/2023 17:32, Hugo Villeneuve wrote:  
> > >>>>> +    required:
> > >>>>> +      - reg
> > >>>>> +
> > >>>>> +    additionalProperties: false    
> > >>>>
> > >>>> You are not allowing anything else from adc.yaml. Is it on purpose?    
> > >>>
> > >>> I am really not an expert with this Yaml stuff, and reading the documentation makes me probably more confused than before reading it :)
> > >>>
> > >>> But one thing that is for sure is that these other properties in adc.yaml are not used in my driver:
> > >>>
> > >>>   bipolar
> > >>>   diff-channels
> > >>>   settling-time-us
> > >>>   oversampling-ratio
> > >>>
> > >>> So is it Ok then to use "additionalProperties: false"? I think so, but what is your recommandation?  
> > >>
> > >> Makes sense to me.  Whilst there are lots of things a channel can support, most
> > >> of them are hardware related and not universal.  
> > > 
> > > Ok, I think I am finally beginning to see the light here :)
> > > 
> > > So I will then leave "additionalProperties: false".
> > > 
> > > I will send a V4 soon with all the latest changes.
> > >   
> > 
> > Just to clarify - we talk about hardware, not your Linux driver. What
> > your driver uses or doesn't, should not matter here that much.  

Indeed. The hardware does not support bipolar inputs, differential channels
or oversampling ratios as all of those require specific silicon that
is not in this particular device.

Technically you could emulate oversampling but there is no reason to do
that in kernel and no drivers do so + then it would not be a feature of
the hardware anyway so wouldn't belong in DT.

> 
> Hi,
> the following properties are definitely not supported by the hardware:
>     bipolar
>     diff-channels
>     oversampling-ratio
> 
> does this means that we should add these lines?
>     bipolar: false
>     diff-channels: false
>     oversampling-ratio: false
> 
> as for settling-time-us, I am not sure of its usage and if its related to this hardware.

That's used for devices that will delay their ADC sampling if there is a mux that is changing
which pin is being internally connected to a single shared ADC.  It requires hardware
support, which isn't present in this device.

Jonathan


> 
> Hugo.
> 
> 
> > Best regards,
> > Krzysztof
> > 
> >   
> 
> 

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ