From: Tony Lindgren <tony@atomide.com>
To: linux-omap@vger.kernel.org
Cc: "Benoît Cousson" <bcousson@baylibre.com>, devicetree@vger.kernel.org
Subject: [PATCH 00/10] Drop even more legacy platform data for omaps
Date: Fri, 18 Oct 2019 09:32:10 -0700 [thread overview]
Message-ID: <20191018163220.3504-1-tony@atomide.com> (raw)
Hi all,
This series of changes remove even more legacy platform data and
ti,hwmods devitree property for omap variants.
The patches are against v5.4-rc1 on top of the previous set:
[PATCH 00/21] Drop more legacy platform data for omaps
Please note that the earlier watchdog changes depend on the following
patch:
[PATCH] bus: ti-sysc: Fix watchdog quirk handling
Regards,
Tony
Tony Lindgren (10):
ARM: OMAP2+: Drop legacy platform data for omap4 mcbsp
ARM: OMAP2+: Drop legacy platform data for omap5 mcbsp
ARM: OMAP2+: Drop legacy platform data for am4 hdq1w
ARM: OMAP2+: Drop legacy platform data for dra7 hdq1w
ARM: OMAP2+: Drop legacy platform data for omap4 hdq1w
ARM: OMAP2+: Drop legacy platform data for am3 and am4 rng
ARM: OMAP2+: Drop legacy platform data for dra7 rng
ARM: OMAP2+: Drop legacy platform data for am3 and am4 mcasp
ARM: OMAP2+: Drop legacy platform data for omap4 mcasp
ARM: OMAP2+: Drop legacy platform data for musb on omap4
arch/arm/boot/dts/am33xx-l4.dtsi | 3 -
arch/arm/boot/dts/am437x-l4.dtsi | 4 -
arch/arm/boot/dts/dra7-l4.dtsi | 2 -
arch/arm/boot/dts/omap4-l4-abe.dtsi | 4 -
arch/arm/boot/dts/omap4-l4.dtsi | 3 -
arch/arm/boot/dts/omap5-l4-abe.dtsi | 3 -
.../omap_hwmod_33xx_43xx_common_data.h | 4 -
.../omap_hwmod_33xx_43xx_interconnect_data.c | 10 -
.../omap_hwmod_33xx_43xx_ipblock_data.c | 74 -----
arch/arm/mach-omap2/omap_hwmod_33xx_data.c | 1 -
arch/arm/mach-omap2/omap_hwmod_43xx_data.c | 37 ---
arch/arm/mach-omap2/omap_hwmod_44xx_data.c | 302 ------------------
arch/arm/mach-omap2/omap_hwmod_54xx_data.c | 113 -------
arch/arm/mach-omap2/omap_hwmod_7xx_data.c | 79 -----
14 files changed, 639 deletions(-)
--
2.23.0
next reply other threads:[~2019-10-18 16:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-18 16:32 Tony Lindgren [this message]
2019-10-18 16:32 ` [PATCH 01/10] ARM: OMAP2+: Drop legacy platform data for omap4 mcbsp Tony Lindgren
2019-10-18 16:32 ` [PATCH 02/10] ARM: OMAP2+: Drop legacy platform data for omap5 mcbsp Tony Lindgren
2019-10-18 16:32 ` [PATCH 03/10] ARM: OMAP2+: Drop legacy platform data for am4 hdq1w Tony Lindgren
2019-10-18 16:32 ` [PATCH 04/10] ARM: OMAP2+: Drop legacy platform data for dra7 hdq1w Tony Lindgren
2019-10-18 16:32 ` [PATCH 05/10] ARM: OMAP2+: Drop legacy platform data for omap4 hdq1w Tony Lindgren
2019-10-18 16:32 ` [PATCH 06/10] ARM: OMAP2+: Drop legacy platform data for am3 and am4 rng Tony Lindgren
2019-10-18 16:32 ` [PATCH 07/10] ARM: OMAP2+: Drop legacy platform data for dra7 rng Tony Lindgren
2019-10-23 15:20 ` Tony Lindgren
2019-10-18 16:32 ` [PATCH 08/10] ARM: OMAP2+: Drop legacy platform data for am3 and am4 mcasp Tony Lindgren
2019-10-21 20:34 ` Tony Lindgren
2019-10-18 16:32 ` [PATCH 09/10] ARM: OMAP2+: Drop legacy platform data for omap4 mcasp Tony Lindgren
2019-10-18 16:32 ` [PATCH 10/10] ARM: OMAP2+: Drop legacy platform data for musb on omap4 Tony Lindgren
2019-10-21 20:45 ` 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=20191018163220.3504-1-tony@atomide.com \
--to=tony@atomide.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-omap@vger.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).