All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Tero Kristo <t-kristo@ti.com>
Cc: linux-omap@vger.kernel.org, s-anna@ti.com,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 00/17] ARM: dts: dra7/am57xx: remoteproc support
Date: Tue, 5 May 2020 11:14:28 -0700	[thread overview]
Message-ID: <20200505181428.GO37466@atomide.com> (raw)
In-Reply-To: <5f8d4dbb-f4fc-ee97-8542-610e98d3f895@ti.com>

* Tero Kristo <t-kristo@ti.com> [200424 15:55]:
> On 24/04/2020 18:51, Tony Lindgren wrote:
> > * Tero Kristo <t-kristo@ti.com> [200424 08:13]:
> > > Hi Tony,
> > > 
> > > This series adds the DT nodes necessary for remoteproc support, now that
> > > the driver side changes are (mostly) in. Couple of things to note
> > > though.
> > > 
> > > 1) There is a new IOMMU issue, for which I posted a fix today [1]
> > > 2) The remoteproc core still has an issue for which there is ongoing
> > >     discussion [2]
> > > 
> > > With these two issue taken care of, the omap remoteproc support is
> > > functional. The question though is, whether we should just wait until
> > > the above two issues are resolved and merge the DT patches post that, or
> > > merge the DT patches with status = "disabled".
> > 
> > If there are no dependencies between the pending driver fixes and
> > the dts changes I see no reason to not merge the dts changes.
> 
> Yeah, no hard dependencies as such, just that things won't work properly
> before they are in.

Applying these all into omap-for-v5.8/dt thanks.

Tony

WARNING: multiple messages have this Message-ID (diff)
From: Tony Lindgren <tony@atomide.com>
To: Tero Kristo <t-kristo@ti.com>
Cc: s-anna@ti.com, linux-omap@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 00/17] ARM: dts: dra7/am57xx: remoteproc support
Date: Tue, 5 May 2020 11:14:28 -0700	[thread overview]
Message-ID: <20200505181428.GO37466@atomide.com> (raw)
In-Reply-To: <5f8d4dbb-f4fc-ee97-8542-610e98d3f895@ti.com>

* Tero Kristo <t-kristo@ti.com> [200424 15:55]:
> On 24/04/2020 18:51, Tony Lindgren wrote:
> > * Tero Kristo <t-kristo@ti.com> [200424 08:13]:
> > > Hi Tony,
> > > 
> > > This series adds the DT nodes necessary for remoteproc support, now that
> > > the driver side changes are (mostly) in. Couple of things to note
> > > though.
> > > 
> > > 1) There is a new IOMMU issue, for which I posted a fix today [1]
> > > 2) The remoteproc core still has an issue for which there is ongoing
> > >     discussion [2]
> > > 
> > > With these two issue taken care of, the omap remoteproc support is
> > > functional. The question though is, whether we should just wait until
> > > the above two issues are resolved and merge the DT patches post that, or
> > > merge the DT patches with status = "disabled".
> > 
> > If there are no dependencies between the pending driver fixes and
> > the dts changes I see no reason to not merge the dts changes.
> 
> Yeah, no hard dependencies as such, just that things won't work properly
> before they are in.

Applying these all into omap-for-v5.8/dt thanks.

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-05-05 18:14 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-24 15:12 [PATCH 00/17] ARM: dts: dra7/am57xx: remoteproc support Tero Kristo
2020-04-24 15:12 ` Tero Kristo
2020-04-24 15:12 ` [PATCH 01/17] ARM: dts: dra7: add timer_sys_ck entries for IPU/DSP timers Tero Kristo
2020-04-24 15:12   ` Tero Kristo
2020-04-24 15:12 ` [PATCH 02/17] ARM: dts: DRA7: Add common IPU and DSP nodes Tero Kristo
2020-04-24 15:12   ` Tero Kristo
2020-04-24 15:12 ` [PATCH 03/17] ARM: dts: DRA74x: Add DSP2 processor device node Tero Kristo
2020-04-24 15:12   ` Tero Kristo
2020-04-24 15:12 ` [PATCH 04/17] ARM: dts: DRA74x: Add aliases for rproc nodes Tero Kristo
2020-04-24 15:12   ` Tero Kristo
2020-04-24 15:12 ` [PATCH 05/17] ARM: dts: DRA72x: " Tero Kristo
2020-04-24 15:12   ` Tero Kristo
2020-04-24 15:12 ` [PATCH 06/17] ARM: dts: dra7-ipu-dsp-common: Move mailboxes into common files Tero Kristo
2020-04-24 15:12   ` Tero Kristo
2020-04-24 15:12 ` [PATCH 07/17] ARM: dts: dra7-ipu-dsp-common: Add mailboxes to IPU and DSP nodes Tero Kristo
2020-04-24 15:12   ` Tero Kristo
2020-04-24 15:12 ` [PATCH 08/17] ARM: dts: dra7-ipu-dsp-common: Add timers " Tero Kristo
2020-04-24 15:12   ` Tero Kristo
2020-04-24 15:12 ` [PATCH 09/17] ARM: dts: dra7-evm: Add CMA pools and enable IPU & DSP rprocs Tero Kristo
2020-04-24 15:12   ` Tero Kristo
2020-04-24 15:12 ` [PATCH 10/17] ARM: dts: dra72-evm: Add CMA pools and enable IPUs & DSP1 rprocs Tero Kristo
2020-04-24 15:12   ` Tero Kristo
2020-04-24 15:12 ` [PATCH 11/17] ARM: dts: dra72-evm-revc: " Tero Kristo
2020-04-24 15:12   ` Tero Kristo
2020-04-24 15:12 ` [PATCH 12/17] ARM: dts: dra71-evm: " Tero Kristo
2020-04-24 15:12   ` Tero Kristo
2020-04-24 15:12 ` [PATCH 13/17] ARM: dts: dra76-evm: Add CMA pools and enable IPU & DSP rprocs Tero Kristo
2020-04-24 15:12   ` Tero Kristo
2020-04-24 15:12 ` [PATCH 14/17] ARM: dts: beagle-x15-common: " Tero Kristo
2020-04-24 15:12   ` Tero Kristo
2020-04-24 15:12 ` [PATCH 15/17] ARM: dts: am572x-idk-common: " Tero Kristo
2020-04-24 15:12   ` Tero Kristo
2020-04-24 15:12 ` [PATCH 16/17] ARM: dts: am571x-idk: Add CMA pools and enable IPUs & DSP1 rprocs Tero Kristo
2020-04-24 15:12   ` Tero Kristo
2020-04-24 15:12 ` [PATCH 17/17] ARM: dts: dra7-ipu-dsp-common: Add watchdog timers to IPU and DSP nodes Tero Kristo
2020-04-24 15:12   ` Tero Kristo
2020-04-24 15:51 ` [PATCH 00/17] ARM: dts: dra7/am57xx: remoteproc support Tony Lindgren
2020-04-24 15:51   ` Tony Lindgren
2020-04-24 15:54   ` Tero Kristo
2020-04-24 15:54     ` Tero Kristo
2020-05-05 18:14     ` Tony Lindgren [this message]
2020-05-05 18:14       ` 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=20200505181428.GO37466@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --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.