From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Suman Anna <s-anna@ti.com>
Cc: linux-remoteproc@vger.kernel.org, Sekhar Nori <nsekhar@ti.com>,
Robert Tivy <rtivy@ti.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] Davinci remoteproc cleanups/fixes
Date: Sun, 25 Jun 2017 14:19:55 -0700 [thread overview]
Message-ID: <20170625211955.GD26155@builder> (raw)
In-Reply-To: <20170518220902.2846-1-s-anna@ti.com>
On Thu 18 May 15:08 PDT 2017, Suman Anna wrote:
> Hi Bjorn,
>
> The following series includes various fixes and cleanups for the TI's
> Davinci DSP remoteproc driver. Patches are based on 4.12-rc1. Following
> is the patch summary:
>
> - Patch1 updates/fixes the build dependency on DMA_CMA which is not
> selected by default in the davinci_defconfig.
> - Patch 3 fixes a DSP boot/functionality issue with repeated 'start'
> and 'stop' commands using the sysfs 'state' variable.
> - Patch 2 and 4 are cleanups/code simplifications.
>
Patches 1, 2 and 3 applied to rproc-next.
Regards,
Bjorn
prev parent reply other threads:[~2017-06-25 21:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-18 22:08 [PATCH 0/4] Davinci remoteproc cleanups/fixes Suman Anna
2017-05-18 22:08 ` [PATCH 1/4] remoteproc/davinci: Update Kconfig to depend on DMA_CMA Suman Anna
2017-05-18 22:09 ` [PATCH 2/4] remoteproc/davinci: simplify the reset function Suman Anna
2017-05-18 22:09 ` [PATCH 3/4] remoteproc/davinci: fix unbalanced reset between start and stop ops Suman Anna
2017-05-18 22:09 ` [PATCH 4/4] remoteproc/davinci: streamline the interrupt management Suman Anna
2017-06-25 21:19 ` Bjorn Andersson
2017-06-26 16:09 ` Suman Anna
2017-06-27 5:38 ` Bjorn Andersson
2017-06-27 19:14 ` Suman Anna
2017-06-08 20:47 ` [PATCH 0/4] Davinci remoteproc cleanups/fixes Suman Anna
2017-06-23 21:29 ` Suman Anna
2017-06-25 21:19 ` Bjorn Andersson [this message]
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=20170625211955.GD26155@builder \
--to=bjorn.andersson@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=rtivy@ti.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;
as well as URLs for NNTP newsgroup(s).