| 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
| ||
|
Message-ID: <20150826065950.GB19594@leoy-linaro>
Date: Wed, 26 Aug 2015 14:59:50 +0800
From: Leo Yan <leo.yan@...aro.org>
To: Haojian Zhuang <haojian.zhuang@...aro.org>
Cc: Mark Rutland <mark.rutland@....com>,
Leif Lindholm <leif.lindholm@...aro.org>,
Rob Herring <robh+dt@...nel.org>,
Pawel Moll <Pawel.Moll@....com>,
Ian Campbell <ijc+devicetree@...lion.org.uk>,
Kumar Gala <galak@...eaurora.org>,
Catalin Marinas <Catalin.Marinas@....com>,
Will Deacon <Will.Deacon@....com>,
Jassi Brar <jassisinghbrar@...il.com>,
Bintian Wang <bintian.wang@...wei.com>,
Yiping Xu <xuyiping@...ilicon.com>,
Wei Xu <xuwei5@...ilicon.com>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"guodong.xu@...aro.org" <guodong.xu@...aro.org>,
Jian Zhang <zhangjian001@...ilicon.com>,
Zhenwei Wang <Zhenwei.wang@...ilicon.com>,
Haoju Mo <mohaoju@...ilicon.com>,
Dan Zhao <dan.zhao@...ilicon.com>,
"kongfei@...ilicon.com" <kongfei@...ilicon.com>,
Guangyue Zeng <zengguangyue@...ilicon.com>
Subject: Re: [PATCH v1 3/3] arm64: dts: add Hi6220 mailbox node
Hi Haojian,
On Wed, Aug 26, 2015 at 09:25:41AM +0800, Haojian Zhuang wrote:
> On Wed, 2015-08-26 at 00:00 +0800, Leo Yan wrote:
> > On Tue, Aug 25, 2015 at 09:43:14PM +0800, Haojian Zhuang wrote:
> > > On Tue, 2015-08-25 at 11:42 +0100, Mark Rutland wrote:
> > > > > > Are you then going to hack GRUB, release a special HiKey version of
> > > > > > GRUB, not support any other versions, and still can your firmware
> > > > > > UEFI?
> > > > >
> > > > > I don't need to hack GRUB at all.
> > > >
> > > > Then it is working for you by pure chance alone.
> > > >
> > > > Please listen to the advice you are being given here; we're trying to
> > > > ensure that your platform functions (and continues to function) as best
> > > > it can.
> > >
> > > Since we discussed a lot on this, let's make a conclusion on it.
> > >
> > > 1. UEFI could append the reserved buffer in it's memory mapping.
> > > 2. These reserved buffer must be declared in DT, since we also need to
> > > support non-UEFI (uboot) at the same time.
> > > 3. Mailbox node should reference reserved buffer by phandle in DT. Then
> > > map the buffer as non-cacheable in driver.
> > > 4. These reserved buffer must use "no-map" property since it should be
> > > non-cacheable in driver.
> >
> > For more specific discussion for DTS, i list two options at here;
> >
> > - Option 1: just simply reserve memory regions through memory node,
> > and mailbox node will directly use the buffer through reg ranges;
> >
> > - Option 2: use reserved-memory and mailbox node will refer phandle
> > of reserved-memory;
> >
> > These two options both can work well with UEFI and Uboot, but option 1
> > is more simple and straightforward; so i personally prefer it. But
> > look forwarding your guys' suggestion.
> >
> > Option 1:
> >
> > memory@0 {
> > device_type = "memory";
> > reg = <0x00000000 0x00000000 0x00000000 0x05e00000>,
> > <0x00000000 0x05f00000 0x00000000 0x00eff000>,
> > <0x00000000 0x06e00000 0x00000000 0x0060f000>,
> > <0x00000000 0x07410000 0x00000000 0x38bf0000>;
> > };
> >
> > [...]
> >
> > mailbox: mailbox@...10000 {
> > #mbox-cells = <1>;
> > compatible = "hisilicon,hi6220-mbox";
> > reg = <0x0 0xf7510000 0x0 0x1000>, /* IPC_S */
> > <0x0 0x06dff800 0x0 0x0800>; /* Mailbox buffer */
> > interrupts = <GIC_SPI 94 IRQ_TYPE_LEVEL_HIGH>;
> > };
> >
> > Option 2:
> >
> > memory@0 {
> > device_type = "memory";
> > reg = <0x0 0x0 0x0 0x40000000>;
> > };
> >
> > reserved-memory {
> > #address-cells = <2>;
> > #size-cells = <2>;
> > ranges;
> >
> > mcu_reserved: mcu_reserved@...ff000 {
> > no-map;
> > reg = <0x0 0x06dff000 0x0 0x00001000>, /* MCU mailbox buffer */
> > <0x0 0x05e00000 0x0 0x00100000>, /* MCU firmware buffer */
> > <0x0 0x0740f000 0x0 0x00001000>; /* MCU firmware section */
> > };
> > };
> >
> > [...]
> >
> > mailbox: mailbox@...10000 {
> > #mbox-cells = <1>;
> > compatible = "hisilicon,hi6220-mbox";
> > reg = <0x0 0xf7510000 0x0 0x1000>; /* IPC_S */
> > memory-region = <&mcu_reserved>; /* Mailbox buffer */
> > interrupts = <GIC_SPI 94 IRQ_TYPE_LEVEL_HIGH>;
> > };
>
> I prefer the second one. From my view, memory node should only describe
> the hardware information of memory.
Yes, option 2 will be more simple for memory node.
But option 2 also will introduce complexity for mailbox node, due mailbox
driver need use property "reg" and "memory-region" to sepeately depict
the regions for mailbox's ipc and slots. If later mailbox is designed to
use SRAM for both ipc and slots, then it will no matter with DDR anymore,
in this case option 1 will easily switch to support it.
Another question is a general question: for Linux kernel, which is the
best method to reserve memory regions? According to previous discussion,
we can use /memory/ node or /reseved-memory/ node to reserve memory
regions.
when review Juno's dts, i also see there have reserved 16MB DDR for secure
world. If so, looks like /reserved-memory/ node is unnecessary. if have some
specific scenarios will we use reserved-memory node to help reserve memory
regions?
Thanks,
Leo Yan
--
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