stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@codeaurora.org>
To: Govindraj Raja <Govindraj.Raja@imgtec.com>
Cc: linux-mips@linux-mips.org, linux-clk@vger.kernel.org,
	Michael Turquette <mturquette@baylibre.com>,
	Zdenko Pulitika <zdenko.pulitika@imgtec.com>,
	Kevin Cernekee <cernekee@chromium.org>,
	Ralf Baechle <ralf@linux-mips.org>,
	Andrew Bresticker <abrestic@chromium.org>,
	James Hartley <James.Hartley@imgtec.com>,
	Damien Horsley <Damien.Horsley@imgtec.com>,
	James Hogan <James.Hogan@imgtec.com>,
	Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>,
	Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
	stable@vger.kernel.org,
	Ezequiel Garcia <ezequiel.garcia@imgtec.com>
Subject: Re: [PATCH v6 4/4] clk: pistachio: correct critical clock list
Date: Wed, 26 Aug 2015 11:36:42 -0700	[thread overview]
Message-ID: <20150826183642.GR19120@codeaurora.org> (raw)
In-Reply-To: <1440605500-13274-5-git-send-email-Govindraj.Raja@imgtec.com>

On 08/26, Govindraj Raja wrote:
> From: "Damien.Horsley" <Damien.Horsley@imgtec.com>
> 
> Current critical clock list for pistachio enables
> only mips and sys clocks by default but there are
> also other clocks that are not claimed by anyone and
> needs to be enabled by default.
> 
> This patch updates the critical clocks that need
> to be enabled by default.
> 
> Add a separate struct to distinguish the critical clocks
> as listed:
> 1.) core clocks:
> 	a.) mips clock
> 2.) peripheral system clocks:
> 	a.) sys clock
> 	b.) sys_bus clock
> 	c.) DDR clock
> 	d.) ROM clock
> 
> Fixes: b35d7c33419c("CLK: Pistachio: Register core clocks")
> Cc: <stable@vger.kernel.org> # 4.1
> Reviewed-by: Andrew Bresticker <abrestic@chromium.org>
> Signed-off-by: Ezequiel Garcia <ezequiel.garcia@imgtec.com>
> Signed-off-by: Damien.Horsley <Damien.Horsley@imgtec.com>
> Signed-off-by: Govindraj Raja <govindraj.raja@imgtec.com>
> ---

Applied to clk-next

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project

      reply	other threads:[~2015-08-26 18:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-26 16:11 [PATCH v6 0/4] clk: pistachio: Fixes for pll calculations Govindraj Raja
2015-08-26 16:11 ` [PATCH v6 1/4] clk: pistachio: Fix 32bit integer overflows Govindraj Raja
2015-08-26 18:36   ` Stephen Boyd
2015-08-26 16:11 ` [PATCH v6 2/4] clk: pistachio: Fix override of clk-pll settings from boot loader Govindraj Raja
2015-08-26 18:36   ` Stephen Boyd
2015-08-26 16:11 ` [PATCH v6 3/4] clk: pistachio: Fix PLL rate calculation in integer mode Govindraj Raja
2015-08-26 18:36   ` Stephen Boyd
2015-08-26 16:11 ` [PATCH v6 4/4] clk: pistachio: correct critical clock list Govindraj Raja
2015-08-26 18:36   ` Stephen Boyd [this message]

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=20150826183642.GR19120@codeaurora.org \
    --to=sboyd@codeaurora.org \
    --cc=Damien.Horsley@imgtec.com \
    --cc=Govindraj.Raja@imgtec.com \
    --cc=James.Hartley@imgtec.com \
    --cc=James.Hogan@imgtec.com \
    --cc=abrestic@chromium.org \
    --cc=cernekee@chromium.org \
    --cc=ezequiel.garcia@imgtec.com \
    --cc=ezequiel@vanguardiasur.com.ar \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=mturquette@baylibre.com \
    --cc=ralf@linux-mips.org \
    --cc=sergei.shtylyov@cogentembedded.com \
    --cc=stable@vger.kernel.org \
    --cc=zdenko.pulitika@imgtec.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 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).