From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 8F02AC46467 for ; Tue, 20 Dec 2022 12:52:04 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233601AbiLTMvx (ORCPT ); Tue, 20 Dec 2022 07:51:53 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58650 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233507AbiLTMvt (ORCPT ); Tue, 20 Dec 2022 07:51:49 -0500 Received: from alexa-out-sd-02.qualcomm.com (alexa-out-sd-02.qualcomm.com [199.106.114.39]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 029A1B85E; Tue, 20 Dec 2022 04:51:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=quicinc.com; i=@quicinc.com; q=dns/txt; s=qcdkim; t=1671540704; x=1703076704; h=message-id:date:mime-version:subject:to:references:from: in-reply-to:content-transfer-encoding; bh=vHdfASFYTb+WMKgS3aMJpiVanrEiSZPCZ0RtpyOP1h8=; b=kB9aSDyM8L2n/qt/d2c9O6AEh2zRdJoWVuEuIl86WYZEYZhaAAFZdBRO IpBR9X5T1XMi5XRq9VzeIUUEm2szFu6ZOHz/5DOpi0SxvvX1uxdkpgY/d Q7ZztGOizzEP0UMQ656yrTUbrnjrxIQnhV0Z0Wsy/lAr9TPN/ibu+y6xC o=; Received: from unknown (HELO ironmsg-SD-alpha.qualcomm.com) ([10.53.140.30]) by alexa-out-sd-02.qualcomm.com with ESMTP; 20 Dec 2022 04:51:43 -0800 X-QCInternal: smtphost Received: from nasanex01c.na.qualcomm.com ([10.45.79.139]) by ironmsg-SD-alpha.qualcomm.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 20 Dec 2022 04:51:43 -0800 Received: from [10.214.66.81] (10.80.80.8) by nasanex01c.na.qualcomm.com (10.45.79.139) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.986.36; Tue, 20 Dec 2022 04:51:37 -0800 Message-ID: Date: Tue, 20 Dec 2022 18:21:35 +0530 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.13.1 Subject: Re: [PATCH v3 2/2] docs: remoteproc: Update section header name requirement Content-Language: en-US To: Srinivasa Rao Mandadapu , , , , , , , , , , , , , , , , , , , , References: <1671523269-21154-1-git-send-email-quic_srivasam@quicinc.com> <1671523269-21154-3-git-send-email-quic_srivasam@quicinc.com> From: Mukesh Ojha In-Reply-To: <1671523269-21154-3-git-send-email-quic_srivasam@quicinc.com> Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [10.80.80.8] X-ClientProxiedBy: nasanex01a.na.qualcomm.com (10.52.223.231) To nasanex01c.na.qualcomm.com (10.45.79.139) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, On 12/20/2022 1:31 PM, Srinivasa Rao Mandadapu wrote: > Add section header name requirement specification in elf segments. > > Signed-off-by: Srinivasa Rao Mandadapu LGTM. Reviewed-by: Mukesh Ojha -Mukesh > --- > 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 348ee7e..0c9c10a 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