From: Stefan Agner <stefan@agner.ch>
To: Lee Jones <lee.jones@linaro.org>
Cc: lgirdwood@gmail.com, broonie@kernel.org, khilman@baylibre.com,
carlo@caione.org, b.galvani@gmail.com, max.oss.09@gmail.com,
marcel@ziswiler.com, linux@armlinux.org.uk, galak@codeaurora.org,
ijc+devicetree@hellion.org.uk, mark.rutland@arm.com,
pawel.moll@arm.com, robh+dt@kernel.org, linux@roeck-us.net,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org
Subject: Re: [PATCH v5 0/5] regulator: add Ricoh RN5T567 PMIC support
Date: Wed, 29 Jun 2016 01:15:36 -0700 [thread overview]
Message-ID: <c82c2ab2fecc805746cb719db5e34723@agner.ch> (raw)
In-Reply-To: <20160629081208.GI29166@dell>
On 2016-06-29 01:12, Lee Jones wrote:
> On Tue, 28 Jun 2016, Stefan Agner wrote:
>
>> This patchset adds RN5T567 PMIC support which is used on the
>> Toradex Colibri iMX7S/iMX7D modules. The existing RN5T618 is from
>> the same family, hence this patchset uses the same driver and adds
>> variant support.
>>
>> The Colibris currently do not use the PMIC's power off capabilities,
>> as do the current users of that PMIC driver. Therefore this patchset
>> also makes the use of the system-power-controller property mandatory
>> if the power off capabilties are required.
>>
>> Changes since v4:
>> - Spell check in patch 5 and added Acks
>>
>> Changes since v3:
>> - Use RN5T618_REPCNT_REPWRON macro when writing RN5T618_REPCNT register
>>
>> Changes since v2:
>> - Elevate restart priority to 192 to make sure PMIC takes presedence
>> over SoC level restart capabilities (e.g. watchdog)
>> - Print a warning if poweroff callback is already assigned
>> - Reorder of_id and variant assignment
>> - Lower delay to 1ms and justify why it is required
>> - Fix DCDC count and a typos in device tree bindings
>>
>> Changes since v1:
>> - Removed obsolete include <asm/system_misc.h>
>>
>> Stefan Agner (5):
>> ARM: dts: meson: minix-neo-x8: define PMIC as power controller
>> mfd: add Ricoh RN5T567 PMIC support
>> regulator: rn5t618: add RN5T567 PMIC support
>> mfd: rn5t618: register power off callback optionally
>> mfd: rn5t618: register restart handler
>>
>> Documentation/devicetree/bindings/mfd/rn5t618.txt | 19 +++---
>> arch/arm/boot/dts/meson8-minix-neo-x8.dts | 1 +
>> drivers/mfd/Kconfig | 7 ++-
>> drivers/mfd/rn5t618.c | 70 +++++++++++++++++++----
>> drivers/regulator/Kconfig | 5 +-
>> drivers/regulator/rn5t618-regulator.c | 40 +++++++++++--
>> include/linux/mfd/rn5t618.h | 13 +++++
>> 7 files changed, 126 insertions(+), 29 deletions(-)
>
> Looks like you have all your Acks now. How do you want to play this?
> Would you like me to take the set through MFD and provide the other
> Maintainers with a branch to pull from, or did you have other ideas?
I did not thought about that really, I guess you have a usual way for
mixed regulator/mfd patchsets? Taking it through MFD sounds good to
me...
--
Stefan
next prev parent reply other threads:[~2016-06-29 8:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-29 5:53 [PATCH v5 0/5] regulator: add Ricoh RN5T567 PMIC support Stefan Agner
2016-06-29 5:53 ` [PATCH v5 1/5] ARM: dts: meson: minix-neo-x8: define PMIC as power controller Stefan Agner
2016-06-29 5:53 ` [PATCH v5 2/5] mfd: add Ricoh RN5T567 PMIC support Stefan Agner
2016-06-29 5:53 ` [PATCH v5 3/5] regulator: rn5t618: add " Stefan Agner
[not found] ` <20160629055322.23038-1-stefan-XLVq0VzYD2Y@public.gmane.org>
2016-06-29 5:53 ` [PATCH v5 4/5] mfd: rn5t618: register power off callback optionally Stefan Agner
2016-06-29 5:53 ` [PATCH v5 5/5] mfd: rn5t618: register restart handler Stefan Agner
2016-06-29 18:05 ` Applied "mfd: rn5t618: Register restart handler" to the regulator tree Mark Brown
2016-06-29 8:12 ` [PATCH v5 0/5] regulator: add Ricoh RN5T567 PMIC support Lee Jones
2016-06-29 8:15 ` Stefan Agner [this message]
2016-06-29 16:25 ` [GIT PULL] Immutable branch between MFD, Regulator and ARM for v4.8 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=c82c2ab2fecc805746cb719db5e34723@agner.ch \
--to=stefan@agner.ch \
--cc=b.galvani@gmail.com \
--cc=broonie@kernel.org \
--cc=carlo@caione.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=khilman@baylibre.com \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=linux@roeck-us.net \
--cc=marcel@ziswiler.com \
--cc=mark.rutland@arm.com \
--cc=max.oss.09@gmail.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.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).