From: Stephen Boyd <sboyd@codeaurora.org>
To: Lee Jones <lee.jones@linaro.org>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel@stlinux.com,
maxime.coquelin@st.com, patrice.chotard@st.com,
mturquette@baylibre.com, broonie@kernel.org,
linux-clk@vger.kernel.org, linux-spi@vger.kernel.org
Subject: Re: [PATCH 0/6] clk: sti: Add support for critical clocks
Date: Thu, 30 Jun 2016 12:23:37 -0700 [thread overview]
Message-ID: <20160630192337.GN1521@codeaurora.org> (raw)
In-Reply-To: <20160607111930.10375-1-lee.jones@linaro.org>
On 06/07, Lee Jones wrote:
> Describe the platform's critical clocks in DT, then search for them
> from the framework. This set allows us to remove the clk_ignore_unused
> kernel command line flag which has been required to achieve a successful
> boot to prompt until this point.
>
> This may not be the definitive list. There may be other clocks which
> need to be marked as critical, but we can add those as we go along.
>
I applied the three clk ones to an immutable branch named
'clk-st-critical' in the clk tree and merged this into clk-next.
I'm not comfortable taking the spi patch as I suspect that will
break something unless the dts patches are applied.
Please use this branch to base your dts and spi patches on so it
can be merged through arm-soc without introducing some bisection
hole.
The following changes since commit 1a695a905c18548062509178b98bc91e67510864:
Linux 4.7-rc1 (2016-05-29 09:29:24 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git clk-st-critical
for you to fetch changes up to 6ca59e6e1fc3a8d7ccbf85ff036bd6ff40847c1a:
clk: st: clkgen-pll: Detect critical clocks (2016-06-30 12:17:11 -0700)
----------------------------------------------------------------
Lee Jones (3):
clk: st: clk-flexgen: Detect critical clocks
clk: st: clkgen-fsyn: Detect critical clocks
clk: st: clkgen-pll: Detect critical clocks
drivers/clk/st/clk-flexgen.c | 4 +++-
drivers/clk/st/clkgen-fsyn.c | 10 +++++++---
drivers/clk/st/clkgen-pll.c | 27 +++++++++++++++++----------
3 files changed, 27 insertions(+), 14 deletions(-)
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2016-06-30 19:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-07 11:19 [PATCH 0/6] clk: sti: Add support for critical clocks Lee Jones
2016-06-07 11:19 ` [PATCH 1/6] clk: st: clk-flexgen: Detect " Lee Jones
2016-06-07 11:19 ` [PATCH 2/6] clk: st: clkgen-fsyn: " Lee Jones
2016-06-07 11:19 ` [PATCH 3/6] clk: st: clkgen-pll: " Lee Jones
2016-06-07 11:19 ` [PATCH 4/6] ARM: sti: stih407-family: Supply defines for CLOCKGEN A0 Lee Jones
2016-06-07 11:19 ` [PATCH 5/6] ARM: sti: stih410-clocks: Identify critical clocks Lee Jones
2016-06-07 11:19 ` [PATCH 6/6] spi: st-ssc4: Remove 'no clocking' hack Lee Jones
2016-06-07 15:17 ` Mark Brown
2016-06-30 20:52 ` Lee Jones
2016-07-01 9:59 ` Mark Brown
2016-06-30 19:23 ` Stephen Boyd [this message]
2016-06-30 20:54 ` [PATCH 0/6] clk: sti: Add support for critical clocks 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=20160630192337.GN1521@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=broonie@kernel.org \
--cc=kernel@stlinux.com \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=maxime.coquelin@st.com \
--cc=mturquette@baylibre.com \
--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 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).