devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Keerthy <j-keerthy@ti.com>
To: Tony Lindgren <tony@atomide.com>, <linux-omap@vger.kernel.org>
Cc: "Benoît Cousson" <bcousson@baylibre.com>,
	devicetree@vger.kernel.org,
	"Ankur Tyagi" <ankur.tyagi@gallagher.com>,
	"Suman Anna" <s-anna@ti.com>
Subject: Re: [PATCH 00/21] Drop more legacy platform data for omaps
Date: Fri, 18 Oct 2019 10:24:41 +0530	[thread overview]
Message-ID: <291b705f-cfe7-9d22-16c0-90d269cfa799@ti.com> (raw)
In-Reply-To: <20191017194411.18258-1-tony@atomide.com>



On 18/10/19 1:13 AM, Tony Lindgren wrote:
> Hi all,
> 
> Here's a series of changes to remove more legacy platform data and
> ti,hwmods devitree property for omap variants.
> 
> The patches are against v5.4-rc1, but please note that the watchdog
> changes depend on the following patch:
> 
> [PATCH] bus: ti-sysc: Fix watchdog quirk handling

Tested with the above on AM33/AM43 for DS0. All working fine
however this series needs a re base on top of 5.4-rc3 as the patches are 
not applying cleanly.

Also rc1 does not have the remoteproc config fix patch so i added that 
remoteproc config fix patch on top.

FWIW

Tested-by: Keerthy <j-keerthy@ti.com>

> 
> Regards,
> 
> Tony
> 
> 
> Tony Lindgren (21):
>    ARM: OMAP2+: Drop legacy platform data for am3 and am4 gpio
>    ARM: dts: Drop custom hwmod property for omap4 gpio
>    ARM: dts: Drop custom hwmod property for omap5 gpio
>    ARM: OMAP2+: Drop legacy platform data for dra7 mailbox
>    ARM: OMAP2+: Drop legacy platform data for am3 and am4 mailbox
>    ARM: OMAP2+: Drop legacy platform data for omap4 mailbox
>    ARM: OMAP2+: Drop legacy platform data for omap5 mailbox
>    ARM: dts: Drop custom hwmod property for omap5 mcspi
>    ARM: OMAP2+: Drop legacy platform data for omap5 mcspi
>    ARM: dts: Drop custom hwmod property for am33xx uart
>    ARM: dts: Drop custom hwmod property for am4 uart
>    ARM: dts: Drop custom hwmod property for omap5 uart
>    ARM: dts: Drop custom hwmod property for am3 i2c
>    ARM: dts: Drop custom hwmod property for am4 i2c
>    ARM: dts: Drop custom hwmod property for omap5 i2c
>    ARM: dts: Drop custom hwmod property for am3 mmc
>    ARM: dts: Drop custom hwmod property for am4 mmc
>    ARM: dts: Drop custom hwmod property for omap5 mmc
>    ARM: OMAP2+: Drop legacy platform data for am3 and am4 wdt
>    ARM: OMAP2+: Drop legacy platform data for dra7 wdt
>    ARM: OMAP2+: Drop legacy platform data for omap5 wdt
> 
>   arch/arm/boot/dts/am33xx-l4.dtsi              |  17 -
>   arch/arm/boot/dts/am33xx.dtsi                 |   1 -
>   arch/arm/boot/dts/am4372.dtsi                 |   1 -
>   arch/arm/boot/dts/am437x-l4.dtsi              |  19 -
>   arch/arm/boot/dts/dra7-l4.dtsi                |  14 -
>   arch/arm/boot/dts/omap4-l4.dtsi               |  11 -
>   arch/arm/boot/dts/omap5-l4.dtsi               |  30 --
>   .../omap_hwmod_33xx_43xx_common_data.h        |   3 -
>   .../omap_hwmod_33xx_43xx_interconnect_data.c  |   8 -
>   .../omap_hwmod_33xx_43xx_ipblock_data.c       | 157 --------
>   arch/arm/mach-omap2/omap_hwmod_33xx_data.c    |  11 -
>   arch/arm/mach-omap2/omap_hwmod_43xx_data.c    |   9 -
>   arch/arm/mach-omap2/omap_hwmod_44xx_data.c    |  41 --
>   arch/arm/mach-omap2/omap_hwmod_54xx_data.c    | 204 ----------
>   arch/arm/mach-omap2/omap_hwmod_7xx_data.c     | 352 ------------------
>   15 files changed, 878 deletions(-)
> 

       reply	other threads:[~2019-10-18  4:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20191017194411.18258-1-tony@atomide.com>
2019-10-18  4:54 ` Keerthy [this message]
2019-10-18 15:38   ` [PATCH 00/21] Drop more legacy platform data for omaps 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=291b705f-cfe7-9d22-16c0-90d269cfa799@ti.com \
    --to=j-keerthy@ti.com \
    --cc=ankur.tyagi@gallagher.com \
    --cc=bcousson@baylibre.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=s-anna@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).