From: Lee Jones <lee.jones@linaro.org>
To: Pascal PAILLET-LME <p.paillet@st.com>
Cc: "dmitry.torokhov@gmail.com" <dmitry.torokhov@gmail.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"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>,
"eballetbo@gmail.com" <eballetbo@gmail.com>,
"axel.lin@ingics.com" <axel.lin@ingics.com>
Subject: Re: [PATCH v7 0/7] Introduce STPMIC1 PMIC Driver
Date: Fri, 7 Dec 2018 07:31:32 +0000 [thread overview]
Message-ID: <20181207073132.GH26661@dell> (raw)
In-Reply-To: <5C07F08B.2010701@st.com>
On Wed, 05 Dec 2018, Pascal PAILLET-LME wrote:
>
> pascal paillet (p.paillet@st.com) Le Mans / France
> Microcontrollers and Digital ICs Group | Application Development
> TEL: +33.(0)2.44.02.74.69 | TINA: 166 7469
>
> Le 12/05/2018 10:36 AM, Lee Jones a écrit :
> > On Tue, 04 Dec 2018, Pascal PAILLET-LME wrote:
> >> Le 12/03/2018 08:11 AM, Lee Jones a écrit :
> >>> On Fri, 30 Nov 2018, Pascal PAILLET-LME wrote:
> >>>
> >>>> The goal of this patch-set is to propose a driver for the STPMIC1 PMIC from
> >>>> STMicroelectronics.
> >>>> The STPMIC1 regulators supply power to an application processor as well as
> >>>> to external system peripherals such as DDR, Flash memories and system
> >>>> devices. It also features onkey button input and an hardware watchdog.
> >>>> The STPMIC1 is controlled via I2C.
> >>>>
> >>>> Main driver is drivers/mfd/stpmic1 that handle I2C regmap configuration and
> >>>> irqchip. stpmic1_regulator, stpmic1_onkey and stpmic1_wdt need stpmic1 mfd
> >>>> as parent.
> >>>>
> >>>> STPMIC1 MFD and regulator drivers maybe mandatory at boot time.
> >>>>
> >>>> Pascal Paillet (7):
> >>>> changes in v7:
> >>>> * rebase on regul/for-next
> >>>>
> >>>> dt-bindings: mfd: document stpmic1
> >>>> mfd: stpmic1: add stpmic1 driver
> >>>> dt-bindings: input: document stpmic1 pmic onkey
> >>>> input: stpmic1: add stpmic1 onkey driver
> >>>> dt-bindings: watchdog: document stpmic1 pmic watchdog
> >>>> watchdog: stpmic1: add stpmic1 watchdog driver
> >>>> regulator: stpmic1: fix regulator_lock usage
> >>>>
> >>>> .../devicetree/bindings/input/st,stpmic1-onkey.txt | 28 +++
> >>>> .../devicetree/bindings/mfd/st,stpmic1.txt | 61 ++++++
> >>>> .../bindings/watchdog/st,stpmic1-wdt.txt | 11 ++
> >>>> drivers/input/misc/Kconfig | 11 ++
> >>>> drivers/input/misc/Makefile | 2 +
> >>>> drivers/input/misc/stpmic1_onkey.c | 198 +++++++++++++++++++
> >>>> drivers/mfd/Kconfig | 16 ++
> >>>> drivers/mfd/Makefile | 1 +
> >>>> drivers/mfd/stpmic1.c | 213 +++++++++++++++++++++
> >>>> drivers/regulator/stpmic1_regulator.c | 2 +-
> >>> Is it just Mark you're waiting on now?
> >> It is ok now, Mark has applied the patch.
> >> Evrey thing has been acked now. What is the nex step ?
> > Mark has applied patch 7?
> >
> > Why don't I see that? Should you have removed it from this set?
> Hi Lee, I have received an email from Mark telliing that the regulator
> patch is applied on
>
> https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
>
> I can see it on the branch regul/for-next.
Mark,
Does your patch tracker only reply to the author?
Any reason why I don't see it?
--
Lee Jones [李琼斯]
Linaro Services Technical Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2018-12-07 7:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-30 9:55 [PATCH v7 0/7] Introduce STPMIC1 PMIC Driver Pascal PAILLET-LME
2018-11-30 9:55 ` [PATCH v7 1/7] dt-bindings: mfd: document stpmic1 Pascal PAILLET-LME
2018-11-30 9:55 ` [PATCH v7 3/7] dt-bindings: input: document stpmic1 pmic onkey Pascal PAILLET-LME
2018-11-30 9:55 ` [PATCH v7 2/7] mfd: stpmic1: add stpmic1 driver Pascal PAILLET-LME
2018-11-30 9:55 ` [PATCH v7 4/7] input: stpmic1: add stpmic1 onkey driver Pascal PAILLET-LME
2018-11-30 9:55 ` [PATCH v7 5/7] dt-bindings: watchdog: document stpmic1 pmic watchdog Pascal PAILLET-LME
2018-11-30 9:55 ` [PATCH v7 6/7] watchdog: stpmic1: add stpmic1 watchdog driver Pascal PAILLET-LME
2018-11-30 9:55 ` [PATCH v7 7/7] regulator: stpmic1: fix regulator_lock usage Pascal PAILLET-LME
2018-12-03 7:11 ` [PATCH v7 0/7] Introduce STPMIC1 PMIC Driver Lee Jones
2018-12-04 15:24 ` Pascal PAILLET-LME
2018-12-05 9:36 ` Lee Jones
2018-12-05 15:36 ` Pascal PAILLET-LME
2018-12-07 7:31 ` Lee Jones [this message]
2018-12-07 12:19 ` Mark Brown
2018-12-14 12:47 ` Lee Jones
2018-12-14 14:36 ` Pascal PAILLET-LME
2019-01-15 0:48 ` dmitry.torokhov
2019-01-16 8:13 ` Lee Jones
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=20181207073132.GH26661@dell \
--to=lee.jones@linaro.org \
--cc=axel.lin@ingics.com \
--cc=benjamin.gaignard@linaro.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=eballetbo@gmail.com \
--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=robh+dt@kernel.org \
--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).