[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b4150898-d5f0-894d-2c69-b98e56142481@quicinc.com>
Date: Tue, 20 Dec 2022 12:57:35 +0530
From: Srinivasa Rao Mandadapu <quic_srivasam@...cinc.com>
To: Philippe Mathieu-Daudé <philmd@...aro.org>,
<linux-remoteproc@...r.kernel.org>, <agross@...nel.org>,
<andersson@...nel.org>, <lgirdwood@...il.com>,
<broonie@...nel.org>, <robh+dt@...nel.org>,
<quic_plai@...cinc.com>, <bgoswami@...cinc.com>, <perex@...ex.cz>,
<tiwai@...e.com>, <srinivas.kandagatla@...aro.org>,
<quic_rohkumar@...cinc.com>, <linux-arm-msm@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <swboyd@...omium.org>,
<judyhsiao@...omium.org>, <devicetree@...r.kernel.org>,
<krzysztof.kozlowski@...aro.org>, <mathieu.poirier@...aro.org>,
<corbet@....net>
Subject: Re: [PATCH v2 2/2] docs: remoteproc: Update section header name
requirement
On 12/15/2022 12:55 PM, Philippe Mathieu-Daudé wrote:
Thanks for your time Phil!!!
> On 13/12/22 10:48, Srinivasa Rao Mandadapu wrote:
>> Add section header name requirement specification in elf segments.
>>
>> Signed-off-by: Srinivasa Rao Mandadapu <quic_srivasam@...cinc.com>
>> ---
>> Documentation/staging/remoteproc.rst | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/Documentation/staging/remoteproc.rst
>> b/Documentation/staging/remoteproc.rst
>> index 348ee7e..3125030 100644
>> --- a/Documentation/staging/remoteproc.rst
>> +++ b/Documentation/staging/remoteproc.rst
>> @@ -245,6 +245,8 @@ 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".
>> +This resource table section name may have anything appended after it,
>> +but it must start with ".resource_table"
>
> What do you think of:
>
> In addition to the standard ELF segments, most remote processors would
> 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.
Okay. Will change accordingly and re-spin the patch set.
>
> Regards,
>
> Phil.
Powered by blists - more mailing lists