From: Tony Lindgren <tony@atomide.com>
To: linux-omap@vger.kernel.org
Cc: "Benoît Cousson" <bcousson@baylibre.com>,
devicetree@vger.kernel.org,
"Grygorii Strashko" <grygorii.strashko@ti.com>,
"Ivan Khoronzhuk" <ivan.khoronzhuk@linaro.org>,
Keerthy <j-keerthy@ti.com>
Subject: [PATCH 0/3] Drop platform data for cpsw for am3/4 and dra7
Date: Wed, 14 Aug 2019 03:19:46 -0700 [thread overview]
Message-ID: <20190814101949.50006-1-tony@atomide.com> (raw)
Hi all,
Here are changes to drop legacy platform data for cpsw for am3, am4
and dra7. Please review and test, I was not able to boot my beagle
x15 as it seems to have a power supply problem and have only tested
on am3 and 4.
Regards,
Tony
Tony Lindgren (3):
ARM: dts: Add fck for cpsw mdio for omap variants
ARM: OMAP2+: Drop legacy platform data for cpsw on am3 and am4
ARM: OMAP2+: Drop legacy platform data for cpsw on dra7
arch/arm/boot/dts/am33xx-l4.dtsi | 4 +-
arch/arm/boot/dts/am437x-l4.dtsi | 6 +-
arch/arm/boot/dts/dra7-l4.dtsi | 4 +-
.../omap_hwmod_33xx_43xx_common_data.h | 3 -
.../omap_hwmod_33xx_43xx_interconnect_data.c | 6 --
.../omap_hwmod_33xx_43xx_ipblock_data.c | 50 --------------
arch/arm/mach-omap2/omap_hwmod_33xx_data.c | 9 ---
arch/arm/mach-omap2/omap_hwmod_43xx_data.c | 9 ---
arch/arm/mach-omap2/omap_hwmod_7xx_data.c | 65 -------------------
9 files changed, 6 insertions(+), 150 deletions(-)
--
2.21.0
next reply other threads:[~2019-08-14 10:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-14 10:19 Tony Lindgren [this message]
2019-08-14 10:19 ` [PATCH 1/3] ARM: dts: Add fck for cpsw mdio for omap variants Tony Lindgren
2019-08-14 10:19 ` [PATCH 2/3] ARM: OMAP2+: Drop legacy platform data for cpsw on am3 and am4 Tony Lindgren
2019-08-14 10:19 ` [PATCH 3/3] ARM: OMAP2+: Drop legacy platform data for cpsw on dra7 Tony Lindgren
2019-08-15 16:44 ` [PATCH 0/3] Drop platform data for cpsw for am3/4 and dra7 grygorii
2019-08-26 15:19 ` 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=20190814101949.50006-1-tony@atomide.com \
--to=tony@atomide.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=grygorii.strashko@ti.com \
--cc=ivan.khoronzhuk@linaro.org \
--cc=j-keerthy@ti.com \
--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).