From: Michael Auchter <michael.auchter@ni.com>
To: Ben Levinsky <BLEVINSK@xilinx.com>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-remoteproc@vger.kernel.org"
<linux-remoteproc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: RE: [PATCH v14 5/5] remoteproc: Add initial zynqmp R5 remoteproc driver
Date: Fri, 18 Sep 2020 11:07:21 -0500 [thread overview]
Message-ID: <20200918160721.GD15530@xaphan> (raw)
In-Reply-To: <BYAPR02MB4407A552ECBA907DFC3CEC91B53E0@BYAPR02MB4407.namprd02.prod.outlook.com>
On Thu, Sep 17, 2020 at 10:50:42PM +0000, Ben Levinsky wrote:
> In addition to device tree, is there particular linker script you use
> for your R5 application? For example with OCM? As presently this
> driver only has DDR and TCM as supported regions to load into
The firmware is being loaded to TCM.
I'm able to use this driver to load and run my firmware on both R5
cores, but only after I change the incorrect:
rpu_mode = lockstep_mode
assignment to:
rpu_mode = lockstep_mode ? PM_RPU_MODE_LOCKSTEP
: PM_RPU_MODE_SPLIT;
WARNING: multiple messages have this Message-ID (diff)
From: Michael Auchter <michael.auchter@ni.com>
To: Ben Levinsky <BLEVINSK@xilinx.com>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-remoteproc@vger.kernel.org"
<linux-remoteproc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: RE: [PATCH v14 5/5] remoteproc: Add initial zynqmp R5 remoteproc driver
Date: Fri, 18 Sep 2020 11:07:21 -0500 [thread overview]
Message-ID: <20200918160721.GD15530@xaphan> (raw)
In-Reply-To: <BYAPR02MB4407A552ECBA907DFC3CEC91B53E0@BYAPR02MB4407.namprd02.prod.outlook.com>
On Thu, Sep 17, 2020 at 10:50:42PM +0000, Ben Levinsky wrote:
> In addition to device tree, is there particular linker script you use
> for your R5 application? For example with OCM? As presently this
> driver only has DDR and TCM as supported regions to load into
The firmware is being loaded to TCM.
I'm able to use this driver to load and run my firmware on both R5
cores, but only after I change the incorrect:
rpu_mode = lockstep_mode
assignment to:
rpu_mode = lockstep_mode ? PM_RPU_MODE_LOCKSTEP
: PM_RPU_MODE_SPLIT;
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-09-18 16:25 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-17 19:43 [PATCH v14 0/5] Provide basic driver to control Arm R5 co-processor found on Xilinx ZynqMP Ben Levinsky
2020-09-17 19:43 ` Ben Levinsky
2020-09-17 19:43 ` [PATCH v14 1/5] firmware: xilinx: Add ZynqMP firmware ioctl enums for RPU configuration Ben Levinsky
2020-09-17 19:43 ` Ben Levinsky
2020-09-17 19:43 ` [PATCH v14 2/5] firmware: xilinx: Add shutdown/wakeup APIs Ben Levinsky
2020-09-17 19:43 ` Ben Levinsky
2020-09-17 19:43 ` [PATCH v14 3/5] firmware: xilinx: Add RPU configuration APIs Ben Levinsky
2020-09-17 19:43 ` Ben Levinsky
2020-09-17 19:43 ` [PATCH v14 4/5] dt-bindings: remoteproc: Add documentation for ZynqMP R5 rproc bindings Ben Levinsky
2020-09-17 19:43 ` Ben Levinsky
2020-09-18 6:28 ` Punit Agrawal
2020-09-18 6:28 ` Punit Agrawal
2020-09-17 19:43 ` [PATCH v14 5/5] remoteproc: Add initial zynqmp R5 remoteproc driver Ben Levinsky
2020-09-17 19:43 ` Ben Levinsky
2020-09-17 22:11 ` Michael Auchter
2020-09-17 22:11 ` Michael Auchter
2020-09-17 22:18 ` Ben Levinsky
2020-09-17 22:18 ` Ben Levinsky
2020-09-17 22:50 ` Ben Levinsky
2020-09-17 22:50 ` Ben Levinsky
2020-09-18 16:07 ` Michael Auchter [this message]
2020-09-18 16:07 ` Michael Auchter
2020-09-18 18:01 ` Ben Levinsky
2020-09-18 18:01 ` Ben Levinsky
2020-09-18 19:06 ` Michael Auchter
2020-09-18 19:06 ` Michael Auchter
2020-09-19 1:53 ` Wendy Liang
2020-09-19 1:53 ` Wendy Liang
2020-09-20 23:16 ` Ben Levinsky
2020-09-20 23:16 ` Ben Levinsky
2020-09-21 5:09 ` Wendy Liang
2020-09-21 5:09 ` Wendy Liang
2020-09-21 5:11 ` Wendy Liang
2020-09-21 5:11 ` Wendy Liang
2020-09-21 10:04 ` Punit Agrawal
2020-09-21 10:04 ` Punit Agrawal
2020-09-18 16:04 ` Michael Auchter
2020-09-18 16:04 ` Michael Auchter
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=20200918160721.GD15530@xaphan \
--to=michael.auchter@ni.com \
--cc=BLEVINSK@xilinx.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.