From: Doug Anderson <dianders@chromium.org>
To: Anton Vorontsov <anton@enomsg.org>
Cc: Olof Johansson <olof@lixom.net>,
Sachin Kamat <sachin.kamat@linaro.org>,
ajaykumar.rs@samsung.com, linux-samsung-soc@vger.kernel.org,
Doug Anderson <dianders@chromium.org>,
devicetree@vger.kernel.org, Randy Dunlap <rdunlap@infradead.org>,
Mark Brown <broonie@kernel.org>, Simon Glass <sjg@chromium.org>,
linux-doc@vger.kernel.org, Liam Girdwood <lgirdwood@gmail.com>,
Samuel Ortiz <sameo@linux.intel.com>,
linux-kernel@vger.kernel.org, Kumar Gala <galak@codeaurora.org>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
David Woodhouse <dwmw2@infradead.org>,
Pawel Moll <pawel.moll@arm.com>, Lee Jones <lee.jones@linaro.org>,
Mark Rutland <mark.rutland@arm.com>,
Sean Paul <seanpaul@chromium.org>,
Michael Spang <spang@chromium.org>
Subject: [PATCH 0/3] Fixes for tps65090 for Samsung ARM Chromebook
Date: Tue, 15 Apr 2014 13:14:33 -0700 [thread overview]
Message-ID: <1397592876-5741-1-git-send-email-dianders@chromium.org> (raw)
These three patches bring tps65090 up to speed with what's currently
in the Chromium OS kernel 3.8 tree and running on the Samsung ARM
Chromebook. Changes were tested atop the current linux tree
(v3.15-rc1). FET retries were tested on a machine with a known flaky
tps65090. Since display isn't working on pure upstream, I augmented
the code to turn FET1 (vcd_led) on/off 500 times at bootup. When
testing I included <https://patchwork.kernel.org/patch/3980731/> to
make sure tps65090 was in exynos5250-snow's device tree.
Doug Anderson (3):
mfd: tps65090: Allow charger module to be used when no irq
mfd: tps65090: Stop caching registers
regulator: tps65090: Make FETs more reliable
.../devicetree/bindings/regulator/tps65090.txt | 4 +
drivers/mfd/tps65090.c | 24 ++-
drivers/power/tps65090-charger.c | 76 ++++++--
drivers/regulator/tps65090-regulator.c | 197 +++++++++++++++++++--
include/linux/mfd/tps65090.h | 5 +
5 files changed, 264 insertions(+), 42 deletions(-)
--
1.9.1.423.g4596e3a
next reply other threads:[~2014-04-15 20:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-15 20:14 Doug Anderson [this message]
2014-04-15 20:14 ` [PATCH 3/3] regulator: tps65090: Make FETs more reliable Doug Anderson
[not found] ` <1397592876-5741-4-git-send-email-dianders-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2014-04-15 22:52 ` Mark Brown
2014-04-16 18:28 ` Doug Anderson
2014-04-16 18:25 ` [PATCH v2 0/5] Fixes for tps65090 for Samsung ARM Chromebook Doug Anderson
2014-04-16 18:25 ` [PATCH v2 4/5] regulator: tps65090: Allow setting the overcurrent wait time Doug Anderson
2014-04-16 20:33 ` Randy Dunlap
2014-04-16 23:12 ` Doug Anderson
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=1397592876-5741-1-git-send-email-dianders@chromium.org \
--to=dianders@chromium.org \
--cc=ajaykumar.rs@samsung.com \
--cc=anton@enomsg.org \
--cc=broonie@kernel.org \
--cc=dbaryshkov@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dwmw2@infradead.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=olof@lixom.net \
--cc=pawel.moll@arm.com \
--cc=rdunlap@infradead.org \
--cc=robh+dt@kernel.org \
--cc=sachin.kamat@linaro.org \
--cc=sameo@linux.intel.com \
--cc=seanpaul@chromium.org \
--cc=sjg@chromium.org \
--cc=spang@chromium.org \
/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).