linux-kernel - Re: [PATCH 1/1] arm64: dts: imx8mp: remove arm, primecell-periphid at etm nodes

Open Source and information security mailing list archives

Message-ID: <ZKbSC8LBjLuo3ygD@lizhi-Precision-Tower-5810>
Date:   Thu, 6 Jul 2023 10:39:07 -0400
From:   Frank Li <Frank.li@....com>
To:     Robin Murphy <robin.murphy@....com>
Cc:     Lucas Stach <l.stach@...gutronix.de>,
        Alexander Stein <alexander.stein@...tq-group.com>,
        suzuki.poulose@....com, coresight@...ts.linaro.org,
        imx@...ts.linux.dev, Rob Herring <robh+dt@...nel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
        Conor Dooley <conor+dt@...nel.org>,
        Shawn Guo <shawnguo@...nel.org>,
        Sascha Hauer <s.hauer@...gutronix.de>,
        Pengutronix Kernel Team <kernel@...gutronix.de>,
        Fabio Estevam <festevam@...il.com>,
        NXP Linux Team <linux-imx@....com>,
        Marek Vasut <marex@...x.de>, Peng Fan <peng.fan@....com>,
        Adam Ford <aford173@...il.com>,
        Laurent Pinchart <laurent.pinchart@...asonboard.com>,
        "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" 
        <devicetree@...r.kernel.org>,
        "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" 
        <linux-arm-kernel@...ts.infradead.org>,
        open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/1] arm64: dts: imx8mp: remove arm, primecell-periphid
 at etm nodes

On Thu, Jul 06, 2023 at 12:06:19PM +0100, Robin Murphy wrote:
> > > 
> > > Am Mittwoch, 5. Juli 2023, 22:59:53 CEST schrieb Frank Li:
> > > > The reg size of etm nodes is incorrectly set to 64k instead of 4k. This
> > > > leads to a crash when calling amba_read_periphid().  After corrected reg
> > > > size, amba_read_periphid() retrieve the correct periphid.
> > > > arm,primecell-periphid were removed from the etm nodes.
> > > 
> > > So this means the reference manual is wrong here? It clearly states the size
> > > is 64kiB. Reference Manual i.MX8MP Rev 1. 06/2021
> > > On a side note: Is imx8mq affected by this as well? The DAP memory table lists
> > > similar sizes in the RM .
> > > 
> > Note that the 64K MMIO space per device is really an alignment thing.
> > It's a recommendation from ARM to allow individual device MMIO regions
> > to be mapped on kernels with 64K page size. Most of the time the real
> > MMIO space occupied by the device is actually much smaller than 64K.
> 
> Indeed, it's quite common for TRM memory maps to be written in terms of the
> interconnect configuration, i.e. from the point of view of the interconnect
> itself, that whole range of address space is assigned to that peripheral,
> and it may even be true that the entire range is routed to the port where
> that peripheral is connected. However what's of more interest for DT is how
> much of that range the peripheral itself actually decodes.

Yes, there are not problem by mapping bigger space in most case.

amba bus's periphal use close to end of region to show device's identical
information.

In drivers/amba/bus.c, 

amba_read_periphid()
{
	...
	size = resource_size(&dev->res);
	...
	for (pid = 0, i = 0; i < 4; i++)
		pid |= (readl(tmp + size - 0x20 + 4 * i) & 255) << (i * 8);
}

So the range in DTS for arm,primecell should be actual IP address space.

> 
> Robin.
> 
> > 
> > _______________________________________________
> > linux-arm-kernel mailing list
> > linux-arm-kernel@...ts.infradead.org
> > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives