From: Stephen Boyd <sboyd@codeaurora.org>
To: Lori Hikichi <lori.hikichi@broadcom.com>
Cc: Michael Turquette <mturquette@baylibre.com>,
Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
Jon Mason <jonmason@broadcom.com>,
bcm-kernel-feedback-list@broadcom.com, linux-clk@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Lori Hikichi <lhikichi@broadcom.com>
Subject: Re: [PATCH v1 3/4] clk: iproc: Allow plls to do minor rate changes without reset
Date: Thu, 28 Dec 2017 14:57:15 -0800 [thread overview]
Message-ID: <20171228225715.GV7997@codeaurora.org> (raw)
In-Reply-To: <1502737241-2040-4-git-send-email-lori.hikichi@broadcom.com>
On 08/14, Lori Hikichi wrote:
> From: Lori Hikichi <lhikichi@broadcom.com>
>
> The iproc plls are capable of doing small rate changes without the
> need for a full reset and re-lock procedure. This feature will
> allow for small tweaks to the PLL rate to occur smoothly.
>
> Signed-off-by: Lori Hikichi <lori.hikichi@broadcom.com>
> ---
Applied to clk-next
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
WARNING: multiple messages have this Message-ID (diff)
From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v1 3/4] clk: iproc: Allow plls to do minor rate changes without reset
Date: Thu, 28 Dec 2017 14:57:15 -0800 [thread overview]
Message-ID: <20171228225715.GV7997@codeaurora.org> (raw)
In-Reply-To: <1502737241-2040-4-git-send-email-lori.hikichi@broadcom.com>
On 08/14, Lori Hikichi wrote:
> From: Lori Hikichi <lhikichi@broadcom.com>
>
> The iproc plls are capable of doing small rate changes without the
> need for a full reset and re-lock procedure. This feature will
> allow for small tweaks to the PLL rate to occur smoothly.
>
> Signed-off-by: Lori Hikichi <lori.hikichi@broadcom.com>
> ---
Applied to clk-next
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2017-12-28 22:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-14 19:00 [PATCH v1 0/4] clk: iproc: Enable glitchless pll rate change Lori Hikichi
2017-08-14 19:00 ` Lori Hikichi
2017-08-14 19:00 ` [PATCH v1 1/4] clk: iproc: Allow iproc pll to runtime calculate vco parameters Lori Hikichi
2017-08-14 19:00 ` Lori Hikichi
2017-12-28 22:57 ` Stephen Boyd
2017-12-28 22:57 ` Stephen Boyd
2017-08-14 19:00 ` [PATCH v1 2/4] clk: iproc: Fix error in the pll post divider rate calculation Lori Hikichi
2017-08-14 19:00 ` Lori Hikichi
2017-12-28 22:57 ` Stephen Boyd
2017-12-28 22:57 ` Stephen Boyd
2017-08-14 19:00 ` [PATCH v1 3/4] clk: iproc: Allow plls to do minor rate changes without reset Lori Hikichi
2017-08-14 19:00 ` Lori Hikichi
2017-12-28 22:57 ` Stephen Boyd [this message]
2017-12-28 22:57 ` Stephen Boyd
2017-08-14 19:00 ` [PATCH v1 4/4] clk: iproc: Minor tidy up of iproc pll data structures Lori Hikichi
2017-08-14 19:00 ` Lori Hikichi
2017-12-28 22:57 ` Stephen Boyd
2017-12-28 22:57 ` Stephen Boyd
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=20171228225715.GV7997@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=jonmason@broadcom.com \
--cc=lhikichi@broadcom.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lori.hikichi@broadcom.com \
--cc=mturquette@baylibre.com \
--cc=rjui@broadcom.com \
--cc=sbranden@broadcom.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.