linux-kernel - Re: [PATCHv2 1/3] Documentation: ad5064: Added devicetree bindings documentation

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Tue, 13 Oct 2015 13:11:17 +0200
From:	Lars-Peter Clausen <lars@...afoo.de>
To:	Mark Rutland <mark.rutland@....com>,
	Paul Cercueil <paul.cercueil@...log.com>
CC:	Jonathan Cameron <jic23@...nel.org>,
	Michael Hennerich <Michael.Hennerich@...log.com>,
	Hartmut Knaack <knaack.h@....de>,
	Peter Meerwald <pmeerw@...erw.net>,
	Rob Herring <robh+dt@...nel.org>,
	Pawel Moll <pawel.moll@....com>,
	Ian Campbell <ijc+devicetree@...lion.org.uk>,
	Kumar Gala <galak@...eaurora.org>, devicetree@...r.kernel.org,
	linux-kernel@...r.kernel.org, linux-iio@...r.kernel.org
Subject: Re: [PATCHv2 1/3] Documentation: ad5064: Added devicetree bindings
 documentation

>> +
>> +Optional properties:
>> +	- vref-supply: phandle to the external reference voltage supply.
>> +	  This should only be set if there is an external reference voltage
>> +	  connected to the vref or vref[A-D] pins.
> 
> I don't understand. Surely the latter case means you're describing the
> same supply twice (as it should already be in vref*-supply)?
> 
> What vref pins does the HW actually have?

Some off the devices supported by the binding have a shared reference for
all DAC outputs, while others have a separate reference for each output. In
addition to that some of them have an internal reference that can used, in
which case the external reference is optional, otherwise the external
reference is required. The bindings documentation should clarify on which
applies to which device.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/