From: loic pallardy <loic.pallardy@st.com>
To: Matt Redfearn <matt.redfearn@imgtec.com>,
<bjorn.andersson@linaro.org>, <ohad@wizery.com>,
<lee.jones@linaro.org>
Cc: <linux-remoteproc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <kernel@stlinux.com>
Subject: Re: [PATCH v3 02/20] remoteproc: core: Add function to dump resource table
Date: Mon, 17 Oct 2016 18:26:30 +0200 [thread overview]
Message-ID: <b48aeeb8-9f7d-aa85-c921-79cf8e2876f4@st.com> (raw)
In-Reply-To: <3d83f9e3-a04a-914e-88ba-9f94a2e3827b@imgtec.com>
On 10/14/2016 10:37 AM, Matt Redfearn wrote:
> Hi Loic,
>
Hi Matt,
>
> On 12/10/16 17:00, Loic Pallardy wrote:
>> Firmware can be loaded with a resource table, which details
>> resources needed by coprocessor like carevout memory, virtual
>> device, trace log buffer etc.
>>
>> Until now, no method exists to display resource table content.
>> This function adds the capability to display the different
>> resources associated to a firmware if DEBUG is enabled.
>
> How about instead adding this to a debugfs entry such that one can
> always access it rather than having to find it in the kernel log, only
> if DEBUG was enabled?
It was one of my remarks on V1, but Lee prefers to have this change on
the top of this series.
Both functions are their interest:
- current function help to analyse changes done during boot sequence
between original and modified resource table
- debugfs function will allow to display resource table provided to
coprocessor and understand what could be wrong in case of error.
I propose to add a patch on the top of the series to support debugfs
interface like mentioned previously by Lee.
Regards,
Loic
>
> Thanks,
> Matt
>
>>
>> Signed-off-by: Lee Jones <lee.jones@linaro.org>
>> Signed-off-by: Loic Pallardy <loic.pallardy@st.com>
>> ---
>> drivers/remoteproc/remoteproc_core.c | 85
>> ++++++++++++++++++++++++++++++++++++
>> 1 file changed, 85 insertions(+)
>>
>> diff --git a/drivers/remoteproc/remoteproc_core.c
>> b/drivers/remoteproc/remoteproc_core.c
>> index 67633ee..3c8395b 100644
>> --- a/drivers/remoteproc/remoteproc_core.c
>> +++ b/drivers/remoteproc/remoteproc_core.c
>> @@ -785,6 +785,91 @@ static void rproc_resource_cleanup(struct rproc
>> *rproc)
>> rproc_remove_virtio_dev(rvdev);
>> }
>> +static void rproc_dump_resource_table(struct rproc *rproc,
>> + struct resource_table *table, int size)
>> +{
>> + static const char *types[] = {"carveout", "devmem", "trace",
>> "vdev"};
>> + struct device *dev = &rproc->dev;
>> + struct fw_rsc_carveout *c;
>> + struct fw_rsc_devmem *d;
>> + struct fw_rsc_trace *t;
>> + struct fw_rsc_vdev *v;
>> + int i, j;
>> +
>> + if (!table) {
>> + dev_dbg(dev, "No resource table found\n");
>> + return;
>> + }
>> +
>> + dev_dbg(dev, "Resource Table: Version %d with %d entries [size:
>> %x]\n",
>> + table->ver, table->num, size);
>> +
>> + for (i = 0; i < table->num; i++) {
>> + int offset = table->offset[i];
>> + struct fw_rsc_hdr *hdr = (void *)table + offset;
>> + void *rsc = (void *)hdr + sizeof(*hdr);
>> +
>> + switch (hdr->type) {
>> + case RSC_CARVEOUT:
>> + c = rsc;
>> + dev_dbg(dev, "Entry %d is of type %s\n", i,
>> types[hdr->type]);
>> + dev_dbg(dev, " Device Address 0x%x\n", c->da);
>> + dev_dbg(dev, " Physical Address 0x%x\n", c->pa);
>> + dev_dbg(dev, " Length 0x%x Bytes\n", c->len);
>> + dev_dbg(dev, " Flags 0x%x\n", c->flags);
>> + dev_dbg(dev, " Reserved (should be zero) [%d]\n",
>> c->reserved);
>> + dev_dbg(dev, " Name %s\n\n", c->name);
>> + break;
>> + case RSC_DEVMEM:
>> + d = rsc;
>> + dev_dbg(dev, "Entry %d is of type %s\n", i,
>> types[hdr->type]);
>> + dev_dbg(dev, " Device Address 0x%x\n", d->da);
>> + dev_dbg(dev, " Physical Address 0x%x\n", d->pa);
>> + dev_dbg(dev, " Length 0x%x Bytes\n", d->len);
>> + dev_dbg(dev, " Flags 0x%x\n", d->flags);
>> + dev_dbg(dev, " Reserved (should be zero) [%d]\n",
>> d->reserved);
>> + dev_dbg(dev, " Name %s\n\n", d->name);
>> + break;
>> + case RSC_TRACE:
>> + t = rsc;
>> + dev_dbg(dev, "Entry %d is of type %s\n", i,
>> types[hdr->type]);
>> + dev_dbg(dev, " Device Address 0x%x\n", t->da);
>> + dev_dbg(dev, " Length 0x%x Bytes\n", t->len);
>> + dev_dbg(dev, " Reserved (should be zero) [%d]\n",
>> t->reserved);
>> + dev_dbg(dev, " Name %s\n\n", t->name);
>> + break;
>> + case RSC_VDEV:
>> + v = rsc;
>> + dev_dbg(dev, "Entry %d is of type %s\n", i,
>> types[hdr->type]);
>> +
>> + dev_dbg(dev, " ID %d\n", v->id);
>> + dev_dbg(dev, " Notify ID %d\n", v->notifyid);
>> + dev_dbg(dev, " Device features 0x%x\n", v->dfeatures);
>> + dev_dbg(dev, " Guest features 0x%x\n", v->gfeatures);
>> + dev_dbg(dev, " Config length 0x%x\n", v->config_len);
>> + dev_dbg(dev, " Status 0x%x\n", v->status);
>> + dev_dbg(dev, " Number of vrings %d\n", v->num_of_vrings);
>> + dev_dbg(dev, " Reserved (should be zero) [%d][%d]\n\n",
>> + v->reserved[0], v->reserved[1]);
>> +
>> + for (j = 0; j < v->num_of_vrings; j++) {
>> + dev_dbg(dev, " Vring %d\n", j);
>> + dev_dbg(dev, " Device Address 0x%x\n",
>> v->vring[j].da);
>> + dev_dbg(dev, " Alignment %d\n", v->vring[j].align);
>> + dev_dbg(dev, " Number of buffers %d\n",
>> v->vring[j].num);
>> + dev_dbg(dev, " Notify ID %d\n",
>> v->vring[j].notifyid);
>> + dev_dbg(dev, " Physical Address 0x%x\n\n",
>> + v->vring[j].pa);
>> + }
>> + break;
>> + default:
>> + dev_dbg(dev, "Invalid resource type found: %d [hdr: %p]\n",
>> + hdr->type, hdr);
>> + return;
>> + }
>> + }
>> +}
>> +
>> int rproc_request_resource(struct rproc *rproc, u32 type, void
>> *resource)
>> {
>> struct device *dev = &rproc->dev;
>
next prev parent reply other threads:[~2016-10-17 16:26 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-12 16:00 [PATCH v3 00/20] remoteproc: Allow platform-specific drivers to request resources Loic Pallardy
2016-10-12 16:00 ` [PATCH v3 01/20] remoteproc: core: New API to add new resources to the resource table Loic Pallardy
2016-10-12 16:00 ` [PATCH v3 02/20] remoteproc: core: Add function to dump " Loic Pallardy
2016-10-14 8:37 ` Matt Redfearn
2016-10-17 16:26 ` loic pallardy [this message]
2016-10-12 16:00 ` [PATCH v3 03/20] remoteproc: core: Add function to amend an existing resource table entry Loic Pallardy
2016-10-12 16:00 ` [PATCH v3 04/20] remoteproc: core: Add function to append a new " Loic Pallardy
2016-10-12 16:00 ` [PATCH v3 05/20] remoteproc: core: Add function to over-ride current resource table Loic Pallardy
2016-10-12 16:00 ` [PATCH v3 06/20] remoteproc: core: Associate action to resource request Loic Pallardy
2016-10-12 16:00 ` [PATCH v3 07/20] remoteproc: core: Add RSC_VDEV support to rproc_request_resource Loic Pallardy
2016-10-12 16:00 ` [PATCH v3 08/20] remoteproc: core: Complete VDEV support in rproc_dump_resource_table function Loic Pallardy
2016-10-12 16:00 ` [PATCH v3 09/20] remoteproc: core: Unify rproc_dump_resource_table debug messages Loic Pallardy
2016-10-12 16:00 ` [PATCH v3 10/20] remoteproc: core: Call rproc_dump_resource_table only if debug is activated Loic Pallardy
2016-10-12 16:00 ` [PATCH v3 11/20] remoteproc: core: Correction carveout name comparison in rproc_update_resource_table_entry Loic Pallardy
2016-10-12 16:00 ` [PATCH v3 12/20] remoteproc: core: Add function to verify an existing resource in rsc table Loic Pallardy
2016-10-12 16:00 ` [PATCH v3 13/20] remoteproc: core: Add vdev support to resource amending function Loic Pallardy
2016-10-12 16:00 ` [PATCH v3 14/20] remoteproc: core: Add force mode " Loic Pallardy
2016-10-12 16:00 ` [PATCH v3 15/20] remoteproc: core: Append resource only if .resource_table section is large enough Loic Pallardy
2016-10-12 16:00 ` [PATCH v3 16/20] remoteproc: core: Add resource request action support Loic Pallardy
2016-10-12 16:00 ` [PATCH v3 17/20] remoteproc: core: Add function to verify resource table consistency Loic Pallardy
2016-10-12 16:00 ` [PATCH v3 18/20] remoteproc: core: Clean-up resource table sanity checks Loic Pallardy
2016-10-12 16:00 ` [PATCH v3 19/20] remotecore: core: Add resource table pointer argument to rproc_handle_resource Loic Pallardy
2016-10-12 16:00 ` [PATCH v3 20/20] remoteproc: core: Support empty resource tables Loic Pallardy
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=b48aeeb8-9f7d-aa85-c921-79cf8e2876f4@st.com \
--to=loic.pallardy@st.com \
--cc=bjorn.andersson@linaro.org \
--cc=kernel@stlinux.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=matt.redfearn@imgtec.com \
--cc=ohad@wizery.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
all inboxes | Powered by JetHome®