remoteproc: depend on EXPERIMENTAL
Remoteproc is still under development and as it gets traction we definitely expect to do some changes in the binary format (most probably only in the resource table, e.g. the upcoming move to TLV-based entries). Active testing and use of remoteproc is most welcome, but we don't want users to expect backward binary compatibility with the preliminary images we have today. Therefore mark remoteproc as EXPERIMENTAL, and explicitly inform the user about this when a new remote processor is registered. Signed-off-by: Ohad Ben-Cohen <ohad@wizery.com> Cc: Stephen Boyd <sboyd@codeaurora.org> Cc: Rob Clark <rob@ti.com> Cc: Mark Grosen <mgrosen@ti.com> Cc: Ludovic BARRE <ludovic.barre@stericsson.com>
This commit is contained in:
parent
f8289edae4
commit
489d129a2f
|
@ -1,8 +1,9 @@
|
|||
menu "Remoteproc drivers"
|
||||
menu "Remoteproc drivers (EXPERIMENTAL)"
|
||||
|
||||
# REMOTEPROC gets selected by whoever wants it
|
||||
config REMOTEPROC
|
||||
tristate
|
||||
depends on EXPERIMENTAL
|
||||
|
||||
config OMAP_REMOTEPROC
|
||||
tristate "OMAP remoteproc support"
|
||||
|
|
|
@ -1275,6 +1275,9 @@ int rproc_register(struct rproc *rproc)
|
|||
|
||||
dev_info(rproc->dev, "%s is available\n", rproc->name);
|
||||
|
||||
dev_info(dev, "Note: remoteproc is still under development and considered experimental.\n");
|
||||
dev_info(dev, "THE BINARY FORMAT IS NOT YET FINALIZED, and backward compatibility isn't yet guaranteed.\n");
|
||||
|
||||
/* create debugfs entries */
|
||||
rproc_create_debug_dir(rproc);
|
||||
|
||||
|
|
Loading…
Reference in New Issue