From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/9] mfd: axp20x: Add basic support for AXP813
Date: Wed, 26 Jul 2017 10:32:42 +0200 [thread overview]
Message-ID: <20170726083242.k35gnk22h35as55n@flea> (raw)
In-Reply-To: <20170726082832.16789-1-wens@csie.org>
On Wed, Jul 26, 2017 at 04:28:23PM +0800, Chen-Yu Tsai wrote:
> Hi everyone,
>
> This is v2 of my AXP813 support series. The device tree patches are
> based on my A83T MMC support series. These will go through the sunxi
> tree. The dt-binding and mfd patches are based on v4.13-rc1. These
> will go through Lee's mfd tree.
>
> Changes since v1:
>
> - Provided relative path for ac100.txt in dt-bindings/mfd/axp20x.txt
>
> - Added Rob's acks to dt-binding patches
>
> - Added Quentin's "mfd: axp20x: use correct platform device id for
> many PEK" patch to this series. This patch depends on mfd changes
> in this series. It is included so Lee can take them together in
> one go.
>
> - Added Lee's mfd-acks to mfd patches
>
> - Added axp818 compatible with axp813 fallback. The two chips are
> identical except for the markings. The added compatible matches
> what is actually on the board, to avoid confusing readers.
>
> - Fixed up device tree patches to mention which board is changed
>
> - Added device tree patches for the H8 homlet
For the whole serie,
Acked-by: Maxime Ripard <maxime.ripard@free-electrons.com>
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20170726/8696d85a/attachment.sig>
next prev parent reply other threads:[~2017-07-26 8:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-26 8:28 [PATCH v2 0/9] mfd: axp20x: Add basic support for AXP813 Chen-Yu Tsai
2017-07-26 8:28 ` [PATCH v2 1/9] dt-bindings: mfd: axp20x: Add AXP806 to supported list of chips Chen-Yu Tsai
2017-08-07 15:43 ` Lee Jones
2017-07-26 8:28 ` [PATCH v2 2/9] dt-bindings: mfd: axp20x: Introduce bindings for AXP813 Chen-Yu Tsai
2017-08-07 15:43 ` Lee Jones
2017-07-26 8:28 ` [PATCH v2 3/9] mfd: axp20x: Add support for AXP813 PMIC Chen-Yu Tsai
2017-08-07 15:43 ` Lee Jones
2017-07-26 8:28 ` [PATCH v2 4/9] mfd: axp20x: use correct platform device id for many PEK Chen-Yu Tsai
2017-08-07 15:43 ` Lee Jones
2017-07-26 8:28 ` [PATCH v2 5/9] ARM: sun8i: a83t: Add device node and pinmux setting for RSB controller Chen-Yu Tsai
2017-07-26 8:28 ` [PATCH v2 6/9] ARM: sun8i: a83t: cubietruck-plus: Enable PMIC part of AXP818 PMIC Chen-Yu Tsai
2017-07-26 8:28 ` [PATCH v2 7/9] ARM: sun8i: a83t: cubietruck-plus: Enable AC100 combo chip in " Chen-Yu Tsai
2017-07-26 8:28 ` [PATCH v2 8/9] ARM: sun8i: a83t: h8homlet-v2: Enable PMIC part of " Chen-Yu Tsai
2017-07-26 8:28 ` [PATCH v2 9/9] ARM: sun8i: a83t: h8homlet-v2: Enable AC100 combo chip in " Chen-Yu Tsai
2017-07-26 8:32 ` Maxime Ripard [this message]
2017-08-08 4:05 ` [PATCH v2 0/9] mfd: axp20x: Add basic support for AXP813 Chen-Yu Tsai
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=20170726083242.k35gnk22h35as55n@flea \
--to=maxime.ripard@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.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