Hi, This patch series adds a wkup_m3_rproc driver for TI AM335x 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 once it is booted. This patch was split off from v4 of the am335x suspend series, found here [1]. I have pushed a branch based on v3.19-rc1 containing all dependencies here [2] for am33xx suspend for a higher level view of the entire series of patch sets. This series is required for a coming series "drivers: soc: ti: Introduce wkup_m3_ipc driver" that boots this rproc driver and handles the communication layer between the SoC and this remote processor. This patch set depends on series "couple of generic remoteproc enhancements" by Suman Anna found here [3]. The driver expects to load firmware am335x-pm-firmware.elf from /lib/firmware which is found here [4]. Regards, Dave [1] http://www.spinics.net/lists/linux-omap/msg109331.html [2] https://github.com/dgerlach/linux-pm/tree/pm-am335x-v3.19-rc1 [3] http://www.spinics.net/lists/arm-kernel/msg362961.html [4] https://git.ti.com/ti-cm3-pm-firmware/amx3-cm3/commits/next Dave Gerlach (3): ARM: OMAP2+: Use pdata-quirks for wkup_m3 deassert_hardreset Documentation: dt: add ti,am3353-wkup-m3 bindings remoteproc: wkup_m3: Add wkup_m3 remote proc driver .../bindings/remoteproc/wkup_m3_rproc.txt | 32 ++++ arch/arm/mach-omap2/pdata-quirks.c | 13 ++ drivers/remoteproc/Kconfig | 12 ++ drivers/remoteproc/Makefile | 1 + drivers/remoteproc/wkup_m3_rproc.c | 175 +++++++++++++++++++++ include/linux/platform_data/wkup_m3.h | 23 +++ 6 files changed, 256 insertions(+) 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.1.0 -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
