From: Tero Kristo <t-kristo@ti.com>
To: bjorn.andersson@linaro.org, ohad@wizery.com,
linux-remoteproc@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, mathieu.poirier@linaro.org,
s-anna@ti.com, linux-omap@vger.kernel.org
Subject: [PATCHv5 00/14] remoteproc: updates for omap remoteproc support
Date: Thu, 16 Jan 2020 15:53:18 +0200 [thread overview]
Message-ID: <20200116135332.7819-1-t-kristo@ti.com> (raw)
Hi,
This version addresses review comments received for v4 of the series.
Mostly cosmetic changes, the most important changes here:
- minor dt binding updates and any driver changes induced by this
- reset handling fixes to avoid asserting/deasserting same reset twice,
this appeared to still produce some timeouts in some cases; this was
masked earlier but became visible with one error handling fix
All changes are listed under individual patches.
-Tero
--
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
next reply other threads:[~2020-01-16 13:53 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-16 13:53 Tero Kristo [this message]
[not found] ` <20200116135332.7819-1-t-kristo-l0cyMroinI0@public.gmane.org>
2020-01-16 13:53 ` [PATCHv5 01/14] dt-bindings: remoteproc: Add OMAP remoteproc bindings Tero Kristo
[not found] ` <20200116135332.7819-2-t-kristo-l0cyMroinI0@public.gmane.org>
2020-01-22 2:34 ` Rob Herring
2020-01-16 13:53 ` [PATCHv5 02/14] remoteproc/omap: Add device tree support Tero Kristo
2020-01-16 13:53 ` [PATCHv5 03/14] remoteproc/omap: Add a sanity check for DSP boot address alignment Tero Kristo
2020-01-16 13:53 ` [PATCHv5 04/14] remoteproc/omap: Add support to parse internal memories from DT Tero Kristo
2020-01-16 13:53 ` [PATCHv5 05/14] remoteproc/omap: Add the rproc ops .da_to_va() implementation Tero Kristo
2020-01-16 13:53 ` [PATCHv5 06/14] remoteproc/omap: Initialize and assign reserved memory node Tero Kristo
2020-01-30 18:11 ` Andrew F. Davis
2020-01-30 19:18 ` Tero Kristo
2020-01-30 19:20 ` Andrew F. Davis
2020-01-30 19:42 ` Tero Kristo
2020-01-30 19:55 ` Suman Anna
2020-01-30 20:22 ` Andrew F. Davis
2020-01-30 20:39 ` Suman Anna
2020-01-30 21:19 ` Andrew F. Davis
2020-01-30 21:39 ` Suman Anna
2020-01-30 21:50 ` Andrew F. Davis
2020-01-30 21:57 ` Suman Anna
2020-01-30 22:06 ` Suman Anna
2020-01-30 23:04 ` Andrew F. Davis
2020-02-05 8:51 ` Tero Kristo
2020-01-16 13:53 ` [PATCHv5 07/14] remoteproc/omap: Add support for DRA7xx remote processors Tero Kristo
2020-01-16 13:53 ` [PATCHv5 08/14] remoteproc/omap: remove the platform_data header Tero Kristo
2020-01-16 13:53 ` [PATCHv5 09/14] remoteproc/omap: Check for undefined mailbox messages Tero Kristo
2020-01-16 13:53 ` [PATCHv5 10/14] remoteproc/omap: Request a timer(s) for remoteproc usage Tero Kristo
2020-01-16 13:53 ` [PATCHv5 11/14] remoteproc/omap: add support for system suspend/resume Tero Kristo
2020-01-16 13:53 ` [PATCHv5 12/14] remoteproc/omap: add support for runtime auto-suspend/resume Tero Kristo
2020-01-16 13:53 ` [PATCHv5 13/14] remoteproc/omap: report device exceptions and trigger recovery Tero Kristo
2020-01-16 13:53 ` [PATCHv5 14/14] remoteproc/omap: add watchdog functionality for remote processors 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=20200116135332.7819-1-t-kristo@ti.com \
--to=t-kristo@ti.com \
--cc=bjorn.andersson@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=ohad@wizery.com \
--cc=s-anna@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox