From: Marek Vasut <marek.vasut@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Lee Jones <lee.jones@linaro.org>,
Marek Vasut <marek.vasut+renesas@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: Re: [PATCH V3 2/2] mfd: Add ROHM BD9571MWV-M MFD PMIC driver
Date: Mon, 17 Jul 2017 22:46:02 +0200 [thread overview]
Message-ID: <4d4afb13-25af-afa5-2eb1-43fe9c7aa813@gmail.com> (raw)
In-Reply-To: <CAMuHMdXmPPRA00yCOiwh1mvaGAy=g_QP=9qrupnzW+f=22Wosw@mail.gmail.com>
On 07/10/2017 05:33 PM, Geert Uytterhoeven wrote:
> Hi Marek,
>
> On Tue, May 2, 2017 at 2:18 PM, Marek Vasut <marek.vasut@gmail.com> 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>
>
>> --- a/drivers/mfd/Kconfig
>> +++ b/drivers/mfd/Kconfig
>> @@ -133,6 +133,19 @@ config MFD_BCM590XX
>> help
>> Support for the BCM590xx PMUs from Broadcom
>>
>> +config MFD_BD9571MWV
>> + tristate "ROHM BD9571MWV PMIC"
>> + select MFD_CORE
>> + select REGMAP_I2C
>
> Missing "select REGMAP_IRQ".
>
> Else it fails with:
Added
--
Best regards,
Marek Vasut
prev parent reply other threads:[~2017-07-17 20:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170502121816.10572-1-marek.vasut+renesas@gmail.com>
2017-05-02 12:18 ` Marek Vasut
2017-06-27 9:54 ` Marek Vasut
2017-07-03 11:55 ` Lee Jones
2017-07-03 12:03 ` Marek Vasut
2017-07-03 13:48 ` Lee Jones
2017-07-03 14:16 ` Marek Vasut
2017-07-03 15:21 ` Lee Jones
2017-07-10 15:33 ` Geert Uytterhoeven
2017-07-17 20:46 ` 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=4d4afb13-25af-afa5-2eb1-43fe9c7aa813@gmail.com \
--to=marek.vasut@gmail.com \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--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®