From: Tony Lindgren <tony@atomide.com>
To: soc@kernel.org
Cc: Tony Lindgren <tony@atomide.com>,
linux-omap@vger.kernel.org, arm@kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 4/4] sgx soc glue changes for omaps for v5.4
Date: Wed, 28 Aug 2019 11:34:52 -0700 [thread overview]
Message-ID: <pull-1567016893-318461@atomide.com-4> (raw)
In-Reply-To: <pull-1567016893-318461@atomide.com>
From: "Tony Lindgren" <tony@atomide.com>
The following changes since commit 7edd00f71f4b91ca31dbfa08926495fe5e77aab4:
bus: ti-sysc: Detect d2d when debug is enabled (2019-08-26 08:33:25 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v5.4/ti-sysc-sgx-signed
for you to fetch changes up to 6cb0ac0fb9786d01f140dcfcd3d09ce850dd0a64:
ARM: dts: ARM: dts: Configure interconnect target module for am3517sgx (2019-08-26 08:47:09 -0700)
----------------------------------------------------------------
SoC glue layer changes for SGX on omap variants for v5.4
For a while we've had omap4 sgx glue layer defined in dts and probed
with ti-sysc driver. This allows idling the sgx module for PM, and
removes the need for custom platform glue layer code for any further
driver changes.
We first drop the unused legacy platform data for omap4 sgx. Then for
omap5, we need add the missing clkctrl clock data so we can configure
sgx. And we configure sgx for omap34xx, omap36xx and am3517.
For am335x, we still have a dependency for rstctrl reset driver changes,
so that will be added later on.
Note that this branch is based on earlier ti-sysc branch for omap36xx
glue layer quirk handling.
----------------------------------------------------------------
Adam Ford (1):
ARM: dts: ARM: dts: Configure interconnect target module for am3517sgx
Tony Lindgren (4):
ARM: OMAP2+: Drop legacy platform data for omap4 gpu
clk: ti: add clkctrl data omap5 sgx
ARM: dts: Configure sgx for omap5
ARM: dts: Configure interconnect target module for omap3 sgx
arch/arm/boot/dts/am3517.dtsi | 24 ++++++++++++++
arch/arm/boot/dts/omap34xx.dtsi | 26 +++++++++++++++
arch/arm/boot/dts/omap36xx.dtsi | 28 ++++++++++++++++
arch/arm/boot/dts/omap4.dtsi | 1 -
arch/arm/boot/dts/omap5.dtsi | 23 +++++++++++++
arch/arm/boot/dts/omap54xx-clocks.dtsi | 14 ++++++++
arch/arm/mach-omap2/omap_hwmod_44xx_data.c | 53 ------------------------------
drivers/clk/ti/clk-54xx.c | 34 +++++++++++++++++++
include/dt-bindings/clock/omap5.h | 3 ++
9 files changed, 152 insertions(+), 54 deletions(-)
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-08-28 18:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-28 18:34 [GIT PULL 1/4] soc changes for omap variants for v5.4 Tony Lindgren
2019-08-28 18:34 ` [GIT PULL 2/4] more ti-sysc driver changes " Tony Lindgren
2019-09-04 15:26 ` Arnd Bergmann
2019-08-28 18:34 ` [GIT PULL 3/4] drop more legacy pdata for omaps " Tony Lindgren
2019-09-04 15:27 ` Arnd Bergmann
2019-08-28 18:34 ` Tony Lindgren [this message]
2019-09-04 15:27 ` [GIT PULL 4/4] sgx soc glue changes " Arnd Bergmann
2019-09-03 12:25 ` [GIT PULL 1/4] soc changes for omap variants " Arnd Bergmann
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=pull-1567016893-318461@atomide.com-4 \
--to=tony@atomide.com \
--cc=arm@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=soc@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).