From: Stephen Boyd <sboyd@codeaurora.org>
To: Leo Yan <leo.yan@linaro.org>
Cc: Michael Turquette <mturquette@baylibre.com>,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
Haojian Zhuang <haojian.zhuang@linaro.org>,
Guodong Xu <guodong.xu@linaro.org>,
John Stultz <john.stultz@linaro.org>
Subject: Re: [PATCH] clk: hisilicon: fix lock assignment
Date: Fri, 20 Jan 2017 14:58:27 -0800 [thread overview]
Message-ID: <20170120225827.GB8009@codeaurora.org> (raw)
In-Reply-To: <1484727218-3499-1-git-send-email-leo.yan@linaro.org>
On 01/18, Leo Yan wrote:
> In clock driver initialize phase the spinlock is missed to assignment
> to struct clkgate_separated, finally there have no locking to protect
> exclusive accessing for clock registers.
>
> This bug introduces the console has no output after enable coresight
> driver on 96borads Hikey; this is because console using UART3, which
s/borads/boards/
> has shared the same register with coresight clock enabling bit. After
> applied this patch it can assign lock properly to protect exclusive
> accessing, and console can work well after enabled coresight modules.
>
> Signed-off-by: Leo Yan <leo.yan@linaro.org>
Is there a Fixes: tag needed?
Is coresight support merged into Linus' tree? I want to know if
this needs to be applied for v4.10 or can wait until v4.11.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2017-01-20 22:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 8:13 [PATCH] clk: hisilicon: fix lock assignment Leo Yan
2017-01-20 22:58 ` Stephen Boyd [this message]
2017-01-21 2:16 ` Leo Yan
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=20170120225827.GB8009@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=guodong.xu@linaro.org \
--cc=haojian.zhuang@linaro.org \
--cc=john.stultz@linaro.org \
--cc=leo.yan@linaro.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.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