From: Dave Gerlach <d-gerlach@ti.com>
To: <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <linux-omap@vger.kernel.org>,
<devicetree@vger.kernel.org>
Cc: Ohad Ben-Cohen <ohad@wizery.com>, Suman Anna <s-anna@ti.com>,
Tony Lindgren <tony@atomide.com>, Dave Gerlach <d-gerlach@ti.com>
Subject: [PATCH v4 0/4] remoteproc: Introduce wkup_m3_rproc driver
Date: Fri, 22 May 2015 15:45:26 -0500 [thread overview]
Message-ID: <1432327530-48032-1-git-send-email-d-gerlach@ti.com> (raw)
Hi,
This patch series is v4 of the series to add a wkup_m3_rproc driver
for TI AM335xi and AM437x SoCs. This family of SoCs contains an ARM
Cortex M3 coprocessor that is responsible for low-level power tasks
that cannot be handled by the main ARM Cortex A8 so firmware running
from the CM3 can be used instead. This driver handles loading
of the firmware and reset of the CM3. Change info can be found
with each patch.
The previous version of this series can be found here [1].
I have pushed a branch based on v4.1-rc4 containing the entire
am335x suspend series along with WIP am437x suspend patches for
a higher level view of the entire series of patch sets here [2].
The driver expects to load firmware am335x-pm-firmware.elf from
/lib/firmware which is found here [3].
Regards,
Dave
[1] http://www.spinics.net/lists/linux-omap/msg117611.html
[2] https://github.com/dgerlach/linux-pm/tree/pm-v4.1-rc4-amx3-suspend
[3] https://git.ti.com/ti-cm3-pm-firmware/amx3-cm3/commits/next-upstream
Dave Gerlach (3):
remoteproc: introduce rproc_get_by_phandle API
Documentation: dt: add bindings for TI Wakeup M3 processor
remoteproc/wkup_m3: add a remoteproc driver for TI Wakeup M3
Suman Anna (1):
remoteproc: add a rproc ops for performing address translation
.../bindings/remoteproc/wkup_m3_rproc.txt | 52 +++++
Documentation/remoteproc.txt | 6 +
drivers/remoteproc/Kconfig | 13 ++
drivers/remoteproc/Makefile | 1 +
drivers/remoteproc/remoteproc_core.c | 81 ++++++-
drivers/remoteproc/wkup_m3_rproc.c | 257 +++++++++++++++++++++
include/linux/platform_data/wkup_m3.h | 30 +++
include/linux/remoteproc.h | 9 +-
8 files changed, 440 insertions(+), 9 deletions(-)
create mode 100644 Documentation/devicetree/bindings/remoteproc/wkup_m3_rproc.txt
create mode 100644 drivers/remoteproc/wkup_m3_rproc.c
create mode 100644 include/linux/platform_data/wkup_m3.h
--
2.4.1
next reply other threads:[~2015-05-22 20:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-22 20:45 Dave Gerlach [this message]
2015-05-22 20:45 ` [PATCH v4 1/4] remoteproc: introduce rproc_get_by_phandle API Dave Gerlach
2015-06-17 18:46 ` [PATCH v5 " Dave Gerlach
2015-06-18 9:04 ` Ohad Ben-Cohen
2015-06-18 16:01 ` Dave Gerlach
2015-06-18 17:21 ` Ohad Ben-Cohen
2015-05-22 20:45 ` [PATCH v4 2/4] remoteproc: add a rproc ops for performing address translation Dave Gerlach
2015-05-22 20:45 ` [PATCH v4 3/4] Documentation: dt: add bindings for TI Wakeup M3 processor Dave Gerlach
2015-05-22 20:45 ` [PATCH v4 4/4] remoteproc/wkup_m3: add a remoteproc driver for TI Wakeup M3 Dave Gerlach
2015-06-17 7:12 ` [PATCH v4 0/4] remoteproc: Introduce wkup_m3_rproc driver Ohad Ben-Cohen
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=1432327530-48032-1-git-send-email-d-gerlach@ti.com \
--to=d-gerlach@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=ohad@wizery.com \
--cc=s-anna@ti.com \
--cc=tony@atomide.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
all inboxes | Powered by JetHome®