linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Suman Anna <s-anna@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Tero Kristo <t-kristo@ti.com>,
	linux-omap@vger.kernel.org, Suman Anna <s-anna@ti.com>,
	linux-arm-kernel@lists.infradead.org,
	Roger Quadros <rogerq@ti.com>
Subject: [PATCH 0/3] Drop PRUSS and OMAP4 IPU/DSP hwmod data
Date: Mon, 24 Feb 2020 17:21:49 -0600	[thread overview]
Message-ID: <20200224232152.25562-1-s-anna@ti.com> (raw)

Hi Tony,

The following patches drop the hwmod data for PRUSS on AM33xx and AM437x
SoCs, and for the IPU and DSP processors on OMAP4 SoC. Patches are based
on 5.6-rc1. Please consider these for the 5.7 merge window.

I will be submitting another series tomorrow to add the ti-sysc support
for PRUSS. Nevertheless, the PRUSS hwmods will not be used going forward
and can be dropped independently.

The IPU and DSP hwmods were never added for OMAP5 and DRA7xx/AM57xx SoCs,
and the MMU data was already dropped for 5.6-rc1, as it has all been
converted to ti-sysc and omap-prm. The DT nodes for these will follow
for the next merge window once the current OMAP remoteproc DT support
is accepted [1].

regards
Suman

[1] https://patchwork.kernel.org/cover/11396049/


Suman Anna (3):
  ARM: OMAP2+: Drop hwmod data for am3 and am4 PRUSS
  ARM: OMAP2+: Drop legacy platform data for OMAP4 DSP
  ARM: OMAP4: hwmod_data: Remove OMAP4 IPU hwmod data

 arch/arm/boot/dts/omap4.dtsi                  |   1 -
 .../omap_hwmod_33xx_43xx_common_data.h        |   2 -
 .../omap_hwmod_33xx_43xx_interconnect_data.c  |   8 --
 .../omap_hwmod_33xx_43xx_ipblock_data.c       |  33 -----
 arch/arm/mach-omap2/omap_hwmod_33xx_data.c    |  10 --
 arch/arm/mach-omap2/omap_hwmod_43xx_data.c    |   9 --
 arch/arm/mach-omap2/omap_hwmod_44xx_data.c    | 127 ------------------
 7 files changed, 190 deletions(-)

-- 
2.23.0


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2020-02-24 23:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-24 23:21 Suman Anna [this message]
2020-02-24 23:21 ` [PATCH 1/3] ARM: OMAP2+: Drop hwmod data for am3 and am4 PRUSS Suman Anna
2020-02-24 23:21 ` [PATCH 2/3] ARM: OMAP2+: Drop legacy platform data for OMAP4 DSP Suman Anna
2020-02-24 23:21 ` [PATCH 3/3] ARM: OMAP4: hwmod_data: Remove OMAP4 IPU hwmod data Suman Anna
2020-02-26 18:26 ` [PATCH 0/3] Drop PRUSS and OMAP4 IPU/DSP " Tony Lindgren
2020-02-26 20:30   ` Suman Anna
2020-02-27  1:27     ` Tony Lindgren
2020-02-27 17:40       ` Suman Anna
2020-02-27 18:03         ` 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=20200224232152.25562-1-s-anna@ti.com \
    --to=s-anna@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=rogerq@ti.com \
    --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).