From: Jeffrey Hugo <jeffrey.l.hugo@gmail.com>
To: Harigovindan P <harigovi@codeaurora.org>
Cc: "open list:DRM PANEL DRIVERS" <dri-devel@lists.freedesktop.org>,
MSM <linux-arm-msm@vger.kernel.org>,
freedreno <freedreno@lists.freedesktop.org>,
DTML <devicetree@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>,
Rob Clark <robdclark@gmail.com>,
nganji@codeaurora.org, Sean Paul <seanpaul@chromium.org>,
kalyan_t@codeaurora.org,
"Kristian H. Kristensen" <hoegsberg@chromium.org>
Subject: Re: [Freedreno] [v1] drm/msm/dsi/pll: call vco set rate explicitly
Date: Thu, 6 Feb 2020 07:59:52 -0700 [thread overview]
Message-ID: <CAOCk7Nr9n-xLtWq=LEM-QFhJcY+QOuzazsoi-yjErA9od2Jwmw@mail.gmail.com> (raw)
In-Reply-To: <1580980321-19256-1-git-send-email-harigovi@codeaurora.org>
On Thu, Feb 6, 2020 at 2:13 AM Harigovindan P <harigovi@codeaurora.org> wrote:
>
> For a given byte clock, if VCO recalc value is exactly same as
> vco set rate value, vco_set_rate does not get called assuming
> VCO is already set to required value. But Due to GDSC toggle,
> VCO values are erased in the HW. To make sure VCO is programmed
> correctly, we forcefully call set_rate from vco_prepare.
Is this specific to certain SoCs? I don't think I've observed this.
next prev parent reply other threads:[~2020-02-06 15:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-06 9:12 [v1] drm/msm/dsi/pll: call vco set rate explicitly Harigovindan P
2020-02-06 14:59 ` Jeffrey Hugo [this message]
2020-02-07 12:38 ` [Freedreno] " harigovi
2020-02-07 14:10 ` Jeffrey Hugo
2020-02-11 5:58 ` harigovi
2020-02-11 15:44 ` Rob Clark
2020-02-11 15:59 ` Jeffrey Hugo
2020-02-12 0:28 ` Rob Clark
2020-02-12 4:05 ` Jeffrey Hugo
2020-02-12 5:10 ` Rob Clark
2020-02-17 10:42 ` harigovi
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='CAOCk7Nr9n-xLtWq=LEM-QFhJcY+QOuzazsoi-yjErA9od2Jwmw@mail.gmail.com' \
--to=jeffrey.l.hugo@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=harigovi@codeaurora.org \
--cc=hoegsberg@chromium.org \
--cc=kalyan_t@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nganji@codeaurora.org \
--cc=robdclark@gmail.com \
--cc=seanpaul@chromium.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).