From: Marek Vasut <marek.vasut@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Simon Horman <horms+renesas@verge.net.au>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Marek Vasut <marek.vasut+renesas@gmail.com>
Subject: Re: [PATCH] ARM: dts: r8a7792: blanche: Add IIC3 and DA9063 PMIC node
Date: Thu, 2 May 2019 16:07:00 +0200 [thread overview]
Message-ID: <d7455e6c-f2b7-3bfc-29a1-78ee632c050e@gmail.com> (raw)
In-Reply-To: <CAMuHMdV1K+0yCbdDD37oeOCQRs7n2-06SQi=6pX_NY0cVcPcWw@mail.gmail.com>
On 3/19/19 11:26 AM, Geert Uytterhoeven wrote:
> Hi Marek,
>
> On Mon, Mar 4, 2019 at 9:00 PM <marek.vasut@gmail.com> wrote:
>> From: Marek Vasut <marek.vasut+renesas@gmail.com>
>>
>> Add IIC3 node to R8A7792 SoC device tree and a DA9063 PMIC node
>> to V2H Blanche board device tree.
>>
>> Signed-off-by: Marek Vasut <marek.vasut+renesas@gmail.com>
>
> Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
>
>> --- a/arch/arm/boot/dts/r8a7792-blanche.dts
>> +++ b/arch/arm/boot/dts/r8a7792-blanche.dts
>> @@ -308,6 +308,26 @@
>> };
>> };
>>
>> +&iic3 {
>> + status = "okay";
>> +
>> + pmic@58 {
>> + compatible = "dlg,da9063";
>> + reg = <0x58>;
>> + interrupt-parent = <&irqc>;
>> + interrupts = <2 IRQ_TYPE_LEVEL_LOW>;
>
> I've just realized none of the R-Car Gen2 boards configure pinctrl for the
> IRQC2 line (intc_irq2/intc), so they all rely on the boot loader doing that.
I just sent out a patch
--
Best regards,
Marek Vasut
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-05-02 14:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-04 19:59 [PATCH] ARM: dts: r8a7792: blanche: Add IIC3 and DA9063 PMIC node marek.vasut
2019-03-08 13:38 ` Simon Horman
2019-03-19 10:26 ` Geert Uytterhoeven
2019-05-02 14:07 ` 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=d7455e6c-f2b7-3bfc-29a1-78ee632c050e@gmail.com \
--to=marek.vasut@gmail.com \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=horms+renesas@verge.net.au \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).