All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Suman Anna <s-anna@ti.com>
Cc: Tero Kristo <t-kristo@ti.com>, Roger Quadros <rogerq@ti.com>,
	linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/3] Drop PRUSS and OMAP4 IPU/DSP hwmod data
Date: Wed, 26 Feb 2020 17:27:05 -0800	[thread overview]
Message-ID: <20200227012705.GD37466@atomide.com> (raw)
In-Reply-To: <0f47de68-6b89-4219-5ff9-a9c39b6bc759@ti.com>

* Suman Anna <s-anna@ti.com> [200226 20:31]:
> On 2/26/20 12:26 PM, Tony Lindgren wrote:
> > * Suman Anna <s-anna@ti.com> [200224 15:22]:
> >> 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].
> > 
> > Well we still need the hwmod data until dts data is in place to reset
> > and idle these modules. So I'll wait with this set until we have the
> > dts changes in place.
> 
> Not really, you cannot just idle these processors devices by themselves
> without the cores running. The hwmod code actually keeps these in the
> default reset asserted state itself, so no harm done in dropping the
> data. The remoteproc bindings are acked, so for next merge window, we
> can post the dts nodes once those get merged.

OK if they are in reset from the bootloader.. I'll try to check.

Regards,

Tony

WARNING: multiple messages have this Message-ID (diff)
From: Tony Lindgren <tony@atomide.com>
To: Suman Anna <s-anna@ti.com>
Cc: Tero Kristo <t-kristo@ti.com>,
	linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	Roger Quadros <rogerq@ti.com>
Subject: Re: [PATCH 0/3] Drop PRUSS and OMAP4 IPU/DSP hwmod data
Date: Wed, 26 Feb 2020 17:27:05 -0800	[thread overview]
Message-ID: <20200227012705.GD37466@atomide.com> (raw)
In-Reply-To: <0f47de68-6b89-4219-5ff9-a9c39b6bc759@ti.com>

* Suman Anna <s-anna@ti.com> [200226 20:31]:
> On 2/26/20 12:26 PM, Tony Lindgren wrote:
> > * Suman Anna <s-anna@ti.com> [200224 15:22]:
> >> 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].
> > 
> > Well we still need the hwmod data until dts data is in place to reset
> > and idle these modules. So I'll wait with this set until we have the
> > dts changes in place.
> 
> Not really, you cannot just idle these processors devices by themselves
> without the cores running. The hwmod code actually keeps these in the
> default reset asserted state itself, so no harm done in dropping the
> data. The remoteproc bindings are acked, so for next merge window, we
> can post the dts nodes once those get merged.

OK if they are in reset from the bootloader.. I'll try to check.

Regards,

Tony

_______________________________________________
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-27  1:27 UTC|newest]

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