[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170717185734.r6vmeherekkhacoh@rob-hp-laptop>
Date: Mon, 17 Jul 2017 13:57:34 -0500
From: Rob Herring <robh@...nel.org>
To: Leonard Crestez <leonard.crestez@....com>
Cc: Srinivas Kandagatla <srinivas.kandagatla@...aro.org>,
Shawn Guo <shawnguo@...nel.org>,
Zhang Rui <rui.zhang@...el.com>,
Eduardo Valentin <edubezval@...il.com>,
Mark Rutland <mark.rutland@....com>,
Lothar Waßmann <LW@...O-electronics.de>,
Dong Aisheng <aisheng.dong@....com>,
Bai Ping <ping.bai@....com>, Anson Huang <Anson.Huang@....com>,
Octavian Purdila <octavian.purdila@....com>,
Fabio Estevam <fabio.estevam@....com>,
linux-pm@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 1/5] thermal: imx: Add nvmem-cells alternate binding
for OCOTP access
On Fri, Jul 14, 2017 at 05:11:06PM +0300, Leonard Crestez wrote:
> On newer imx SOCs accessing OCOTP directly is wrong because the ocotp
> clock needs to be enabled first. Add a binding for accessing the same
> values through the imx-ocotp nvmem driver using nvmem-cells. This is
> similar to other thermal drivers.
>
> The old binding is preserved for compatibility and because it still
> works fine on imx6qdl series chips.
>
> In theory this problem could be solved by adding a reference to the
> OCOTP clock instead but it is better to hide such details in a specific
> nvmem driver.
>
> Signed-off-by: Leonard Crestez <leonard.crestez@....com>
> ---
> Documentation/devicetree/bindings/thermal/imx-thermal.txt | 7 +++++++
> 1 file changed, 7 insertions(+)
Acked-by: Rob Herring <robh@...nel.org>
Powered by blists - more mailing lists