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: <CACRpkdajc7e00EdgnYD_7ucOMDFhqx53EvN3uEzJ1pQhHazr9Q@mail.gmail.com>
Date:	Thu, 17 Jan 2013 11:30:48 +0100
From:	Linus Walleij <linus.walleij@...aro.org>
To:	Sekhar Nori <nsekhar@...com>
Cc:	"Kumar, Anil" <anilkumar.v@...com>,
	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
	davinci-linux-open-source@...ux.davincidsp.com,
	linux@....linux.org.uk, Kevin Hilman <khilman@...prootsystems.com>,
	hs@...x.de
Subject: Re: [PATCH V2 3/3] ARM: davinci: da850: add NAND driver entries

On Wed, Jan 9, 2013 at 1:47 PM, Sekhar Nori <nsekhar@...com> wrote:
> On 1/8/2013 1:50 PM, Kumar, Anil wrote:

>> +&pmx_core{
>> +     pinctrl-names = "default";
>> +     pinctrl-0 = <
>> +             &nand_cs3_pins
>> +     >;
>
> This means that the NAND pins are configured even if NAND is not
> probed. Right? This can be moved into the nand_cs3 node to avoid that.
> And then when used with Linus Walleij's patch "drivers/pinctrl: grab
> default handles from device core" which should be accepted soon, the
> pins will be automatically setup when the NAND gets probed.

That is correct, I am waiting for Greg's ACK on the core grab patch
(maybe it's higher up in my mailbox) and some indication from Stephen
Warren that it doesn't break the Tegra, and I'll put it into linux-next.

Yours,
Linus Walleij
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ