devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: balbi@ti.com
Cc: "Tony Lindgren" <tony@atomide.com>,
	"Benoît Cousson" <bcousson@baylibre.com>,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	linux-omap@vger.kernel.org, sre@kernel.org
Subject: Re: [PATCH V4] ARM: dts: am57xx-beagle-x15: Add GPIO controlled fan node
Date: Mon, 5 Jan 2015 11:33:50 -0600	[thread overview]
Message-ID: <54AACAFE.7050609@ti.com> (raw)
In-Reply-To: <20150105172737.GK19336@saruman>

On 01/05/2015 11:27 AM, Felipe Balbi wrote:
> On Mon, Jan 05, 2015 at 10:32:29AM -0600, Nishanth Menon wrote:
>> TPS gpio now controls a 5v 500mA TL5209 regulator which may be supply
>> a fan (such as AFB02505HHB) over J1 connector for various purposes.
>> Provide device tree node to enable the same.
>>
>> Signed-off-by: Nishanth Menon <nm@ti.com>
>> ---
>> V4: Change format of the speed-map used.
>> V3: https://patchwork.kernel.org/patch/5562121/
>> V2: https://patchwork.kernel.org/patch/5445111/
>> V1: https://patchwork.kernel.org/patch/5444911/
>>
>> Enable and disable can be controlled by (post the RPM, it finds
>> closest match - even a 1 will do)
>>
>> echo '13000' > /sys/class/hwmon/hwmon0/fan1_target
>> and
>> echo '0' > /sys/class/hwmon/hwmon0/fan1_target
>>
>> Test log: http://slexy.org/view/s2T0ajh46z
>>
>> requires CONFIG_GPIO_PALMAS and CONFIG_SENSORS_GPIO_FAN to be operational
> 
> oh, perhaps add these as modules to omap2plus_defconfig ?
> 

In a different patch I suppose if Tony wants it that way.


-- 
Regards,
Nishanth Menon

  reply	other threads:[~2015-01-05 17:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-05 16:32 [PATCH V4] ARM: dts: am57xx-beagle-x15: Add GPIO controlled fan node Nishanth Menon
2015-01-05 17:27 ` Felipe Balbi
2015-01-08  0:20   ` Tony Lindgren
2015-01-05 17:27 ` Felipe Balbi
2015-01-05 17:33   ` Nishanth Menon [this message]
2015-01-05 17:45     ` Felipe Balbi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=54AACAFE.7050609@ti.com \
    --to=nm@ti.com \
    --cc=balbi@ti.com \
    --cc=bcousson@baylibre.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=sre@kernel.org \
    --cc=tony@atomide.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).