From: robh@kernel.org (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/5] dt-bindings: clock: ti: add latching support to mux and divider clocks
Date: Mon, 19 Feb 2018 08:36:20 -0600 [thread overview]
Message-ID: <20180219143620.vu3ucann7vmgsdlt@rob-hp-laptop> (raw)
In-Reply-To: <1518698991-10099-2-git-send-email-t-kristo@ti.com>
On Thu, Feb 15, 2018 at 02:49:47PM +0200, Tero Kristo wrote:
> Certain hardware configurations, like dra76x, have some of the clock
> registers partitioned in a funky manner that requires the clock
> control setup to be latched for PRCM to be notified of the change. This
> is accomplished with a separate control bit under the register. Add
> support for this clock latching support to divider and mux clocks.
>
> Signed-off-by: Tero Kristo <t-kristo@ti.com>
> ---
> Documentation/devicetree/bindings/clock/ti/divider.txt | 3 +++
> Documentation/devicetree/bindings/clock/ti/mux.txt | 3 +++
> 2 files changed, 6 insertions(+)
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2018-02-19 14:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-15 12:49 [PATCH 0/5] clk: ti: add support for dra76x latched clocks Tero Kristo
2018-02-15 12:49 ` [PATCH 1/5] dt-bindings: clock: ti: add latching support to mux and divider clocks Tero Kristo
2018-02-19 14:36 ` Rob Herring [this message]
2018-02-15 12:49 ` [PATCH 2/5] clk: ti: add support for register read-modify-write low-level operation Tero Kristo
2018-02-15 12:49 ` [PATCH 3/5] clk: ti: add generic support for clock latching Tero Kristo
2018-02-15 12:49 ` [PATCH 4/5] clk: ti: add support for clock latching to divider clocks Tero Kristo
2018-02-15 12:49 ` [PATCH 5/5] clk: ti: add support for clock latching to mux clocks Tero Kristo
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=20180219143620.vu3ucann7vmgsdlt@rob-hp-laptop \
--to=robh@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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