From: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
To: Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Masami Hiramatsu <masami.hiramatsu@linaro.org>,
Jassi Brar <jaswinder.singh@linaro.org>,
Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
Subject: [PATCH 0/2] regulator: add new UniPhier regulator support
Date: Fri, 29 Jun 2018 17:22:11 +0900 [thread overview]
Message-ID: <1530260533-19415-1-git-send-email-hayashi.kunihiko@socionext.com> (raw)
This series add new regulator controller support for UniPhier SoCs.
Currently this supports USB3 VBUS controller only.
This USB3 VBUS is included in USB3 glue layer.
Kunihiko Hayashi (2):
dt-bindings: regulator: add DT bindings for UniPhier regulator
regulator: uniphier: add regulator driver for UniPhier SoC
.../bindings/regulator/uniphier-regulator.txt | 54 +++++
drivers/regulator/Kconfig | 8 +
drivers/regulator/Makefile | 1 +
drivers/regulator/uniphier-regulator.c | 251 +++++++++++++++++++++
4 files changed, 314 insertions(+)
create mode 100644 Documentation/devicetree/bindings/regulator/uniphier-regulator.txt
create mode 100644 drivers/regulator/uniphier-regulator.c
--
2.7.4
next reply other threads:[~2018-06-29 8:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-29 8:22 Kunihiko Hayashi [this message]
2018-06-29 8:22 ` [PATCH 1/2] dt-bindings: regulator: add DT bindings for UniPhier regulator Kunihiko Hayashi
2018-06-29 8:22 ` [PATCH 2/2] regulator: uniphier: add regulator driver for UniPhier SoC Kunihiko Hayashi
2018-06-29 11:03 ` Mark Brown
2018-07-02 1:10 ` Kunihiko Hayashi
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=1530260533-19415-1-git-send-email-hayashi.kunihiko@socionext.com \
--to=hayashi.kunihiko@socionext.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jaswinder.singh@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=masami.hiramatsu@linaro.org \
--cc=robh+dt@kernel.org \
--cc=yamada.masahiro@socionext.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).