[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <1462957929-20105-1-git-send-email-henryc.chen@mediatek.com>
Date: Wed, 11 May 2016 17:12:07 +0800
From: Henry Chen <henryc.chen@...iatek.com>
To: Rob Herring <robh+dt@...nel.org>,
Liam Girdwood <lgirdwood@...il.com>,
Mark Brown <broonie@...nel.org>,
Matthias Brugger <matthias.bgg@...il.com>
CC: Pawel Moll <pawel.moll@....com>,
Mark Rutland <mark.rutland@....com>,
Ian Campbell <ijc+devicetree@...lion.org.uk>,
Kumar Gala <galak@...eaurora.org>,
Stephen Boyd <sboyd@...eaurora.org>,
Henry Chen <henryc.chen@...iatek.com>,
Bjorn Andersson <bjorn.andersson@...ymobile.com>,
Laxman Dewangan <ldewangan@...dia.com>,
<devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-mediatek@...ts.infradead.org>
Subject: Add support for regulator operation mode of mt6397
Some regulators support different operating modes, but there is no suitable
property that can pass the opeation mode constraints on runtime at present.
This series making the change to specify supported modes as a devicetree list.
Consumers can change or get the regulator operation mode by regulator_set_mode
/regulator_get_mode and define the support operating mode on devicetree.
There is a requirement from SVS driver. SVS calibartion requires that the
regulator be in its low-noise (pwm mode) state at boot, but at all other times
it can be normal mode for power saving.
http://www.spinics.net/lists/devicetree/msg111204.html
Powered by blists - more mailing lists