From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Loic PALLARDY <loic.pallardy@st.com>
Cc: Ohad Ben-Cohen <ohad@wizery.com>,
"linux-remoteproc@vger.kernel.org"
<linux-remoteproc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
"linux-soc@vger.kernel.org" <linux-soc@vger.kernel.org>,
Suman Anna <s-anna@ti.com>,
Avaneesh Kumar Dwivedi <akdwived@codeaurora.org>
Subject: Re: [PATCH v2 2/4] remoteproc: Rename "load_rsc_table" to "parse_fw"
Date: Wed, 3 Jan 2018 12:19:40 -0800 [thread overview]
Message-ID: <20180103201940.GI12655@minitux> (raw)
In-Reply-To: <c9204e2d67ce40a0a218fd679e5370a0@SFHDAG7NODE2.st.com>
On Wed 03 Jan 05:15 PST 2018, Loic PALLARDY wrote:
> > -----Original Message-----
> > From: linux-remoteproc-owner@vger.kernel.org [mailto:linux-remoteproc-
> > owner@vger.kernel.org] On Behalf Of Loic PALLARDY
> > Sent: Wednesday, January 03, 2018 11:27 AM
> > To: Bjorn Andersson <bjorn.andersson@linaro.org>; Ohad Ben-Cohen
> > <ohad@wizery.com>
> > Cc: linux-remoteproc@vger.kernel.org; linux-kernel@vger.kernel.org; linux-
> > arm-msm@vger.kernel.org; linux-soc@vger.kernel.org; Suman Anna <s-
> > anna@ti.com>; Avaneesh Kumar Dwivedi <akdwived@codeaurora.org>
> > Subject: RE: [PATCH v2 2/4] remoteproc: Rename "load_rsc_table" to
> > "parse_fw"
> > > -----Original Message-----
> > > From: linux-remoteproc-owner@vger.kernel.org [mailto:linux-
> > remoteproc-
> > > owner@vger.kernel.org] On Behalf Of Bjorn Andersson
[..]
> > > - /* load resource table */
> > > - ret = rproc_load_rsc_table(rproc, fw);
> > > + /* parse firmware resources */
> > > + ret = rproc_parse_fw(rproc, fw);
> > Hi Bjorn,
> >
> > I think it will be good to keep resource (aka rsc) in function name. only
> > "parse_fw" is not enough explicit and we don't know why rproc should parse
> > firmware.
> >
> > Regards,
> > Loic
> Forgot my previous remark, better understanding thanks to the rest of
> the series.
> Anyway, will be nice to have a comment here as it is not only parsing
> the firmware, you collect some information like copy of the resource
> table, list of elf segment to dump...
> I think it is important to be clear about resource table management as
> it is a key element of the remoteproc core, where it is loaded, where
> it is copied back in memory...
I didn't manage to come up with a better name, but adding a comment to
capture this makes a lot of sense. I will respin this patch!
Thanks for reviewing this!
Regards,
Bjorn
next prev parent reply other threads:[~2018-01-03 20:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-26 20:38 [PATCH v2 0/4] Remoteproc core dump support Bjorn Andersson
2017-12-26 20:38 ` [PATCH v2 1/4] remoteproc: Add remote processor coredump support Bjorn Andersson
2017-12-26 20:38 ` [PATCH v2 2/4] remoteproc: Rename "load_rsc_table" to "parse_fw" Bjorn Andersson
2018-01-03 10:26 ` Loic PALLARDY
2018-01-03 13:15 ` Loic PALLARDY
2018-01-03 20:19 ` Bjorn Andersson [this message]
2017-12-26 20:38 ` [PATCH v2 3/4] soc: qcom: mdt-loader: Return relocation base Bjorn Andersson
2017-12-26 20:38 ` [PATCH v2 4/4] remoteproc: qcom: Register segments for core dump Bjorn Andersson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180103201940.GI12655@minitux \
--to=bjorn.andersson@linaro.org \
--cc=akdwived@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=linux-soc@vger.kernel.org \
--cc=loic.pallardy@st.com \
--cc=ohad@wizery.com \
--cc=s-anna@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox