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] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140220080955.GA3142@lukather>
Date:	Thu, 20 Feb 2014 09:09:55 +0100
From:	Maxime Ripard <maxime.ripard@...e-electrons.com>
To:	Mark Rutland <mark.rutland@....com>
Cc:	Alexandre Belloni <alexandre.belloni@...e-electrons.com>,
	Nicolas Ferre <nicolas.ferre@...el.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"b.brezillon@...rkiz.com" <b.brezillon@...rkiz.com>,
	Gregory Clement <gregory.clement@...e-electrons.com>,
	Jean-Christophe Plagniol-Villard <plagnioj@...osoft.com>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCHv2 1/8] ARM: at91: Add at91sam9rl DT SoC support

Hi Mark,

On Wed, Feb 19, 2014 at 05:00:20PM +0000, Mark Rutland wrote:
> > +                       adc0: adc@...d0000 {
> > +                               compatible = "atmel,at91sam9260-adc";
> > +                               reg = <0xfffd0000 0x100>;
> > +                               interrupts = <20 IRQ_TYPE_LEVEL_HIGH 0>;
> > +                               atmel,adc-use-external-triggers;
> > +                               atmel,adc-channels-used = <0xf>;
> > +                               atmel,adc-vref = <3300>;
> > +                               atmel,adc-num-channels = <4>;
> > +                               atmel,adc-startup-time = <15>;
> > +                               atmel,adc-channel-base = <0x30>;
> > +                               atmel,adc-drdy-mask = <0x10000>;
> > +                               atmel,adc-status-register = <0x1c>;
> > +                               atmel,adc-trigger-register = <0x04>;
> > +                               atmel,adc-res = <8 10>;
> > +                               atmel,adc-res-names = "lowres", "highres";
> > +                               atmel,adc-use-res = "highres";
> > +
> > +                               trigger@0 {
> > +                                       trigger-name = "timer-counter-0";
> > +                                       trigger-value = <0x1>;
> > +                               };
> 
> A unit-address should go with a reg value. Either this needs a reg and
> the parent node needs #address-cells and #size-cells, or the
> unit-address should go, and the names made unique through other means.

What do you suggest to make the name unique then?

The ePAPR is pretty clear that the above is the way to go, so I'm
unclear on what you have in mind here.

Plus, I haven't seen anywhere that reg was actually mandatory.

Thanks!
Maxime

-- 
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ