From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Ohad Ben-Cohen <ohad@wizery.com>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Sekhar Nori <nsekhar@ti.com>,
David Lechner <david@lechnology.com>, Suman Anna <s-anna@ti.com>,
Aparna Balasubramanian <aparnab@ti.com>,
Kevin Hilman <khilman@kernel.org>
Cc: linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org,
Bartosz Golaszewski <bgolaszewski@baylibre.com>
Subject: [PATCH 0/3] remoteproc/davinci: common clock framework related fixes
Date: Wed, 2 May 2018 11:56:56 +0200 [thread overview]
Message-ID: <20180502095659.3626-1-brgl@bgdev.pl> (raw)
From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
Hi Bjorn,
this series contains the patches from my previous remoteproc series[1]
which are safe to apply on top of 4.17-rc1. They contain fixes needed
for the driver to work once we're done converting to using the CCF for
DaVinci.
The last remoteproc patch will be sent later once the platform parts
are applied.
All the patches are reviewed and tested.
[1] https://lkml.org/lkml/2018/4/17/1000
Bartosz Golaszewski (3):
remoteproc/davinci: add the missing retval check for clk_enable()
remoteproc/davinci: prepare and unprepare the clock where needed
remoteproc/davinci: use octal permissions for module_param()
drivers/remoteproc/da8xx_remoteproc.c | 12 +++++++++---
1 file changed, 9 insertions(+), 3 deletions(-)
--
2.17.0
next reply other threads:[~2018-05-02 9:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-02 9:56 Bartosz Golaszewski [this message]
2018-05-02 9:56 ` [PATCH 1/3] remoteproc/davinci: add the missing retval check for clk_enable() Bartosz Golaszewski
2018-05-09 21:31 ` Bjorn Andersson
2018-05-02 9:56 ` [PATCH 2/3] remoteproc/davinci: prepare and unprepare the clock where needed Bartosz Golaszewski
2018-05-02 9:56 ` [PATCH 3/3] remoteproc/davinci: use octal permissions for module_param() Bartosz Golaszewski
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=20180502095659.3626-1-brgl@bgdev.pl \
--to=brgl@bgdev.pl \
--cc=aparnab@ti.com \
--cc=bgolaszewski@baylibre.com \
--cc=bjorn.andersson@linaro.org \
--cc=david@lechnology.com \
--cc=khilman@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=nsekhar@ti.com \
--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