Hi Nishanth, On 24 August 2015 at 11:28, Nishanth Menon <n...@ti.com> wrote: > Hi, > > Many System on Chip(SoC) solutions are complex with multiple > processors on the same die dedicated to either general purpose of > specialized functions. Many examples do exist in today's SoCs from > various vendors. Typical examples are micro controllers such as an ARM > M3/M0 doing a offload of specific function such as event integration > or power management or controlling camera etc. > > Traditionally, the responsibility of loading up such a processor with > a firmware and communication has been with a High Level Operating > System(HLOS) such as Linux. However, there exists classes of products > where Linux would need to expect services from such a processor or > the delay of Linux and operating system being able to load up such a > firmware is unacceptable. > > The intent here is to introduce a simplified remoteproc framework > which can then be used to provide basic services to these remote > processors. > > Nishanth Menon (3): > drivers: Introduce a simplified remoteproc framework > remoteproc: Introduce a sandbox dummy driver > sandbox: Introduce dummy remoteproc nodes > > arch/sandbox/dts/test.dts | 13 + > common/Kconfig | 5 + > common/Makefile | 1 + > common/cmd_remoteproc.c | 224 ++++++++++++ > configs/sandbox_defconfig | 2 + > doc/device-tree-bindings/remoteproc/remoteproc.txt | 14 + > doc/driver-model/remoteproc-framework.txt | 163 +++++++++ > drivers/Kconfig | 2 + > drivers/Makefile | 1 + > drivers/remoteproc/Kconfig | 24 ++ > drivers/remoteproc/Makefile | 10 + > drivers/remoteproc/rproc-uclass.c | 406 > +++++++++++++++++++++ > drivers/remoteproc/sandbox_testproc.c | 243 ++++++++++++ > include/dm/uclass-id.h | 1 + > include/remoteproc.h | 81 ++++ > 15 files changed, 1190 insertions(+) > create mode 100644 common/cmd_remoteproc.c > create mode 100644 doc/device-tree-bindings/remoteproc/remoteproc.txt > create mode 100644 doc/driver-model/remoteproc-framework.txt > create mode 100644 drivers/remoteproc/Kconfig > create mode 100644 drivers/remoteproc/Makefile > create mode 100644 drivers/remoteproc/rproc-uclass.c > create mode 100644 drivers/remoteproc/sandbox_testproc.c > create mode 100644 include/remoteproc.h > > Simple test with test.dtb: > u-boot$ ./u-boot -d ./arch/sandbox/dts/test.dtb
Can you please also add a test to test/dm/remoteproc.c? It should try a few operations as a sanity check. Ideally it shouldn't output anything on the console. Regards, Simon _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
