From: Dmitry Osipenko <digetx@gmail.com>
To: Lee Jones <lee.jones@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Laxman Dewangan <ldewangan@nvidia.com>,
Mallikarjun Kasoju <mkasoju@nvidia.com>,
Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>
Cc: devicetree@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v3 0/6] Add support for Maxim 77663 MFD
Date: Thu, 25 Apr 2019 01:48:54 +0300 [thread overview]
Message-ID: <20190424224900.8018-1-digetx@gmail.com> (raw)
Hello,
This series adds support for the Maxim 77663 chip that provides PMIC, RTC,
GPIO and watchdog timer functionality. The hardware is very similar to the
Maxim 77620/20024 hardware units that are already supported by the kernel,
hence we will reuse the existing drivers for 77663. The GPIO, regulator,
RTC and watchdog timer functionality was tested on a Nexus 7 tablet that
has the Max77663 chip, everything is working perfectly fine. I'm looking
at upstreaming support for that tablet device and Max77663 is one of the
core components that are currently missing in the upstream kernel.
Changelog:
v3: Dropped "Support device-tree properly" patch since turned out that
I2C core takes care of the device-tree matching and I wasn't aware of
it.
v2: Added PINCTRL sub-device to Max77663 MFD as it looks compatible with
77620.
Added new "maxim,system-power-controller" OF property.
Patch "Support device-tree properly" now doesn't remove driver's
"id_table" since potentially it could have some use in the downstream
kernel forks and it doesn't hurt to keep it around.
Dmitry Osipenko (6):
mfd: max77620: Fix swapped FPS_PERIOD_MAX_US values
mfd: max77620: Support Maxim 77663
regulator: max77620: Support Maxim 77663
dt-bindings: mfd: max77620: Add compatible for Maxim 77663
dt-bindings: mfd: max77620: Add maxim,system-power-controller property
mfd: max77620: Provide system power-off functionality
.../devicetree/bindings/mfd/max77620.txt | 7 +-
drivers/mfd/max77620.c | 88 ++++++++++++++++++-
drivers/regulator/max77620-regulator.c | 26 +++++-
include/linux/mfd/max77620.h | 5 +-
4 files changed, 121 insertions(+), 5 deletions(-)
--
2.21.0
next reply other threads:[~2019-04-24 22:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-24 22:48 Dmitry Osipenko [this message]
2019-04-24 22:48 ` [PATCH v3 1/6] mfd: max77620: Fix swapped FPS_PERIOD_MAX_US values Dmitry Osipenko
2019-04-24 22:48 ` [PATCH v3 2/6] mfd: max77620: Support Maxim 77663 Dmitry Osipenko
2019-04-24 22:48 ` [PATCH v3 3/6] regulator: " Dmitry Osipenko
2019-04-25 17:41 ` Mark Brown
2019-04-24 22:48 ` [PATCH v3 4/6] dt-bindings: mfd: max77620: Add compatible for " Dmitry Osipenko
2019-04-30 22:53 ` Rob Herring
2019-04-24 22:48 ` [PATCH v3 5/6] dt-bindings: mfd: max77620: Add maxim,system-power-controller property Dmitry Osipenko
2019-04-30 22:55 ` Rob Herring
2019-04-24 22:49 ` [PATCH v3 6/6] mfd: max77620: Provide system power-off functionality Dmitry Osipenko
2019-04-25 11:22 ` Thierry Reding
2019-04-25 14:58 ` Dmitry Osipenko
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=20190424224900.8018-1-digetx@gmail.com \
--to=digetx@gmail.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=ldewangan@nvidia.com \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mkasoju@nvidia.com \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@gmail.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).