All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Lothar Waßmann" <LW@KARO-electronics.de>
To: Fabio Estevam <festevam@gmail.com>
Cc: Bai Ping <ping.bai@nxp.com>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Eduardo Valentin <edubezval@gmail.com>,
	Sascha Hauer <kernel@pengutronix.de>,
	Fabio Estevam <fabio.estevam@nxp.com>,
	Zhang Rui <rui.zhang@intel.com>,
	Leonard Crestez <leonard.crestez@nxp.com>,
	Shawn Guo <shawnguo@kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 2/2] ARM: dts: imx6ul: Add imx6ul-tempmon
Date: Mon, 12 Jun 2017 15:37:52 +0200	[thread overview]
Message-ID: <20170612153752.3b71516c@karo-electronics.de> (raw)
In-Reply-To: <CAOMZO5Dm8+1Ddh1QqkgNLbSrZPQgFL=EO6NcjusXA0Vi9mvXeg@mail.gmail.com>

Hi,

On Mon, 12 Jun 2017 10:22:45 -0300 Fabio Estevam wrote:
> On Mon, Jun 12, 2017 at 8:47 AM, Leonard Crestez
> <leonard.crestez@nxp.com> wrote:
> 
> > However it seems that this might be accidental, it just happens that
> > the OCOTP clock starts as enabled and is only disabled later in the
> 
> Most likely because U-Boot enabled the OCOTP clock as it reads the
> speed grading fuse.
>
No, the imx6q_opp_check_speed_grading() runs on an i.MX6Q which, as
mentioned in my other mail <20170612124029.1643469d@karo-electronics.de>,
does not require any clock to be enabled for accessing the OCOTP regs.


Lothar Waßmann

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: LW@KARO-electronics.de (Lothar Waßmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: dts: imx6ul: Add imx6ul-tempmon
Date: Mon, 12 Jun 2017 15:37:52 +0200	[thread overview]
Message-ID: <20170612153752.3b71516c@karo-electronics.de> (raw)
In-Reply-To: <CAOMZO5Dm8+1Ddh1QqkgNLbSrZPQgFL=EO6NcjusXA0Vi9mvXeg@mail.gmail.com>

Hi,

On Mon, 12 Jun 2017 10:22:45 -0300 Fabio Estevam wrote:
> On Mon, Jun 12, 2017 at 8:47 AM, Leonard Crestez
> <leonard.crestez@nxp.com> wrote:
> 
> > However it seems that this might be accidental, it just happens that
> > the OCOTP clock starts as enabled and is only disabled later in the
> 
> Most likely because U-Boot enabled the OCOTP clock as it reads the
> speed grading fuse.
>
No, the imx6q_opp_check_speed_grading() runs on an i.MX6Q which, as
mentioned in my other mail <20170612124029.1643469d@karo-electronics.de>,
does not require any clock to be enabled for accessing the OCOTP regs.


Lothar Wa?mann

WARNING: multiple messages have this Message-ID (diff)
From: "Lothar Waßmann" <LW@KARO-electronics.de>
To: Fabio Estevam <festevam@gmail.com>
Cc: Leonard Crestez <leonard.crestez@nxp.com>,
	Bai Ping <ping.bai@nxp.com>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	Shawn Guo <shawnguo@kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Eduardo Valentin <edubezval@gmail.com>,
	Sascha Hauer <kernel@pengutronix.de>,
	Fabio Estevam <fabio.estevam@nxp.com>,
	Zhang Rui <rui.zhang@intel.com>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 2/2] ARM: dts: imx6ul: Add imx6ul-tempmon
Date: Mon, 12 Jun 2017 15:37:52 +0200	[thread overview]
Message-ID: <20170612153752.3b71516c@karo-electronics.de> (raw)
In-Reply-To: <CAOMZO5Dm8+1Ddh1QqkgNLbSrZPQgFL=EO6NcjusXA0Vi9mvXeg@mail.gmail.com>

Hi,

On Mon, 12 Jun 2017 10:22:45 -0300 Fabio Estevam wrote:
> On Mon, Jun 12, 2017 at 8:47 AM, Leonard Crestez
> <leonard.crestez@nxp.com> wrote:
> 
> > However it seems that this might be accidental, it just happens that
> > the OCOTP clock starts as enabled and is only disabled later in the
> 
> Most likely because U-Boot enabled the OCOTP clock as it reads the
> speed grading fuse.
>
No, the imx6q_opp_check_speed_grading() runs on an i.MX6Q which, as
mentioned in my other mail <20170612124029.1643469d@karo-electronics.de>,
does not require any clock to be enabled for accessing the OCOTP regs.


Lothar Waßmann

  reply	other threads:[~2017-06-12 13:37 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-08 16:26 [PATCH 1/2] ARM: imx_v6_v7_defconfig: Set THERMAL_WRITABLE_TRIPS=y for testing Leonard Crestez
2017-06-08 16:26 ` Leonard Crestez
2017-06-08 16:26 ` Leonard Crestez
2017-06-08 16:26 ` [PATCH 2/2] ARM: dts: imx6ul: Add imx6ul-tempmon Leonard Crestez
2017-06-08 16:26   ` Leonard Crestez
2017-06-08 16:26   ` Leonard Crestez
2017-06-08 16:45   ` Fabio Estevam
2017-06-08 16:45     ` Fabio Estevam
2017-06-09 10:58     ` Leonard Crestez
2017-06-09 10:58       ` Leonard Crestez
2017-06-09 12:18       ` Fabio Estevam
2017-06-09 12:18         ` Fabio Estevam
2017-06-09 13:46       ` Lothar Waßmann
2017-06-09 13:46         ` Lothar Waßmann
2017-06-09 13:46         ` Lothar Waßmann
2017-06-09 15:34         ` Leonard Crestez
2017-06-09 15:34           ` Leonard Crestez
2017-06-12 10:40           ` Lothar Waßmann
2017-06-12 10:40             ` Lothar Waßmann
2017-06-12 11:47             ` Leonard Crestez
2017-06-12 11:47               ` Leonard Crestez
2017-06-12 13:22               ` Fabio Estevam
2017-06-12 13:22                 ` Fabio Estevam
2017-06-12 13:37                 ` Lothar Waßmann [this message]
2017-06-12 13:37                   ` Lothar Waßmann
2017-06-12 13:37                   ` Lothar Waßmann
2017-06-12 14:30                   ` Fabio Estevam
2017-06-12 14:30                     ` Fabio Estevam
2017-06-15  1:35 ` [PATCH 1/2] ARM: imx_v6_v7_defconfig: Set THERMAL_WRITABLE_TRIPS=y for testing Shawn Guo
2017-06-15  1:35   ` Shawn Guo

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=20170612153752.3b71516c@karo-electronics.de \
    --to=lw@karo-electronics.de \
    --cc=edubezval@gmail.com \
    --cc=fabio.estevam@nxp.com \
    --cc=festevam@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=leonard.crestez@nxp.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=ping.bai@nxp.com \
    --cc=rui.zhang@intel.com \
    --cc=shawnguo@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.