From: marek.vasut@gmail.com (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: shmobile: silk: Add DA9063 PMIC node
Date: Thu, 2 Aug 2018 15:55:55 +0200 [thread overview]
Message-ID: <42d09bc8-a883-c3af-b0d6-0087b6e2558e@gmail.com> (raw)
In-Reply-To: <CAMuHMdXib8fz3c41RX-70eA5w4ThM6e02ybmX=N=xXR6=F80KA@mail.gmail.com>
On 08/01/2018 02:32 PM, Geert Uytterhoeven wrote:
> Hi Marek,
Hi,
> On Mon, Jul 30, 2018 at 1:18 PM Marek Vasut <marek.vasut@gmail.com> wrote:
>> Add DA9063 PMIC node to the I2C bus.
>>
>> Signed-off-by: Marek Vasut <marek.vasut+renesas@gmail.com>
>
> Thanks for your patch!
>
> Oneline-summary prefix should be "ARM: dts: silk:".
Right, fixed
>> --- a/arch/arm/boot/dts/r8a7794-silk.dts
>> +++ b/arch/arm/boot/dts/r8a7794-silk.dts
>> @@ -403,6 +403,18 @@
>> pinctrl-names = "i2c-hdmi";
>>
>> clock-frequency = <400000>;
>> +
>> + pmic at 5a {
>
> Hmm, the da9063 is actually connected to two i2c buses: i2c1 (3.3v)
> and i2c7 (1.8v).
> On Koelsch, we describe the 1.8v connection, as that i2c bus
> ("i2c_dvfs") is meant
> for power control.
On Koelsch, the pmic is sitting on i2c6 only. What am I missing ?
>> + compatible = "dlg,da9063";
>> + reg = <0x5a>;
>> + interrupt-parent = <&irqc0>;
>> + interrupts = <2 IRQ_TYPE_LEVEL_LOW>;
>
> According to my schematics, the interrupt is connected to GP3_31?
Yeah, fixed, thanks.
>> + interrupt-controller;
>> +
>> + wdt {
>> + compatible = "dlg,da9063-watchdog";
>> + };
>> + };
>> };
>
> Gr{oetje,eeting}s,
>
> Geert
>
--
Best regards,
Marek Vasut
next prev parent reply other threads:[~2018-08-02 13:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-30 11:18 [PATCH] ARM: shmobile: silk: Add DA9063 PMIC node Marek Vasut
2018-08-01 12:32 ` Geert Uytterhoeven
2018-08-02 13:55 ` Marek Vasut [this message]
2018-08-02 14:07 ` Geert Uytterhoeven
2018-08-03 10:12 ` Marek Vasut
2018-08-03 10:48 ` Wolfram Sang
2018-08-03 11:40 ` Marek Vasut
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=42d09bc8-a883-c3af-b0d6-0087b6e2558e@gmail.com \
--to=marek.vasut@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).