All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Griffin <peter.griffin@linaro.org>
To: Lee Jones <lee.jones@linaro.org>
Cc: linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, kernel@stlinux.com,
	patrice.chotard@st.com, devicetree@vger.kernel.org
Subject: Re: [PATCH] ARM: sti: stih410-clocks: Add PROC_STFE as a critical clock
Date: Wed, 26 Oct 2016 09:56:20 +0100	[thread overview]
Message-ID: <20161026085620.GA5476@griffinp-ThinkPad-X1-Carbon-2nd> (raw)
In-Reply-To: <20161026085141.GJ8574@dell>

Hi Lee,

On Wed, 26 Oct 2016, Lee Jones wrote:

> > > > If the clock is enabled when Linux boots, the Linux clock framework *needs*
> > > > to assume the hardware may have been used in previous boot stages, and it should
> > > > not attempt to disable the clock.
> > > 
> > > None of the boot loaders we use do this.
> > 
> > But the Linux kernel isn't just used by us. It is not uncommon for STB
> > bootloaders to get information from the frontend as part of the boot process. 
> 
> Okay, this is the clincher.  Since we need to support non-standard
> bootloaders, it's difficult to guarantee that the clock will be
> disabled at boot.  For this reason, I believe that we can call this a
> critical clock.
> 
That's good news as the STi maintainer already acked and applied the patch.

Peter.

WARNING: multiple messages have this Message-ID (diff)
From: peter.griffin@linaro.org (Peter Griffin)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: sti: stih410-clocks: Add PROC_STFE as a critical clock
Date: Wed, 26 Oct 2016 09:56:20 +0100	[thread overview]
Message-ID: <20161026085620.GA5476@griffinp-ThinkPad-X1-Carbon-2nd> (raw)
In-Reply-To: <20161026085141.GJ8574@dell>

Hi Lee,

On Wed, 26 Oct 2016, Lee Jones wrote:

> > > > If the clock is enabled when Linux boots, the Linux clock framework *needs*
> > > > to assume the hardware may have been used in previous boot stages, and it should
> > > > not attempt to disable the clock.
> > > 
> > > None of the boot loaders we use do this.
> > 
> > But the Linux kernel isn't just used by us. It is not uncommon for STB
> > bootloaders to get information from the frontend as part of the boot process. 
> 
> Okay, this is the clincher.  Since we need to support non-standard
> bootloaders, it's difficult to guarantee that the clock will be
> disabled at boot.  For this reason, I believe that we can call this a
> critical clock.
> 
That's good news as the STi maintainer already acked and applied the patch.

Peter.

  reply	other threads:[~2016-10-26  8:56 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-18 15:35 [PATCH] ARM: sti: stih410-clocks: Add PROC_STFE as a critical clock Peter Griffin
2016-10-18 15:35 ` Peter Griffin
2016-10-18 15:35 ` Peter Griffin
2016-10-20 13:50 ` Patrice Chotard
2016-10-20 13:50   ` Patrice Chotard
2016-10-20 13:50   ` Patrice Chotard
2016-10-24  8:53 ` Lee Jones
2016-10-24  8:53   ` Lee Jones
2016-10-24  8:53   ` Lee Jones
2016-10-24 13:44   ` Peter Griffin
2016-10-24 13:44     ` Peter Griffin
2016-10-24 13:44     ` Peter Griffin
2016-10-25  7:42     ` Lee Jones
2016-10-25  7:42       ` Lee Jones
2016-10-25  7:42       ` Lee Jones
2016-10-25  9:39       ` Peter Griffin
2016-10-25  9:39         ` Peter Griffin
2016-10-25 10:01         ` Lee Jones
2016-10-25 10:01           ` Lee Jones
2016-10-25 10:01           ` Lee Jones
2016-10-25 13:49           ` Peter Griffin
2016-10-25 13:49             ` Peter Griffin
2016-10-26  8:51             ` Lee Jones
2016-10-26  8:51               ` Lee Jones
2016-10-26  8:51               ` Lee Jones
2016-10-26  8:56               ` Peter Griffin [this message]
2016-10-26  8:56                 ` Peter Griffin
2016-10-26 13:00                 ` Lee Jones
2016-10-26 13:00                   ` Lee Jones

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=20161026085620.GA5476@griffinp-ThinkPad-X1-Carbon-2nd \
    --to=peter.griffin@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kernel@stlinux.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patrice.chotard@st.com \
    /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.