[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.21.2010081304550.23978@sstabellini-ThinkPad-T480s>
Date: Thu, 8 Oct 2020 13:22:09 -0700 (PDT)
From: Stefano Stabellini <stefano.stabellini@...inx.com>
To: Ben Levinsky <BLEVINSK@...inx.com>, linus.walleij@...aro.org
cc: Catalin Marinas <catalin.marinas@....com>,
Stefano Stabellini <stefanos@...inx.com>,
"Ed T. Mooring" <emooring@...inx.com>,
"sunnyliangjy@...il.com" <sunnyliangjy@...il.com>,
Punit Agrawal <punit1.agrawal@...hiba.co.jp>,
Michal Simek <michals@...inx.com>,
"michael.auchter@...com" <michael.auchter@...com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@...r.kernel.org>,
Mathieu Poirier <mathieu.poirier@...aro.org>,
"linux-remoteproc@...r.kernel.org" <linux-remoteproc@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Rob Herring <robh+dt@...nel.org>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>
Subject: RE: [PATCH v18 4/5] dt-bindings: remoteproc: Add documentation for
ZynqMP R5 rproc bindings
On Thu, 8 Oct 2020, Ben Levinsky wrote:
> > Does it mean that the main CPU see the memory of the
> > R5 as "some kind of TCM" and that TCM is physically
> > mapped at 0xffe00000 (ITCM) and 0xffe20000 (DTCM)?
> >
> > If the first is ITCM and the second DTCM that is pretty
> > important to point out, since this reflects the harvard
> > architecture properties of these two memory areas.
Hi Linus,
I don't think Xilinx TCMs are split in ITCM and DTCM in the way you
describe here: https://www.kernel.org/doc/Documentation/arm/tcm.txt.
Either TCM could be used for anything. See
https://www.xilinx.com/support/documentation/user_guides/ug1085-zynq-ultrascale-trm.pdf
at page 82.
Powered by blists - more mailing lists