From: "Vaittinen, Matti" <Matti.Vaittinen@fi.rohmeurope.com>
To: "mazziesaccount@gmail.com" <mazziesaccount@gmail.com>
Cc: "corbet@lwn.net" <corbet@lwn.net>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"phil.edworthy@renesas.com" <phil.edworthy@renesas.com>,
"dmurphy@ti.com" <dmurphy@ti.com>,
"linux-leds@vger.kernel.org" <linux-leds@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-rtc@vger.kernel.org" <linux-rtc@vger.kernel.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"mchehab+samsung@kernel.org" <mchehab+samsung@kernel.org>,
"alexandre.belloni@bootlin.com" <alexandre.belloni@bootlin.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"mturquette@baylibre.com" <mturquette@baylibre.com>,
"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
"jacek.anaszewski@gmail.com" <jacek.anaszewski@gmail.com>,
"wsa+renesas@sang-engineering.com"
<wsa+renesas@sang-engineering.com>,
"a.zummo@towertech.it" <a.zummo@towertech.it>,
"linus.walleij@linaro.org" <linus.walleij@linaro.org>,
"arnd@arndb.de" <arnd@arndb.de>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"noralf@tronnes.org" <noralf@tronnes.org>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"bgolaszewski@baylibre.com" <bgolaszewski@baylibre.com>,
"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
"lee.jones@linaro.org" <lee.jones@linaro.org>,
"pavel@ucw.cz" <pavel@ucw.cz>,
"broonie@kernel.org" <broonie@kernel.org>,
"sboyd@kernel.org" <sboyd@kernel.org>
Subject: Re: [PATCH v12 00/10] Support ROHM BD71828 PMIC
Date: Mon, 20 Jan 2020 12:41:14 +0000 [thread overview]
Message-ID: <ecc8ab43dfdb78c7bcab82311f608f6d4e12dc5c.camel@fi.rohmeurope.com> (raw)
In-Reply-To: <cover.1579511114.git.matti.vaittinen@fi.rohmeurope.com>
Hello,
Do you know those days when nothing, _nothing_ just works out as
intended? Today is one of those.
On Mon, 2020-01-20 at 11:12 +0200, Matti Vaittinen wrote:
> Patch series introducing support for ROHM BD71828 PMIC
>
> ROHM BD71828 is a power management IC containing 7 bucks and 7 LDOs.
> All
> regulators can be controlled individually via I2C. Bucks 1,2,6 and
> 7 can also be assigned to a "regulator group" controlled by run-
> levels.
> Eg. Run level specific voltages and enable/disable statuses for each
> of
> these bucks can be set via register interface. The buck run-level
> group
> assignment (selection if buck is to be controlled individually or via
> run-levels) can be changed at run-time via I2C.
>
> This patch series brings only the basic support for controlling
> regulators individually via I2C.
//snip
> Patch 11:
> Allow control of GP(I)O pins on BD71828 via GPIO subsystem
>
I accidentally rebased to wrong commit and cropped the GPIO patch out
of the series. Lee - can you take the GPIO part from v11 (patch 11/13
there). It should apply cleanly and I have no changes to it. Or should
I just resend the whole series (again)?
Br,
Matti Vaittinen
next prev parent reply other threads:[~2020-01-20 12:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-20 9:12 [PATCH v12 00/10] Support ROHM BD71828 PMIC Matti Vaittinen
2020-01-20 9:12 ` [PATCH v12 01/10] dt-bindings: leds: ROHM BD71282 PMIC LED driver Matti Vaittinen
2020-01-20 9:13 ` [PATCH v12 02/10] dt-bindings: mfd: Document ROHM BD71828 bindings Matti Vaittinen
2020-01-20 9:17 ` [PATCH v12 03/10] mfd: rohm PMICs - use platform_device_id to match MFD sub-devices Matti Vaittinen
2020-01-20 9:18 ` [PATCH v12 04/10] mfd: bd718x7: Add compatible for BD71850 Matti Vaittinen
2020-01-20 9:18 ` [PATCH v12 05/10] mfd: bd71828: Support ROHM BD71828 PMIC - core Matti Vaittinen
2020-01-20 9:19 ` [PATCH v12 06/10] mfd: bd71828: Add power-key support Matti Vaittinen
2020-01-20 9:19 ` [PATCH v12 07/10] clk: bd718x7: Support ROHM BD71828 clk block Matti Vaittinen
2020-01-20 9:21 ` [PATCH v12 08/10] regulator: bd718x7: Split driver to common and bd718x7 specific parts Matti Vaittinen
2020-01-20 9:21 ` [PATCH v12 09/10] mfd: bd70528: Fix hour register mask Matti Vaittinen
2020-01-20 9:22 ` [PATCH v12 10/10] rtc: bd70528: add BD71828 support Matti Vaittinen
2020-01-20 12:41 ` Vaittinen, Matti [this message]
2020-01-20 13:41 ` [PATCH v12 00/10] Support ROHM BD71828 PMIC Vaittinen, Matti
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=ecc8ab43dfdb78c7bcab82311f608f6d4e12dc5c.camel@fi.rohmeurope.com \
--to=matti.vaittinen@fi.rohmeurope.com \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=arnd@arndb.de \
--cc=bgolaszewski@baylibre.com \
--cc=broonie@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=dmurphy@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=jacek.anaszewski@gmail.com \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mazziesaccount@gmail.com \
--cc=mchehab+samsung@kernel.org \
--cc=mturquette@baylibre.com \
--cc=noralf@tronnes.org \
--cc=pavel@ucw.cz \
--cc=phil.edworthy@renesas.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=wsa+renesas@sang-engineering.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).