From: Srinivasa Rao Mandadapu <quic_srivasam@xxxxxxxxxxx> Add section header name requirement specification in elf segments. Signed-off-by: Srinivasa Rao Mandadapu <quic_srivasam@xxxxxxxxxxx> Signed-off-by: Mohammad Rafi Shaik <quic_mohs@xxxxxxxxxxx> Reviewed-by: Philippe Mathieu-Daudé <philmd@xxxxxxxxxx> Reviewed-by: Mukesh Ojha <quic_mojha@xxxxxxxxxxx> --- Documentation/staging/remoteproc.rst | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/Documentation/staging/remoteproc.rst b/Documentation/staging/remoteproc.rst index 348ee7e508ac..0c9c10a30c3d 100644 --- a/Documentation/staging/remoteproc.rst +++ b/Documentation/staging/remoteproc.rst @@ -244,7 +244,10 @@ according to the specified device address (might be a physical address if the remote processor is accessing memory directly). In addition to the standard ELF segments, most remote processors would -also include a special section which we call "the resource table". +also include a special section which we call the "resource table". +A "resource table" section name must start with the ".resource_table" prefix, +optionally having a more descriptive string appended. For example, +".resource_table.my_rproc" is a valid section name. The resource table contains system resources that the remote processor requires before it should be powered on, such as allocation of physically -- 2.25.1
