From: Stephen Boyd <sboyd@kernel.org>
To: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@codeaurora.org>,
Tero Kristo <t-kristo@ti.com>, Tony Lindgren <tony@atomide.com>
Cc: devicetree@vger.kernel.org, linux-clk@vger.kernel.org,
linux-omap@vger.kernel.org, Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH 2/5] ARM: dts: Add missing omap4 secure clocks
Date: Mon, 30 Dec 2019 12:00:31 -0800 [thread overview]
Message-ID: <20191230200032.22EA120718@mail.kernel.org> (raw)
In-Reply-To: <20191210172108.38868-3-tony@atomide.com>
Quoting Tony Lindgren (2019-12-10 09:21:05)
> The secure clocks on omap4 are similar to what we already have for dra7
> in dra7_l4sec_clkctrl_regs and documented in the omap4460 TRM "Table
> 3-1346 L4PER_CM2 Registers Mapping Summary".
>
> The secure clocks are part of the l4_per clock manager. As the l4_per
> clock manager has now two clock domains as children, let's also update
> the l4_per clockdomain node name to follow the "clock" node naming with
> a domain specific compatible property.
>
> Cc: devicetree@vger.kernel.org
> Cc: Rob Herring <robh+dt@kernel.org>
> Signed-off-by: Tony Lindgren <tony@atomide.com>
> ---
Acked-by: Stephen Boyd <sboyd@kernel.org>
next prev parent reply other threads:[~2019-12-30 20:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-10 17:21 [PATCH 0/5] Clock changes needed to probe rng on omap4 and 5 Tony Lindgren
2019-12-10 17:21 ` [PATCH 1/5] clk: ti: clkctrl: Fix hidden dependency to node name Tony Lindgren
2019-12-19 20:18 ` Rob Herring
2019-12-30 20:00 ` Stephen Boyd
2019-12-10 17:21 ` [PATCH 2/5] ARM: dts: Add missing omap4 secure clocks Tony Lindgren
2019-12-30 20:00 ` Stephen Boyd [this message]
2019-12-10 17:21 ` [PATCH 3/5] ARM: dts: Add missing omap5 " Tony Lindgren
2019-12-30 20:00 ` Stephen Boyd
2019-12-10 17:21 ` [PATCH 4/5] ARM: dts: Configure omap4 rng to probe with ti-sysc Tony Lindgren
2019-12-10 17:21 ` [PATCH 5/5] ARM: dts: Configure omap5 " Tony Lindgren
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=20191230200032.22EA120718@mail.kernel.org \
--to=sboyd@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@codeaurora.org \
--cc=t-kristo@ti.com \
--cc=tony@atomide.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 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).