From: Marek Vasut <marek.vasut@gmail.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: linux-renesas-soc@vger.kernel.org,
Marek Vasut <marek.vasut+renesas@gmail.com>,
linux-kernel@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: Re: [PATCH V4 2/2] mfd: Add ROHM BD9571MWV-M MFD PMIC driver
Date: Mon, 31 Jul 2017 16:00:50 +0200 [thread overview]
Message-ID: <60189f52-b3bc-4036-a07a-0bab9c7b36f8@gmail.com> (raw)
In-Reply-To: <20170718092357.6w6yjjwny54llgqd@dell>
On 07/18/2017 11:23 AM, Lee Jones wrote:
> On Mon, 17 Jul 2017, Marek Vasut wrote:
>
>> Add the MFD part of the ROHM BD9571MWV-M PMIC driver and MAINTAINERS
>> entry. The MFD part only specifies the regmap bits for the PMIC and
>> binds the subdevs together.
>>
>> Signed-off-by: Marek Vasut <marek.vasut+renesas@gmail.com>
>> Cc: linux-kernel@vger.kernel.org
>> Cc: Geert Uytterhoeven <geert+renesas@glider.be>
>> Cc: Lee Jones <lee.jones@linaro.org>
>> ---
>> V2: - Change BD9571MWV_AVS_VD09_VID0,1,2,3 to BD9571MWV_AVS_VD09_VID(n)
>> - Change BD9571MWV_AVS_DVFS_VID0,1,2,3 to BD9571MWV_AVS_DVFS_VID(n)
>> - Make the AVS_VD09 range RW, so it can be used by the regulator
>> driver for the VD09 regulator
>> - Report the regmap read return values when attempting to read ID
>> registers fails
>> V3: No change
>> V4: select REGMAP_IRQ
>> ---
>> MAINTAINERS | 11 ++
>> drivers/mfd/Kconfig | 14 +++
>> drivers/mfd/Makefile | 1 +
>> drivers/mfd/bd9571mwv.c | 230 ++++++++++++++++++++++++++++++++++++++++++
>> include/linux/mfd/bd9571mwv.h | 115 +++++++++++++++++++++
>> 5 files changed, 371 insertions(+)
>> create mode 100644 drivers/mfd/bd9571mwv.c
>> create mode 100644 include/linux/mfd/bd9571mwv.h
>
> Applied, thanks.
I still don't see these patches in next, why ?
--
Best regards,
Marek Vasut
prev parent reply other threads:[~2017-07-31 14:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170717204512.7075-1-marek.vasut+renesas@gmail.com>
2017-07-17 20:45 ` Marek Vasut
2017-07-18 9:23 ` Lee Jones
2017-07-31 14:00 ` Marek Vasut [this message]
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=60189f52-b3bc-4036-a07a-0bab9c7b36f8@gmail.com \
--to=marek.vasut@gmail.com \
--cc=geert+renesas@glider.be \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=marek.vasut+renesas@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
all inboxes | Powered by JetHome®