linux-clk.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sylwester Nawrocki <s.nawrocki@samsung.com>
To: Alim Akhtar <alim.akhtar@samsung.com>
Cc: Krzysztof Kozlowski <k.kozlowski@samsung.com>,
	linux-arm-kernel@lists.infradead.org, thomas.ab@samsung.com,
	linux-kernel@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
	linux-clk@vger.kernel.org, sboyd@codeaurora.org,
	mturquette@baylibre.com, tomasz.figa@gmail.com
Subject: Re: [PATCH] clk: samsung: exynos7: Don't gate CMU_{CCORE, FSYS0} blocks clock
Date: Fri, 15 Apr 2016 18:34:18 +0200	[thread overview]
Message-ID: <5711180A.8030809@samsung.com> (raw)
In-Reply-To: <5710E082.2050303@samsung.com>

On 04/15/2016 02:37 PM, Alim Akhtar wrote:
> On 04/14/2016 01:20 PM, Krzysztof Kozlowski wrote:
>> > On 04/14/2016 06:42 AM, Alim Akhtar wrote:
>>> >> This patch adds CLK_IS_CRITICAL flag to ACLK_CCORE_133 and ACLK_FSYS0_200
>>> >> clocks. These clocks are critical for accessing CMU_CCORE and CMU_FSYS0
>>> >> blocks registers. Let these clocks to be enabled all the time.
>>> >>
>>> >> Signed-off-by: Alim Akhtar <alim.akhtar@samsung.com>
>>> >> ---
>>> >>   drivers/clk/samsung/clk-exynos7.c |    5 +++--
>>> >>   1 file changed, 3 insertions(+), 2 deletions(-)
>> >
>> > Reviewed-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
>> >
> Thanks Krzysztof,
> Sylwester, do you have any concern here?

I'm fine with the patch, if it fixes all the issues for you.
I will apply it and will likely send it upstream after v4.7-rc1 release.

-- 
Regards,
Sylwester

  reply	other threads:[~2016-04-15 16:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-14  4:42 [PATCH] clk: samsung: exynos7: Don't gate CMU_{CCORE, FSYS0} blocks clock Alim Akhtar
2016-04-14  7:50 ` Krzysztof Kozlowski
2016-04-15 12:37   ` Alim Akhtar
2016-04-15 16:34     ` Sylwester Nawrocki [this message]
2016-05-25  6:04       ` Alim Akhtar
2016-05-25 10:49         ` Sylwester Nawrocki
2016-05-30 12:50 ` Sylwester Nawrocki

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=5711180A.8030809@samsung.com \
    --to=s.nawrocki@samsung.com \
    --cc=alim.akhtar@samsung.com \
    --cc=k.kozlowski@samsung.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=sboyd@codeaurora.org \
    --cc=thomas.ab@samsung.com \
    --cc=tomasz.figa@gmail.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).