<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Technicalities &#187; regulator</title>
	<atom:link href="http://www.sirena.org.uk/log/category/tech/linux/regulator/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sirena.org.uk/log</link>
	<description>Just another random blog</description>
	<lastBuildDate>Fri, 16 Jul 2010 17:24:50 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Setting up regulator consumers with dev_name</title>
		<link>http://www.sirena.org.uk/log/2009/09/16/setting-up-regulator-consumers-with-dev_name/</link>
		<comments>http://www.sirena.org.uk/log/2009/09/16/setting-up-regulator-consumers-with-dev_name/#comments</comments>
		<pubDate>Wed, 16 Sep 2009 12:29:13 +0000</pubDate>
		<dc:creator>Mark Brown</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Planet Debian]]></category>
		<category><![CDATA[regulator]]></category>
		<category><![CDATA[tech]]></category>
		<category><![CDATA[api]]></category>
		<category><![CDATA[kernel]]></category>

		<guid isPermaLink="false">http://www.sirena.org.uk/log/?p=43</guid>
		<description><![CDATA[The Linux kernel regulator API requires that each system sets up the connections between the various voltage and current regulators in the system and the devices they supply, known as consumers within the regulator API. This is done using the struct device for the consumer device as the key for consumer access. This works well [...]]]></description>
			<content:encoded><![CDATA[<p>The Linux kernel regulator API requires that each system sets up the connections between the various voltage and current regulators in the system and the devices they supply, known as consumers within the regulator API. This is done using the <tt>struct device</tt> for the consumer device as the key for consumer access. This works well for things like platform devices which are generally always allocated at system startup but is not really usable with buses like I2C which only allocate the <tt>struct device</tt> late on during system startup.</p>
<p>To help work with these buses Linux 2.6.32 will follow the clock API and allow the use of the <tt>dev_name()</tt> for the device instead. A new field <tt>dev_name</tt> has been added to <tt>struct regulator_consumer_supply</tt> which should be used instead of <tt>dev</tt> &#8211; this is now the preferred mechanism. It is a simple string and so does not depend on any other initialization.</p>
<p>For those backporting the relevant commit is <a href="http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=history;f=drivers/regulator/core.c;h=744ea1d0b59bf084f19559b8f199b644fbb0899c;hb=master">744ea1d0b59bf084f19559b8f199b644fbb0899c</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.sirena.org.uk/log/2009/09/16/setting-up-regulator-consumers-with-dev_name/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
