[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150926093835.GA20255@n2100.arm.linux.org.uk>
Date: Sat, 26 Sep 2015 10:38:35 +0100
From: Russell King - ARM Linux <linux@....linux.org.uk>
To: Yingjoe Chen <yingjoe.chen@...iatek.com>
Cc: Matthias Brugger <matthias.bgg@...il.com>,
devicetree@...r.kernel.org, Arnd Bergmann <arnd@...db.de>,
Stephen Boyd <sboyd@...eaurora.org>,
linux-kernel@...r.kernel.org, Rob Herring <robh+dt@...nel.org>,
linux-mediatek@...ts.infradead.org,
Sascha Hauer <kernel@...gutronix.de>,
Olof Johansson <olof@...om.net>, srv_heupstream@...iatek.com,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v4 3/5] ARM: mediatek: add smp bringup code
On Thu, Sep 24, 2015 at 11:38:58PM +0800, Yingjoe Chen wrote:
> +struct mtk_smp_boot_info {
> + unsigned long smp_base;
...
> +static const struct mtk_smp_boot_info mtk_mt8135_tz_boot = {
> + 0x80002000, 0x3fc,
...
> +static const struct mtk_smp_boot_info mtk_mt6589_boot = {
> + 0x10002000, 0x34,
...
> + if (trustzone) {
> + /* smp_base(trustzone-bootinfo) is reserved by device tree */
> + mtk_smp_base = phys_to_virt(mtk_smp_info->smp_base);
I can't say whether this is correct or not, as we've got rid of most of
the information that would allow me to make that decision.
The address passed to phys_to_virt() _must_ be one which is mapped by
the kernel as lowmem. I've no idea if the above would fall into that
category though.
--
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists