From: Paul Kocialkowski <contact@paulk.fr>
To: linux-kernel@vger.kernel.org
Cc: "Rob Herring" <robh+dt@kernel.org>,
"Pawel Moll" <pawel.moll@arm.com>,
"Mark Rutland" <mark.rutland@arm.com>,
"Ian Campbell" <ijc+devicetree@hellion.org.uk>,
"Kumar Gala" <galak@codeaurora.org>,
"Russell King" <linux@arm.linux.org.uk>,
"Benoît Cousson" <bcousson@baylibre.com>,
"Tony Lindgren" <tony@atomide.com>,
"Liam Girdwood" <lgirdwood@gmail.com>,
"Javier Martinez Canillas" <javier@dowhile0.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-omap@vger.kernel.org
Subject: [PATCH v3 0/4] LG Optimus Black codename sniper support series
Date: Sun, 28 Feb 2016 11:20:23 +0100 [thread overview]
Message-ID: <1456654827-11349-1-git-send-email-contact@paulk.fr> (raw)
This series requires lp872x regulator patches from the regulator tree[0] to work
at run-time but can be applied as-is.
Changes since v2:
* Add USB OTG support
* Add TWL4030 keypad support
* Drop references to P970 since other devices (e.g. KU5900) are supported too
Changes since v1:
* Remove lp872x patches that were accepted already from the series
* Explain why removing the invalid DVS GPIO warning is enough
* Update copyright notice on omap3-sniper.dts
* Rename the devicetree property for the enable GPIO to enable-gpios
* Rename function to enable GPIO to lp872x_hw_enable
* Add enable delays after requesting the enable GPIO
* Use IOPAD macros for pinmux description
* Mux the dp3t uart selection pins to gpio
* Restrict not-reset gpio controllers to only avoid reset when needed
This series introduces support for the LG Optimus Black, as described in the
patch adding devicetree support for the device.
In order to power the external mmc (mmc1), the lp872x regulator is used.
Its code had to be improved a bit to work on the device.
Note that the patch adding devicetree support for the device requires the
changes applied to the lp872x regulator, so all this is sent in one series
despite the fact they're different parts of the code.
[0]: https://git.kernel.org/cgit/linux/kernel/git/broonie/regulator.git/log/?h=topic/lp872x
next reply other threads:[~2016-02-28 10:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-28 10:20 Paul Kocialkowski [this message]
2016-02-28 10:20 ` [PATCH v3 1/4] ARM: dts: LG Optimus Black codename sniper basic support Paul Kocialkowski
2016-02-28 10:20 ` [PATCH v3 2/4] ARM: dts: omap3-sniper: USB OTG support Paul Kocialkowski
[not found] ` <1456654827-11349-1-git-send-email-contact-W9ppeneeCTY@public.gmane.org>
2016-02-28 10:20 ` [PATCH v3 3/4] ARM: dts: omap3-sniper: TWL4030 keypad support Paul Kocialkowski
2016-02-28 10:20 ` [PATCH v3 4/4] ARM: multi_v7_defconfig: Enable LP872x regulator support Paul Kocialkowski
2016-02-28 12:38 ` [PATCH v3 0/4] LG Optimus Black codename sniper support series Paul Kocialkowski
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=1456654827-11349-1-git-send-email-contact@paulk.fr \
--to=contact@paulk.fr \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=javier@dowhile0.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@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).