[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOf5uwk3FJ4K4gL8xNNAp-z_AesjwTwSz986gfveVJsOU+N8Ow@mail.gmail.com>
Date: Mon, 26 Sep 2016 15:56:39 +0200
From: Michael Trimarchi <michael@...rulasolutions.com>
To: Fabio Estevam <festevam@...il.com>
Cc: Matteo Lisi <matteo.lisi@...icam.com>,
Jagan Teki <jagan@...rulasolutions.com>,
Jagan Teki <jagannadh.teki@...il.com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
Sascha Hauer <kernel@...gutronix.de>,
Fabio Estevam <fabio.estevam@....com>,
Shawn Guo <shawnguo@...nel.org>
Subject: Re: [PATCH v4 2/5] ARM: dts: imx6q: Add Engicam i.CoreM6 Quad/Dual
initial support
Hi
On Mon, Sep 26, 2016 at 3:55 PM, Fabio Estevam <festevam@...il.com> wrote:
> On Mon, Sep 26, 2016 at 10:54 AM, Michael Trimarchi
> <michael@...rulasolutions.com> wrote:
>
>>> Why don't you simply do like this?
>>>
>>> reg_3p3v: regulator-3p3v {
>>> compatible = "regulator-fixed";
>>> regulator-name = "3P3V";
>>> regulator-min-microvolt = <3300000>;
>>> regulator-max-microvolt = <3300000>;
>>> };
>>
>> Should dts rispect the schematic connection?
>
> Yes
So boot on and always on are used to declare their status and their
behavionr. I don't
see the point to not specify them in this way
Michael
--
| Michael Nazzareno Trimarchi Amarula Solutions BV |
| COO - Founder Cruquiuskade 47 |
| +31(0)851119172 Amsterdam 1018 AM NL |
| [`as] http://www.amarulasolutions.com |
Powered by blists - more mailing lists