From: matthias.bgg@gmail.com (Matthias Brugger)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V6 00/11] soc: mediatek: PMIC wrap: add MT6323/2701/7623 support
Date: Wed, 20 Apr 2016 13:07:44 +0200 [thread overview]
Message-ID: <57176300.8050505@gmail.com> (raw)
In-Reply-To: <1455871455-21212-1-git-send-email-blogic@openwrt.org>
On 19/02/16 09:44, John Crispin wrote:
> This series adds support for the MT6323 PMIC and the MT2701/7623 SoC.
> MT6323 is slightly different to the already supported PMIC. This series
> makes a few changes to the code to allow easy addition of the new PMIC
> and SoCs.
>
> Changes in V6
> * 4/11 - make description verbose and rename init_special
> * 6/11 - make description verbose
> * 7/11 - make description verbose
> * 8/11 - make description verbose
> * 9/11 - put mt6397 specific dew registers in their own paragraph
>
>
> John Crispin (11):
> dt-bindings: ARM: Mediatek: add MT2701/7623 string to the PMIC
> wrapper doc
> soc: mediatek: PMIC wrap: don't duplicate the wrapper data
> soc: mediatek: PMIC wrap: add wrapper callbacks for init_reg_clock
> soc: mediatek: PMIC wrap: split SoC specific init into callback
> soc: mediatek: PMIC wrap: WRAP_INT_EN needs a different bitmask for
> MT2701/7623
> soc: mediatek: PMIC wrap: SPI_WRITE needs a different bitmask for
> MT2701/7623
> soc: mediatek: PMIC wrap: move wdt_src into the pmic_wrapper_type
> struct
> soc: mediatek: PMIC wrap: remove pwrap_is_mt8135() and
> pwrap_is_mt8173()
> soc: mediatek: PMIC wrap: add a slave specific struct
> soc: mediatek: PMIC wrap: add mt6323 slave support
> soc: mediatek: PMIC wrap: add MT2701/7623 support
>
> .../devicetree/bindings/soc/mediatek/pwrap.txt | 1 +
> drivers/soc/mediatek/mtk-pmic-wrap.c | 544 +++++++++++++++-----
> 2 files changed, 414 insertions(+), 131 deletions(-)
>
Applied, thanks!
prev parent reply other threads:[~2016-04-20 11:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-19 8:44 [PATCH V6 00/11] soc: mediatek: PMIC wrap: add MT6323/2701/7623 support John Crispin
2016-02-19 8:44 ` [PATCH V6 01/11] dt-bindings: ARM: Mediatek: add MT2701/7623 string to the PMIC wrapper doc John Crispin
2016-02-19 8:44 ` [PATCH V6 02/11] soc: mediatek: PMIC wrap: don't duplicate the wrapper data John Crispin
2016-02-19 8:44 ` [PATCH V6 03/11] soc: mediatek: PMIC wrap: add wrapper callbacks for init_reg_clock John Crispin
2016-02-19 8:44 ` [PATCH V6 04/11] soc: mediatek: PMIC wrap: split SoC specific init into callback John Crispin
2016-02-19 8:44 ` [PATCH V6 05/11] soc: mediatek: PMIC wrap: WRAP_INT_EN needs a different bitmask for MT2701/7623 John Crispin
2016-02-19 8:44 ` [PATCH V6 06/11] soc: mediatek: PMIC wrap: SPI_WRITE " John Crispin
2016-02-19 8:44 ` [PATCH V6 07/11] soc: mediatek: PMIC wrap: move wdt_src into the pmic_wrapper_type struct John Crispin
2016-02-19 8:44 ` [PATCH V6 08/11] soc: mediatek: PMIC wrap: remove pwrap_is_mt8135() and pwrap_is_mt8173() John Crispin
2016-02-19 8:44 ` [PATCH V6 09/11] soc: mediatek: PMIC wrap: add a slave specific struct John Crispin
2016-02-19 8:44 ` [PATCH V6 10/11] soc: mediatek: PMIC wrap: add mt6323 slave support John Crispin
2016-02-19 8:44 ` [PATCH V6 11/11] soc: mediatek: PMIC wrap: add MT2701/7623 support John Crispin
2016-04-20 11:07 ` Matthias Brugger [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=57176300.8050505@gmail.com \
--to=matthias.bgg@gmail.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;
as well as URLs for NNTP newsgroup(s).