From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/8] Add hwmod data for IPU & DSP processors/MMUs
Date: Fri, 22 Sep 2017 10:51:10 -0700 [thread overview]
Message-ID: <20170922175110.GC4394@atomide.com> (raw)
In-Reply-To: <d4715d1e-8113-050b-9a0f-77f4a4486081@ti.com>
* Suman Anna <s-anna@ti.com> [170922 10:19]:
> Ping on this series. Tero's clkctrl series changes are orthogonal to
> these changes.
With patch 5/8 you said earlier "It will still be a shared set
between the MMU and remoteproc drivers, but let me look into
how these get integrated." So was there any conclusion there?
Also, what's the deal with these omap4 changes that I commented
on in 5/8?
Regards,
Tony
next prev parent reply other threads:[~2017-09-22 17:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-21 23:48 [PATCH 0/8] Add hwmod data for IPU & DSP processors/MMUs Suman Anna
2017-08-21 23:48 ` [PATCH 1/8] ARM: DRA7: hwmod data: Add MMU data for IPUs Suman Anna
2017-08-21 23:48 ` [PATCH 2/8] ARM: DRA7: hwmod data: Add MMU data for DSPs Suman Anna
2017-08-21 23:48 ` [PATCH 3/8] ARM: OMAP2+: Extend iommu pdata-quirks to DRA7 IPUs Suman Anna
2017-08-21 23:48 ` [PATCH 4/8] ARM: OMAP2+: Extend iommu pdata-quirks to DRA7 DSPs Suman Anna
2017-08-21 23:48 ` [PATCH 5/8] ARM: OMAP4: hwmod_data: Remove modulemode from IPU/DSP hwmods Suman Anna
2017-08-22 17:37 ` Tony Lindgren
2017-08-22 18:44 ` Suman Anna
2017-08-22 19:24 ` Tony Lindgren
2017-08-22 20:54 ` Suman Anna
2017-08-21 23:48 ` [PATCH 6/8] ARM: OMAP5: hwmod_data: Add data for IPU & DSP processors Suman Anna
2017-10-11 18:41 ` Tony Lindgren
2017-08-21 23:48 ` [PATCH 7/8] ARM: DRA7: hwmod_data: Add data for IPUs Suman Anna
2017-08-21 23:48 ` [PATCH 8/8] ARM: DRA7: hwmod_data: Add data for DSPs Suman Anna
2017-09-22 17:18 ` [PATCH 0/8] Add hwmod data for IPU & DSP processors/MMUs Suman Anna
2017-09-22 17:51 ` Tony Lindgren [this message]
2017-09-22 21:07 ` Suman Anna
2017-09-22 21:19 ` Tony Lindgren
2017-10-12 5:50 ` Tero Kristo
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=20170922175110.GC4394@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).