All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Tony Lindgren <tony@atomide.com>
Cc: SoC Team <soc@kernel.org>, arm-soc <arm@kernel.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	linux-omap <linux-omap@vger.kernel.org>
Subject: Re: [GIT PULL 3/4] drop more legacy pdata for omaps for v5.4
Date: Wed, 4 Sep 2019 17:27:15 +0200	[thread overview]
Message-ID: <CAK8P3a1C_OEPwrf-vdEmns5f87GN6dtsoda_WVmZAxEvLfFiDw@mail.gmail.com> (raw)
In-Reply-To: <pull-1567016893-318461@atomide.com-3>

On Wed, Aug 28, 2019 at 8:35 PM Tony Lindgren <tony@atomide.com> wrote:
> Drop legacy platform data omap variants for v5.4
>
> We can now drop more platform data in favor of dts data for most
> devices like cpsw, gpio, i2c, mmc, uart and watchdog.
>
> In general we can do this by dropping legacy "ti,hwmods" custom dts
> property, and the platform data assuming the related dts data is correct.
> This is best done as single patch as otherwise we'd have to revert two
> patches in case of any unexpected issues, and we're just removing data.
>
> Fro cpsw, before we can do this, we need to configure the cpsw mdio clocks
> properly in dts though in the first patch. For omap4 i2c, we've already
> dropped the platform data earlier, but have been still allocting it
> dynamically based on the dts data based on the "ti,hwmods" property, but
> that is no longer needed. For d2d, we are missing the dts data, so we
> first add it and then drop the platform data.
>
> For dra7, we drop platform data and "ti,hwmods" for mcasp and mcspi.
> We've already dropped platform data earlier for gpio, i2c, mmc, and
> uart so we just need to drop "ti,hwmods" property for those.
>
> Note that this branch is based on earlier ti-sysc-fixes branch.

Pulled into arm/late, thanks!

     Arnd

WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: Tony Lindgren <tony@atomide.com>
Cc: SoC Team <soc@kernel.org>, arm-soc <arm@kernel.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	linux-omap <linux-omap@vger.kernel.org>
Subject: Re: [GIT PULL 3/4] drop more legacy pdata for omaps for v5.4
Date: Wed, 4 Sep 2019 17:27:15 +0200	[thread overview]
Message-ID: <CAK8P3a1C_OEPwrf-vdEmns5f87GN6dtsoda_WVmZAxEvLfFiDw@mail.gmail.com> (raw)
In-Reply-To: <pull-1567016893-318461@atomide.com-3>

On Wed, Aug 28, 2019 at 8:35 PM Tony Lindgren <tony@atomide.com> wrote:
> Drop legacy platform data omap variants for v5.4
>
> We can now drop more platform data in favor of dts data for most
> devices like cpsw, gpio, i2c, mmc, uart and watchdog.
>
> In general we can do this by dropping legacy "ti,hwmods" custom dts
> property, and the platform data assuming the related dts data is correct.
> This is best done as single patch as otherwise we'd have to revert two
> patches in case of any unexpected issues, and we're just removing data.
>
> Fro cpsw, before we can do this, we need to configure the cpsw mdio clocks
> properly in dts though in the first patch. For omap4 i2c, we've already
> dropped the platform data earlier, but have been still allocting it
> dynamically based on the dts data based on the "ti,hwmods" property, but
> that is no longer needed. For d2d, we are missing the dts data, so we
> first add it and then drop the platform data.
>
> For dra7, we drop platform data and "ti,hwmods" for mcasp and mcspi.
> We've already dropped platform data earlier for gpio, i2c, mmc, and
> uart so we just need to drop "ti,hwmods" property for those.
>
> Note that this branch is based on earlier ti-sysc-fixes branch.

Pulled into arm/late, thanks!

     Arnd

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

  reply	other threads:[~2019-09-04 15:27 UTC|newest]

Thread overview: 16+ 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 ` Tony Lindgren
2019-08-28 18:34 ` [GIT PULL 2/4] more ti-sysc driver changes " Tony Lindgren
2019-08-28 18:34   ` Tony Lindgren
2019-09-04 15:26   ` Arnd Bergmann
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-08-28 18:34   ` Tony Lindgren
2019-09-04 15:27   ` Arnd Bergmann [this message]
2019-09-04 15:27     ` Arnd Bergmann
2019-08-28 18:34 ` [GIT PULL 4/4] sgx soc glue changes " Tony Lindgren
2019-08-28 18:34   ` Tony Lindgren
2019-09-04 15:27   ` Arnd Bergmann
2019-09-04 15:27     ` Arnd Bergmann
2019-09-03 12:25 ` [GIT PULL 1/4] soc changes for omap variants " Arnd Bergmann
2019-09-03 12:25   ` 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=CAK8P3a1C_OEPwrf-vdEmns5f87GN6dtsoda_WVmZAxEvLfFiDw@mail.gmail.com \
    --to=arnd@arndb.de \
    --cc=arm@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=soc@kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.