devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Saeed Nowshadi <saeed.nowshadi@xilinx.com>
To: <linux-clk@vger.kernel.org>, <devicetree@vger.kernel.org>
Cc: <mturquette@baylibre.com>, <sboyd@kernel.org>,
	<robh+dt@kernel.org>, <git-dev@xilinx.com>,
	Saeed Nowshadi <saeed.nowshadi@xilinx.com>
Subject: [PATCH 0/2] clk: si570: Skip recall NVM into RAM operation
Date: Thu, 4 Feb 2021 19:35:02 -0800	[thread overview]
Message-ID: <1612496104-3437-1-git-send-email-saeed.nowshadi@xilinx.com> (raw)

Silicon Labs' si570 clock driver re-initializes the register space from
non-volatile memory by issuing a 'recall NVM to RAM' operation during
probe(). This operation causes the device to re-calibrate the frequency of
clock out. If the clock is being used while this operation is occurring, a
pause/glitch could be detected on the clock out.  For use cases that the
clock frequency needs to remain consistent from power on, a device tree
optional property is added so the recall operation could be skipped.

Saeed Nowshadi (2):
  dt-bindings: clock: si570: Add 'silabs,skip-recall' property
  clk: si570: Skip NVM to RAM recall operation if an optional property
    is set

 Documentation/devicetree/bindings/clock/silabs,si570.txt |  2 ++
 drivers/clk/clk-si570.c                                  | 16 ++++++++++++----
 2 files changed, 14 insertions(+), 4 deletions(-)

-- 
2.7.4


             reply	other threads:[~2021-02-05  3:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-05  3:35 Saeed Nowshadi [this message]
2021-02-05  3:35 ` [PATCH 1/2] dt-bindings: clock: si570: Add 'silabs,skip-recall' property Saeed Nowshadi
2021-02-11  0:01   ` Rob Herring
2021-02-11 20:16   ` Stephen Boyd
2021-02-05  3:35 ` [PATCH 2/2] clk: si570: Skip NVM to RAM recall operation if an optional property is set Saeed Nowshadi
2021-02-11 20:17   ` 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=1612496104-3437-1-git-send-email-saeed.nowshadi@xilinx.com \
    --to=saeed.nowshadi@xilinx.com \
    --cc=devicetree@vger.kernel.org \
    --cc=git-dev@xilinx.com \
    --cc=linux-clk@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=robh+dt@kernel.org \
    --cc=sboyd@kernel.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).