From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Alexandre Courbot <gnurou@gmail.com>,
Lee Jones <lee.jones@linaro.org>, Chen-Yu Tsai <wens@csie.org>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
Hans de Goede <hdegoede@redhat.com>
Subject: Re: [PATCH v2 0/4] Add AXP209 GPIO driver
Date: Mon, 22 Aug 2016 15:36:14 +0200 [thread overview]
Message-ID: <20160822133614.GN7104@lukather> (raw)
In-Reply-To: <20160720141139.25098-1-maxime.ripard@free-electrons.com>
[-- Attachment #1: Type: text/plain, Size: 655 bytes --]
On Wed, Jul 20, 2016 at 04:11:35PM +0200, Maxime Ripard wrote:
> Hi,
>
> The axp209 PMIC used in combination to some Allwinner SoCs has a bunch
> of GPIOs accessible. Some boards use these to control their backlight
> or a few LEDs.
>
> There's supposed to be 4 of them, but the fourth one has a different
> configuration register scheme, and I couldn't find any board that was
> using this GPIO. It will be probably be supported eventually, but
> until then, we support only the first 3 GPIOs.
I merged the patches 3 and 4.
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-08-22 13:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-20 14:11 [PATCH v2 0/4] Add AXP209 GPIO driver Maxime Ripard
2016-07-20 14:11 ` [PATCH v2 1/4] gpio: " Maxime Ripard
2016-08-11 8:28 ` Linus Walleij
2016-07-20 14:11 ` [PATCH v2 2/4] mfd: axp20x: Add AXP209 GPIO driver to the mfd Maxime Ripard
2016-08-09 9:58 ` Lee Jones
2016-07-20 14:11 ` [PATCH v2 3/4] ARM: dt: axp209: Add AXP209 GPIO driver Maxime Ripard
2016-07-20 14:11 ` [PATCH v2 4/4] ARM: sun5i: chip: Add status LED Maxime Ripard
2016-08-22 13:36 ` Maxime Ripard [this message]
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=20160822133614.GN7104@lukather \
--to=maxime.ripard@free-electrons.com \
--cc=devicetree@vger.kernel.org \
--cc=gnurou@gmail.com \
--cc=hdegoede@redhat.com \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wens@csie.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).