From: Wadim Egorov <w.egorov@phytec.de>
To: linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
devicetree@vger.kernel.org
Cc: robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
lee.jones@linaro.org, lgirdwood@gmail.com, broonie@kernel.org,
dianders@chromium.org, zyw@rock-chips.com
Subject: [RFC 0/3] Add RK818 PMIC support
Date: Fri, 8 Apr 2016 11:47:38 +0200 [thread overview]
Message-ID: <1460108861-32818-1-git-send-email-w.egorov@phytec.de> (raw)
Hello,
this patch adds support for rockchip's RK818 PMIC.
I am not sure if I have to rename all filenames and all relevant variable names
after adding a second supported device to the RK808 driver, e.g:
mfd/rk8xx.c
regulator/rk8xx-regulator.c
clk/clk-rk8xx.c
Regards,
Wadim
Wadim Egorov (3):
mfd: RK808: Add RK818 support
regulator: rk808: Add support for rk818
mfd: dt-bindings: Add RK818 device tree bindings document
Documentation/devicetree/bindings/mfd/rk808.txt | 37 ++-
drivers/mfd/Kconfig | 6 +-
drivers/mfd/rk808.c | 279 +++++++++++++++----
drivers/regulator/rk808-regulator.c | 343 ++++++++++++++++++++++--
include/linux/mfd/rk808.h | 182 ++++++++++++-
5 files changed, 761 insertions(+), 86 deletions(-)
--
1.9.1
next reply other threads:[~2016-04-08 9:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-08 9:47 Wadim Egorov [this message]
2016-04-08 9:47 ` [RFC 1/3] mfd: RK808: Add RK818 support Wadim Egorov
2016-04-11 8:41 ` Lee Jones
2016-04-08 9:47 ` [RFC 2/3] regulator: rk808: Add support for rk818 Wadim Egorov
2016-04-10 19:04 ` Mark Brown
2016-04-08 9:47 ` [RFC 3/3] mfd: dt-bindings: Add RK818 device tree bindings document Wadim Egorov
2016-04-11 8:44 ` Lee Jones
2016-04-11 16:03 ` Rob Herring
2016-04-11 16:19 ` Lee Jones
2016-04-11 15:48 ` Rob Herring
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=1460108861-32818-1-git-send-email-w.egorov@phytec.de \
--to=w.egorov@phytec.de \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=zyw@rock-chips.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
all inboxes | Powered by JetHome®