From: 'Stephen Boyd' <sboyd@codeaurora.org>
To: Sricharan <sricharan@codeaurora.org>
Cc: mturquette@baylibre.com, linux-clk@vger.kernel.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
rnayak@codeaurora.org, stanimir.varbanov@linaro.org
Subject: Re: [PATCH 1/3] clk: qcom: gdsc: Add support for gdscs with HW control
Date: Thu, 3 Nov 2016 13:05:50 -0700 [thread overview]
Message-ID: <20161103200550.GZ16026@codeaurora.org> (raw)
In-Reply-To: <000f01d235d6$6e63e680$4b2bb380$@codeaurora.org>
On 11/03, Sricharan wrote:
> Ok, so the video ip core, has a hw control signal/bit.
> I checked this by dumping this out that, the moment the
> gdsc is put to hw control, the video ip's hw control bit also
> gets asserted/set. so this means that video ip's bit get
> aligned with the gdsc setting. so this should avoid the
> glitches, right ?
>
Yes that matches my understanding. Thanks for confirming.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2016-11-03 20:05 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-24 10:18 [PATCH 0/3] clk: qcom: Add support for hw controlled gdscs/clocks Sricharan R
2016-10-24 10:18 ` [PATCH 1/3] clk: qcom: gdsc: Add support for gdscs with HW control Sricharan R
2016-10-25 13:01 ` Stanimir Varbanov
2016-10-26 4:12 ` Sricharan
2016-11-02 0:18 ` Stephen Boyd
2016-11-02 6:50 ` Sricharan
2016-11-02 6:53 ` Sricharan
2016-11-02 17:59 ` 'Stephen Boyd'
2016-11-03 13:30 ` Sricharan
2016-11-03 20:05 ` 'Stephen Boyd' [this message]
2016-10-24 10:18 ` [PATCH 2/3] clk: qcom: Put venus core0/1 gdscs to hw control mode Sricharan R
2016-10-24 10:18 ` [PATCH 3/3] clk: qcom: Set BRANCH_HALT_DELAY flags for venus core0/1 clks Sricharan R
2016-11-03 20:34 ` Stephen Boyd
2016-11-04 9:09 ` Sricharan
2016-11-04 20:18 ` 'Stephen Boyd'
2016-11-07 5:48 ` Rajendra Nayak
2016-11-08 22:33 ` 'Stephen Boyd'
2016-11-09 16:56 ` Sricharan
2016-11-10 2:32 ` Rajendra Nayak
2016-11-10 3:28 ` Sricharan
2016-11-10 23:30 ` 'Stephen Boyd'
2016-11-14 3:51 ` Sricharan
2016-12-12 15:40 ` Stanimir Varbanov
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=20161103200550.GZ16026@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=rnayak@codeaurora.org \
--cc=sricharan@codeaurora.org \
--cc=stanimir.varbanov@linaro.org \
/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).