From: Rob Herring <robh@kernel.org>
To: Pascal PAILLET-LME <p.paillet@st.com>
Cc: "dmitry.torokhov@gmail.com" <dmitry.torokhov@gmail.com>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"lee.jones@linaro.org" <lee.jones@linaro.org>,
"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
"broonie@kernel.org" <broonie@kernel.org>,
"wim@linux-watchdog.org" <wim@linux-watchdog.org>,
"linux@roeck-us.net" <linux@roeck-us.net>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-watchdog@vger.kernel.org" <linux-watchdog@vger.kernel.org>,
"benjamin.gaignard@linaro.org" <benjamin.gaignard@linaro.org>
Subject: Re: [PATCH 2/8] mfd: stpmu1: add stpmu1 pmic driver
Date: Mon, 16 Jul 2018 16:15:58 -0600 [thread overview]
Message-ID: <20180716221558.GA3786@rob-hp-laptop> (raw)
In-Reply-To: <1530803657-17684-3-git-send-email-p.paillet@st.com>
On Thu, Jul 05, 2018 at 03:14:22PM +0000, Pascal PAILLET-LME wrote:
> From: pascal paillet <p.paillet@st.com>
>
> stpmu1 is a pmic from STMicroelectronics. The stpmu1 integrates 10
> regulators and 3 switches with various capabilities.
>
> Signed-off-by: pascal paillet <p.paillet@st.com>
> ---
> drivers/mfd/Kconfig | 14 ++
> drivers/mfd/Makefile | 1 +
> drivers/mfd/stpmu1.c | 490 ++++++++++++++++++++++++++++++++++++
> include/dt-bindings/mfd/st,stpmu1.h | 46 ++++
This belongs with patch 1.
> include/linux/mfd/stpmu1.h | 220 ++++++++++++++++
> 5 files changed, 771 insertions(+)
> create mode 100644 drivers/mfd/stpmu1.c
> create mode 100644 include/dt-bindings/mfd/st,stpmu1.h
> create mode 100644 include/linux/mfd/stpmu1.h
next prev parent reply other threads:[~2018-07-16 22:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-05 15:14 [PATCH 0/8] Introduce STPMU1 PMIC Driver Pascal PAILLET-LME
2018-07-05 15:14 ` [PATCH 2/8] mfd: stpmu1: add stpmu1 pmic driver Pascal PAILLET-LME
2018-07-09 22:38 ` Enric Balletbo Serra
2018-08-21 12:23 ` Pascal PAILLET-LME
2018-07-16 22:15 ` Rob Herring [this message]
2018-07-05 15:14 ` [PATCH 1/8] dt-bindings: mfd: document stpmu1 pmic Pascal PAILLET-LME
2018-07-16 22:14 ` Rob Herring
2018-07-05 15:14 ` [PATCH 3/8] dt-bindings: regulator: document stpmu1 pmic regulators Pascal PAILLET-LME
2018-07-16 22:21 ` Rob Herring
2018-07-05 15:14 ` [PATCH 4/8] regulator: stpmu1: add stpmu1 regulator driver Pascal PAILLET-LME
2018-07-05 16:48 ` Mark Brown
2018-07-05 15:14 ` [PATCH 6/8] input: stpmu1: add stpmu1 onkey driver Pascal PAILLET-LME
2018-08-06 22:47 ` Dmitry Torokhov
2018-07-05 15:14 ` [PATCH 5/8] dt-bindings: input: document stpmu1 pmic onkey Pascal PAILLET-LME
2018-07-05 15:14 ` [PATCH 7/8] dt-bindings: watchdog: document stpmu1 pmic watchdog Pascal PAILLET-LME
2018-07-05 15:14 ` [PATCH 8/8] watchdog: stpmu1: add stpmu1 watchdog driver Pascal PAILLET-LME
2018-07-05 18:48 ` Guenter Roeck
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=20180716221558.GA3786@rob-hp-laptop \
--to=robh@kernel.org \
--cc=benjamin.gaignard@linaro.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mark.rutland@arm.com \
--cc=p.paillet@st.com \
--cc=wim@linux-watchdog.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).