| author | Suman Anna <s-anna@ti.com> | |
| Mon, 15 Jan 2018 18:01:54 +0000 (12:01 -0600) | ||
| committer | Suman Anna <s-anna@ti.com> | |
| Mon, 8 Mar 2021 22:22:56 +0000 (16:22 -0600) | ||
| commit | 4eb45c11141832dc29e81744de6d89148c2a734e | |
| tree | 8bfa3657f13369f0e0ae6ed81ac96a4628bd67ca | tree | snapshot (tar.xz tar.gz zip) |
| parent | 4d4745e65701ab149344e998ef189f1a6f110efb | commit | diff |
remoteproc: add api for retrieving a rproc unique id
A new api, rproc_get_id(), is added to allow remoteproc/rpmsg clients
to be able to retrieve a fixed unique id associated with a rproc
device. Each of the rprocs is given an ida index as well, but this
is dynamic depending on the order rproc_alloc is called (probe order),
and also depends on what remote processor devices are instantiated.
This unique id needs to be supported for both DT and non-DT devices.
The platform device id or the remoteproc alias id are therefore
chosen for non-DT and DT devices respectively, with the assumption
that the remoteproc devices are created with known platform device
ids or alias ids in DT.
Signed-off-by: Suman Anna <s-anna@ti.com>
A new api, rproc_get_id(), is added to allow remoteproc/rpmsg clients
to be able to retrieve a fixed unique id associated with a rproc
device. Each of the rprocs is given an ida index as well, but this
is dynamic depending on the order rproc_alloc is called (probe order),
and also depends on what remote processor devices are instantiated.
This unique id needs to be supported for both DT and non-DT devices.
The platform device id or the remoteproc alias id are therefore
chosen for non-DT and DT devices respectively, with the assumption
that the remoteproc devices are created with known platform device
ids or alias ids in DT.
Signed-off-by: Suman Anna <s-anna@ti.com>
| drivers/remoteproc/remoteproc_core.c | diff | blob | history | |
| include/linux/remoteproc.h | diff | blob | history |