linux-kernel - [RFC 0/4] STE-modem remoteproc driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 22 Jun 2012 16:31:06 +0200
From:	sjur.brandeland@...ricsson.com
To:	Ohad Ben-Cohen <ohad@...ery.com>
Cc:	linux-kernel@...r.kernel.org, Arnd Bergmann <arnd@...db.de>,
	Linus Walleij <linus.walleij@...aro.org>,
	Sjur Brændeland <sjurbren@...il.com>,
	Sjur Brændeland <sjur.brandeland@...ricsson.com>
Subject: [RFC 0/4] STE-modem remoteproc driver

From: Sjur Brændeland <sjur.brandeland@...ricsson.com>

Hi Ohad,

This is the initial stab on the remoteproc driver for ST-Ericsson modems.
Please let me know what you think.

remoteproc_ste_modem features:
For kicking to work I need to declare what IDs I'm currently using, so I had to
iterate over the rproc->notifyids to find the IDs. 

A sysfs file is introduced for switching on/off the modem, as modem
start-up must be controlled from user space. 

As mentioned before I need the firmware to be allocated first in the shared
memory are. So in order to reserve  space for firmware at the start of the
memory region, I had to allocate dma memory before calling rproc_register(),
and then releasing it afterward.

I do not yet have an implementation of the stemod_kick module available. It
might take a while before this is upstreamed. The stemod_kick functions are
looked up dynamically so this is not a build issue.

The platform device is not yet upstreamed either. But it should be pretty simple,
it basically just provides the shared memory area to the driver.

I also included one fix in this patch-set. It doesn't seems like carveout for
non-iommu is working correctly. I added a simple patch for this.
Let me know what you think, and how to proceed for this fix.

Best regards,
Sjur Brændeland

Sjur Brændeland (4):
  remoteproc: Bugfix assign device address to carveout (noiommu)
  remoteproc: Add custom STE-modem firmware loader.
  remoteproc: Add API (header file) for kicking STE modems
  remoteproc: Add driver for STE Modem

 drivers/remoteproc/Kconfig                       |   10 +
 drivers/remoteproc/Makefile                      |    3 +
 drivers/remoteproc/remoteproc_core.c             |    4 +
 drivers/remoteproc/remoteproc_internal.h         |    1 +
 drivers/remoteproc/remoteproc_ste_modem_loader.c |  179 ++++++++++++
 drivers/remoteproc/ste_modem_rproc.c             |  333 ++++++++++++++++++++++
 drivers/remoteproc/stemod_kick.h                 |  113 ++++++++
 7 files changed, 643 insertions(+), 0 deletions(-)
 create mode 100644 drivers/remoteproc/remoteproc_ste_modem_loader.c
 create mode 100644 drivers/remoteproc/ste_modem_rproc.c
 create mode 100644 drivers/remoteproc/stemod_kick.h

-- 
1.7.5.4

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/