From: marek.vasut@gmail.com (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: porter: Add missing PMIC nodes
Date: Sat, 24 Feb 2018 11:05:49 +0100 [thread overview]
Message-ID: <1d93db7c-e65a-e2b3-5a65-a1eb4fa1d60e@gmail.com> (raw)
In-Reply-To: <20180223164517.aboazzeuujgtkh7q@verge.net.au>
On 02/23/2018 05:45 PM, Simon Horman wrote:
> On Sun, Feb 18, 2018 at 04:07:51PM +0100, Geert Uytterhoeven wrote:
>> Hi Marek,
>>
>> CC Steve Twiss
>>
>> On Sat, Feb 17, 2018 at 3:07 AM, Marek Vasut <marek.vasut@gmail.com> wrote:
>>> Add PMIC nodes to Porter and connect CPU DVFS supply. There is
>>> one DA9063 and one DA9210 on Porter, the only difference from
>>> the other boards is that DA9063 is at I2C address 0x5a rather
>>> than 0x58 .
>>>
>>> Signed-off-by: Marek Vasut <marek.vasut+renesas@gmail.com>
>>
>> Thanks for your patch!
>>
>>> --- a/arch/arm/boot/dts/r8a7791-porter.dts
>>> +++ b/arch/arm/boot/dts/r8a7791-porter.dts
>>> @@ -354,10 +354,47 @@
>>> clock-frequency = <400000>;
>>> };
>>>
>>> +&i2c6 {
>>> + status = "okay";
>>> + clock-frequency = <100000>;
>>> +
>>> + pmic at 5a {
>>> + compatible = "dlg,da9063";
>>
>> Does it matter that this is a DA9063L ("Variant 6B")?
>> Do we need a new compatible value, or can this be detected at runtime?
>
> Hi Marek,
>
> could you follow up on this?
Yes, ASAP, once I'm back in the office, currently I'm stuck at the airport.
--
Best regards,
Marek Vasut
next prev parent reply other threads:[~2018-02-24 10:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-17 2:07 [PATCH] ARM: dts: porter: Add missing PMIC nodes Marek Vasut
2018-02-18 15:07 ` Geert Uytterhoeven
2018-02-23 16:45 ` Simon Horman
2018-02-24 10:05 ` Marek Vasut [this message]
2018-02-24 22:11 ` Marek Vasut
2018-02-26 10:55 ` Simon Horman
2018-02-26 11:15 ` Marek Vasut
-- strict thread matches above, loose matches on Subject: below --
2018-05-23 11:43 Marek Vasut
2018-05-23 11:52 ` Geert Uytterhoeven
2018-05-23 11:54 ` Marek Vasut
2018-05-25 10:09 ` Simon Horman
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=1d93db7c-e65a-e2b3-5a65-a1eb4fa1d60e@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).