linux-mediatek.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Wen Su <Wen.Su@mediatek.com>
To: Lee Jones <lee.jones@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	"Mark Brown" <broonie@kernel.org>,
	Matthias Brugger <matthias.bgg@gmail.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
	devicetree@vger.kernel.org, wen.su@mediatek.com,
	wsd_upstream@mediatek.com, linux-kernel@vger.kernel.org,
	Liam Girdwood <lgirdwood@gmail.com>,
	linux-mediatek@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/4] Add Support for MediaTek PMIC MT6359 Regulator
Date: Thu, 6 Feb 2020 11:06:47 +0800	[thread overview]
Message-ID: <1580958411-2478-1-git-send-email-Wen.Su@mediatek.com> (raw)

This patchset add support to MT6359 PMIC regulator. MT6359 is primary
PMIC for MT6779 platform.

Changes since v2:
- remove open coding in the mt6359 regulator for volt_table type regulators
- refine coding style in the mt6359 regulator to avoid using ternery operator
- remove unnecessary reject operation in mt6359 regulator set mode function


Wen Su (4):
  dt-bindings: regulator: Add document for MT6359 regulator
  mfd: Add for PMIC MT6359 registers definition
  regulator: mt6359: Add support for MT6359 regulator
  arm64: dts: mt6359: add PMIC MT6359 related nodes

 .../bindings/regulator/mt6359-regulator.txt        |  58 ++
 arch/arm64/boot/dts/mediatek/mt6359.dtsi           | 306 +++++++++
 drivers/regulator/Kconfig                          |   9 +
 drivers/regulator/Makefile                         |   1 +
 drivers/regulator/mt6359-regulator.c               | 738 +++++++++++++++++++++
 include/linux/mfd/mt6359/registers.h               | 531 +++++++++++++++
 include/linux/regulator/mt6359-regulator.h         |  58 ++
 7 files changed, 1701 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/regulator/mt6359-regulator.txt
 create mode 100644 arch/arm64/boot/dts/mediatek/mt6359.dtsi
 create mode 100644 drivers/regulator/mt6359-regulator.c
 create mode 100644 include/linux/mfd/mt6359/registers.h
 create mode 100644 include/linux/regulator/mt6359-regulator.h

-- 
1.9.1
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek

             reply	other threads:[~2020-02-06  3:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-06  3:06 Wen Su [this message]
2020-02-06  3:06 ` [PATCH v2 1/4] dt-bindings: regulator: Add document for MT6359 regulator Wen Su
2020-02-06 11:49   ` Mark Brown
2020-02-10 11:57     ` Wen Su
2020-02-11 16:06       ` Matthias Brugger
2020-02-12  6:08         ` Wen Su
2020-02-06  3:06 ` [PATCH v2 2/4] mfd: Add for PMIC MT6359 registers definition Wen Su
2020-02-06  3:06 ` [PATCH v2 3/4] regulator: mt6359: Add support for MT6359 regulator Wen Su
2020-02-06  3:06 ` [PATCH v2 4/4] arm64: dts: mt6359: add PMIC MT6359 related nodes Wen Su

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=1580958411-2478-1-git-send-email-Wen.Su@mediatek.com \
    --to=wen.su@mediatek.com \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=lee.jones@linaro.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=mark.rutland@arm.com \
    --cc=matthias.bgg@gmail.com \
    --cc=robh+dt@kernel.org \
    --cc=wsd_upstream@mediatek.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).