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: <4F73E895.6000207@ti.com>
Date:	Thu, 29 Mar 2012 10:14:05 +0530
From:	Rajendra Nayak <rnayak@...com>
To:	Michael Bohan <mbohan@...eaurora.org>
CC:	Mark Brown <broonie@...nsource.wolfsonmicro.com>, lrg@...com,
	LKML <linux-kernel@...r.kernel.org>,
	linux-arm-msm@...r.kernel.org
Subject: Re: Regulator supplies when using Device Tree

On Thursday 29 March 2012 05:36 AM, Michael Bohan wrote:
> Put simply, whose responsibility is it to assign the
> regulator_desc->supply_name pointer before registering a regulator
> device added from Device Tree?

The drivers, and its expected to know, and not lookup something from the 
DT node to figure out what regulator_desc->supply_name should be.

You can read through the discussion when the bindings were being
proposed.
http://www.spinics.net/lists/linux-omap/msg58395.html
--
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