From: Tony Lindgren <tony@atomide.com>
To: Dario Binacchi <dariobin@libero.it>
Cc: linux-kernel@vger.kernel.org, "Lee Jones" <lee.jones@linaro.org>,
"Benoît Cousson" <bcousson@baylibre.com>,
"Rob Herring" <robh@kernel.org>,
"Tero Kristo" <kristo@kernel.org>,
"Michael Turquette" <mturquette@baylibre.com>,
"Stephen Boyd" <sboyd@kernel.org>,
"Rob Herring" <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH v6 4/5] ARM: dts: am43xx-clocks: add spread spectrum support
Date: Fri, 21 May 2021 12:26:50 +0300 [thread overview]
Message-ID: <YKd82iRaWhydlAdx@atomide.com> (raw)
In-Reply-To: <20210520191306.21711-5-dariobin@libero.it>
* Dario Binacchi <dariobin@libero.it> [210520 19:13]:
> Registers for adjusting the spread spectrum clocking (SSC) have been
> added. As reported by the TI spruhl7x RM, SSC is supported only for LCD
> and MPU PLLs, but the PRCM_CM_SSC_DELTAMSTEP_DPLL_XXX and
> PRCM_CM_SSC_MODFREQDIV_DPLL_XXX registers, as well as the enable field
> in the PRCM_CM_CLKMODE_DPLL_XXX registers are mapped for all PLLs (CORE,
> MPU, DDR, PER, DISP, EXTDEV).
This too:
Acked-by: Tony Lindgren <tony@atomide.com>
next prev parent reply other threads:[~2021-05-21 9:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-20 19:13 [PATCH v6 0/5] clk: ti: add am33xx spread spectrum clock support Dario Binacchi
2021-05-20 19:13 ` [PATCH v6 1/5] clk: ti: fix typo in routine description Dario Binacchi
2021-05-20 19:13 ` [PATCH v6 2/5] dt-bindings: ti: dpll: add spread spectrum support Dario Binacchi
2021-05-20 19:13 ` [PATCH v6 3/5] ARM: dts: am33xx-clocks: " Dario Binacchi
2021-05-20 19:13 ` [PATCH v6 4/5] ARM: dts: am43xx-clocks: " Dario Binacchi
2021-05-21 9:26 ` Tony Lindgren [this message]
2021-05-20 19:13 ` [PATCH v6 5/5] clk: ti: add am33xx/am43xx spread spectrum clock support Dario Binacchi
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=YKd82iRaWhydlAdx@atomide.com \
--to=tony@atomide.com \
--cc=bcousson@baylibre.com \
--cc=dariobin@libero.it \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=robh@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 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.