All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@codeaurora.org>
To: Carlo Caione <carlo@caione.org>
Cc: mturquette@baylibre.com, linux-clk@vger.kernel.org,
	dvhart@infradead.org, pierre-louis.bossart@linux.intel.com,
	linux@endlessm.com, eballetbo@gmail.com,
	andriy.shevchenko@linux.intel.com,
	Carlo Caione <carlo@endlessm.com>
Subject: Re: [PATCH v3] clk: x86: Do not gate clocks enabled by the firmware
Date: Tue, 18 Jul 2017 16:24:51 -0700	[thread overview]
Message-ID: <20170718232451.GI18179@codeaurora.org> (raw)
In-Reply-To: <20170714082356.28117-1-carlo@caione.org>

On 07/14, Carlo Caione wrote:
> From: Carlo Caione <carlo@endlessm.com>
> 
> Read the enable register to determine if the clock is already in use by
> the firmware. In this case avoid gating the clock.
> 
> Tested-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>
> Acked-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> Acked-by: Darren Hart (VMware) <dvhart@infradead.org>
> Signed-off-by: Carlo Caione <carlo@endlessm.com>
> ---

Applied to clk-fixes and added a Fixes tag.

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

  reply	other threads:[~2017-07-18 23:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-14  8:23 [PATCH v3] clk: x86: Do not gate clocks enabled by the firmware Carlo Caione
2017-07-18 23:24 ` Stephen Boyd [this message]
2017-09-07  9:22 ` Carlo Caione
2017-09-07 11:59   ` Pierre-Louis Bossart
2017-09-07 21:51     ` Pierre-Louis Bossart
2017-09-08  8:05       ` Carlo Caione
2017-09-18  8:05       ` Andy Shevchenko
2017-09-22 21:36         ` Darren Hart
2017-09-22 21:47           ` Carlo Caione
2017-09-22 22:17           ` Pierre-Louis Bossart

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=20170718232451.GI18179@codeaurora.org \
    --to=sboyd@codeaurora.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=carlo@caione.org \
    --cc=carlo@endlessm.com \
    --cc=dvhart@infradead.org \
    --cc=eballetbo@gmail.com \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux@endlessm.com \
    --cc=mturquette@baylibre.com \
    --cc=pierre-louis.bossart@linux.intel.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.