From: sudeep.holla@arm.com (Sudeep Holla)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v1 3/3] arm64: dts: add Hi6220 mailbox node
Date: Tue, 25 Aug 2015 12:36:12 +0100 [thread overview]
Message-ID: <55DC532C.3020005@arm.com> (raw)
In-Reply-To: <1439977055-1747-4-git-send-email-leo.yan@linaro.org>
On 19/08/15 10:37, Leo Yan wrote:
> On Hi6220, below memory regions in DDR have specific purpose:
>
> 0x05e0,0000 - 0x05ef,ffff: For MCU firmware using at runtime;
> 0x0740,f000 - 0x0740,ffff: For MCU firmware's section;
> 0x06df,f000 - 0x06df,ffff: For mailbox message data.
>
Unless I am reading the DTS file completely wrong, I don't think the
above memory regions are in DDR as per the memory node.
> This patch reserves these memory regions and add device node for
> mailbox in dts.
>
> Signed-off-by: Leo Yan <leo.yan@linaro.org>
> ---
> arch/arm64/boot/dts/hisilicon/hi6220-hikey.dts | 20 +++++++++++++++++---
> arch/arm64/boot/dts/hisilicon/hi6220.dtsi | 8 ++++++++
> 2 files changed, 25 insertions(+), 3 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/hisilicon/hi6220-hikey.dts b/arch/arm64/boot/dts/hisilicon/hi6220-hikey.dts
> index e36a539..d5470d3 100644
> --- a/arch/arm64/boot/dts/hisilicon/hi6220-hikey.dts
> +++ b/arch/arm64/boot/dts/hisilicon/hi6220-hikey.dts
> @@ -7,9 +7,6 @@
>
> /dts-v1/;
>
> -/*Reserved 1MB memory for MCU*/
> -/memreserve/ 0x05e00000 0x00100000;
> -
> #include "hi6220.dtsi"
>
> / {
> @@ -28,4 +25,21 @@
> device_type = "memory";
> reg = <0x0 0x0 0x0 0x40000000>;
> };
I have no access to the spec, but I read this as 1GB RAM @0x0
Unless this entry is completely wrong, what your commit log claims is
incorrect. If this entry is wrong I wonder how is it booting with this
DT then.
> +
> + reserved-memory {
> + #address-cells = <2>;
> + #size-cells = <2>;
> + ranges;
> +
> + mcu-buf at 05e00000 {
> + no-map;
> + reg = <0x0 0x05e00000 0x0 0x00100000>, /* MCU firmware buffer */
> + <0x0 0x0740f000 0x0 0x00001000>; /* MCU firmware section */
So I don't see how can this be part of DDR ? Or at-least part of DDR
that's mapped by kernel ?
Regards,
Sudeep
WARNING: multiple messages have this Message-ID (diff)
From: Sudeep Holla <sudeep.holla-5wv7dgnIgG8@public.gmane.org>
To: Leo Yan <leo.yan-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
"guodong.xu-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org"
<guodong.xu-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
Jian Zhang <zhangjian001-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org>,
Zhenwei Wang
<Zhenwei.wang-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org>,
Haoju Mo <mohaoju-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org>,
Dan Zhao <dan.zhao-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org>,
"kongfei-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org"
<kongfei-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org>,
Guangyue Zeng
<zengguangyue-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org>
Cc: Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Pawel Moll <Pawel.Moll-5wv7dgnIgG8@public.gmane.org>,
Mark Rutland <Mark.Rutland-5wv7dgnIgG8@public.gmane.org>,
Ian Campbell
<ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org>,
Kumar Gala <galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>,
Catalin Marinas <Catalin.Marinas-5wv7dgnIgG8@public.gmane.org>,
Will Deacon <Will.Deacon-5wv7dgnIgG8@public.gmane.org>,
Jassi Brar
<jassisinghbrar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Bintian Wang
<bintian.wang-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>,
Haojian Zhuang
<haojian.zhuang-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
Yiping Xu <xuyiping-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org>,
Wei Xu <xuwei5-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org>,
Sudeep Holla <sudeep.holla-5wv7dgnIgG8@public.gmane.org>
Subject: Re: [PATCH v1 3/3] arm64: dts: add Hi6220 mailbox node
Date: Tue, 25 Aug 2015 12:36:12 +0100 [thread overview]
Message-ID: <55DC532C.3020005@arm.com> (raw)
In-Reply-To: <1439977055-1747-4-git-send-email-leo.yan-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
On 19/08/15 10:37, Leo Yan wrote:
> On Hi6220, below memory regions in DDR have specific purpose:
>
> 0x05e0,0000 - 0x05ef,ffff: For MCU firmware using at runtime;
> 0x0740,f000 - 0x0740,ffff: For MCU firmware's section;
> 0x06df,f000 - 0x06df,ffff: For mailbox message data.
>
Unless I am reading the DTS file completely wrong, I don't think the
above memory regions are in DDR as per the memory node.
> This patch reserves these memory regions and add device node for
> mailbox in dts.
>
> Signed-off-by: Leo Yan <leo.yan-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
> ---
> arch/arm64/boot/dts/hisilicon/hi6220-hikey.dts | 20 +++++++++++++++++---
> arch/arm64/boot/dts/hisilicon/hi6220.dtsi | 8 ++++++++
> 2 files changed, 25 insertions(+), 3 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/hisilicon/hi6220-hikey.dts b/arch/arm64/boot/dts/hisilicon/hi6220-hikey.dts
> index e36a539..d5470d3 100644
> --- a/arch/arm64/boot/dts/hisilicon/hi6220-hikey.dts
> +++ b/arch/arm64/boot/dts/hisilicon/hi6220-hikey.dts
> @@ -7,9 +7,6 @@
>
> /dts-v1/;
>
> -/*Reserved 1MB memory for MCU*/
> -/memreserve/ 0x05e00000 0x00100000;
> -
> #include "hi6220.dtsi"
>
> / {
> @@ -28,4 +25,21 @@
> device_type = "memory";
> reg = <0x0 0x0 0x0 0x40000000>;
> };
I have no access to the spec, but I read this as 1GB RAM @0x0
Unless this entry is completely wrong, what your commit log claims is
incorrect. If this entry is wrong I wonder how is it booting with this
DT then.
> +
> + reserved-memory {
> + #address-cells = <2>;
> + #size-cells = <2>;
> + ranges;
> +
> + mcu-buf@05e00000 {
> + no-map;
> + reg = <0x0 0x05e00000 0x0 0x00100000>, /* MCU firmware buffer */
> + <0x0 0x0740f000 0x0 0x00001000>; /* MCU firmware section */
So I don't see how can this be part of DDR ? Or at-least part of DDR
that's mapped by kernel ?
Regards,
Sudeep
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Sudeep Holla <sudeep.holla@arm.com>
To: Leo Yan <leo.yan@linaro.org>,
"devicetree@vger.kernel.org" <devicetree@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>,
"guodong.xu@linaro.org" <guodong.xu@linaro.org>,
Jian Zhang <zhangjian001@hisilicon.com>,
Zhenwei Wang <Zhenwei.wang@hisilicon.com>,
Haoju Mo <mohaoju@hisilicon.com>,
Dan Zhao <dan.zhao@hisilicon.com>,
"kongfei@hisilicon.com" <kongfei@hisilicon.com>,
Guangyue Zeng <zengguangyue@hisilicon.com>
Cc: Rob Herring <robh+dt@kernel.org>, Pawel Moll <Pawel.Moll@arm.com>,
Mark Rutland <Mark.Rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Catalin Marinas <Catalin.Marinas@arm.com>,
Will Deacon <Will.Deacon@arm.com>,
Jassi Brar <jassisinghbrar@gmail.com>,
Bintian Wang <bintian.wang@huawei.com>,
Haojian Zhuang <haojian.zhuang@linaro.org>,
Yiping Xu <xuyiping@hisilicon.com>, Wei Xu <xuwei5@hisilicon.com>,
Sudeep Holla <sudeep.holla@arm.com>
Subject: Re: [PATCH v1 3/3] arm64: dts: add Hi6220 mailbox node
Date: Tue, 25 Aug 2015 12:36:12 +0100 [thread overview]
Message-ID: <55DC532C.3020005@arm.com> (raw)
In-Reply-To: <1439977055-1747-4-git-send-email-leo.yan@linaro.org>
On 19/08/15 10:37, Leo Yan wrote:
> On Hi6220, below memory regions in DDR have specific purpose:
>
> 0x05e0,0000 - 0x05ef,ffff: For MCU firmware using at runtime;
> 0x0740,f000 - 0x0740,ffff: For MCU firmware's section;
> 0x06df,f000 - 0x06df,ffff: For mailbox message data.
>
Unless I am reading the DTS file completely wrong, I don't think the
above memory regions are in DDR as per the memory node.
> This patch reserves these memory regions and add device node for
> mailbox in dts.
>
> Signed-off-by: Leo Yan <leo.yan@linaro.org>
> ---
> arch/arm64/boot/dts/hisilicon/hi6220-hikey.dts | 20 +++++++++++++++++---
> arch/arm64/boot/dts/hisilicon/hi6220.dtsi | 8 ++++++++
> 2 files changed, 25 insertions(+), 3 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/hisilicon/hi6220-hikey.dts b/arch/arm64/boot/dts/hisilicon/hi6220-hikey.dts
> index e36a539..d5470d3 100644
> --- a/arch/arm64/boot/dts/hisilicon/hi6220-hikey.dts
> +++ b/arch/arm64/boot/dts/hisilicon/hi6220-hikey.dts
> @@ -7,9 +7,6 @@
>
> /dts-v1/;
>
> -/*Reserved 1MB memory for MCU*/
> -/memreserve/ 0x05e00000 0x00100000;
> -
> #include "hi6220.dtsi"
>
> / {
> @@ -28,4 +25,21 @@
> device_type = "memory";
> reg = <0x0 0x0 0x0 0x40000000>;
> };
I have no access to the spec, but I read this as 1GB RAM @0x0
Unless this entry is completely wrong, what your commit log claims is
incorrect. If this entry is wrong I wonder how is it booting with this
DT then.
> +
> + reserved-memory {
> + #address-cells = <2>;
> + #size-cells = <2>;
> + ranges;
> +
> + mcu-buf@05e00000 {
> + no-map;
> + reg = <0x0 0x05e00000 0x0 0x00100000>, /* MCU firmware buffer */
> + <0x0 0x0740f000 0x0 0x00001000>; /* MCU firmware section */
So I don't see how can this be part of DDR ? Or at-least part of DDR
that's mapped by kernel ?
Regards,
Sudeep
next prev parent reply other threads:[~2015-08-25 11:36 UTC|newest]
Thread overview: 108+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-19 9:37 [PATCH v1 0/3] mailbox: hisilicon: add Hi6220 mailbox driver Leo Yan
2015-08-19 9:37 ` Leo Yan
2015-08-19 9:37 ` Leo Yan
2015-08-19 9:37 ` [PATCH v1 1/3] dt-bindings: mailbox: Document " Leo Yan
2015-08-19 9:37 ` Leo Yan
2015-08-25 11:17 ` Sudeep Holla
2015-08-25 11:17 ` Sudeep Holla
2015-08-25 11:17 ` Sudeep Holla
2015-08-25 13:01 ` Leo Yan
2015-08-25 13:01 ` Leo Yan
2015-08-25 13:01 ` Leo Yan
2015-08-19 9:37 ` [PATCH v1 2/3] mailbox: Hi6220: add " Leo Yan
2015-08-19 9:37 ` Leo Yan
2015-08-19 9:37 ` [PATCH v1 3/3] arm64: dts: add Hi6220 mailbox node Leo Yan
2015-08-19 9:37 ` Leo Yan
2015-08-21 18:40 ` Mark Rutland
2015-08-21 18:40 ` Mark Rutland
2015-08-21 18:40 ` Mark Rutland
2015-08-22 13:30 ` Leo Yan
2015-08-22 13:30 ` Leo Yan
2015-08-22 13:30 ` Leo Yan
2015-08-24 3:27 ` Leo Yan
2015-08-24 3:27 ` Leo Yan
2015-08-24 3:27 ` Leo Yan
2015-08-24 9:18 ` Leo Yan
2015-08-24 9:18 ` Leo Yan
2015-08-24 9:18 ` Leo Yan
2015-08-24 9:51 ` Mark Rutland
2015-08-24 9:51 ` Mark Rutland
2015-08-24 9:51 ` Mark Rutland
2015-08-24 10:19 ` Haojian Zhuang
2015-08-24 10:19 ` Haojian Zhuang
2015-08-24 10:19 ` Haojian Zhuang
2015-08-24 11:49 ` Leif Lindholm
2015-08-24 11:49 ` Leif Lindholm
2015-08-24 11:49 ` Leif Lindholm
2015-08-25 8:13 ` Haojian Zhuang
2015-08-25 8:13 ` Haojian Zhuang
2015-08-25 8:13 ` Haojian Zhuang
2015-08-25 9:46 ` Leif Lindholm
2015-08-25 9:46 ` Leif Lindholm
2015-08-25 9:46 ` Leif Lindholm
2015-08-25 10:15 ` Haojian Zhuang
2015-08-25 10:15 ` Haojian Zhuang
2015-08-25 10:15 ` Haojian Zhuang
2015-08-25 10:40 ` Leif Lindholm
2015-08-25 10:40 ` Leif Lindholm
2015-08-25 10:40 ` Leif Lindholm
2015-08-25 10:42 ` Mark Rutland
2015-08-25 10:42 ` Mark Rutland
2015-08-25 10:42 ` Mark Rutland
2015-08-25 13:43 ` Haojian Zhuang
2015-08-25 13:43 ` Haojian Zhuang
2015-08-25 13:43 ` Haojian Zhuang
2015-08-25 14:24 ` Leif Lindholm
2015-08-25 14:24 ` Leif Lindholm
2015-08-25 14:24 ` Leif Lindholm
2015-08-25 14:51 ` Ard Biesheuvel
2015-08-25 14:51 ` Ard Biesheuvel
2015-08-25 14:51 ` Ard Biesheuvel
2015-08-25 15:37 ` Leif Lindholm
2015-08-25 15:37 ` Leif Lindholm
2015-08-25 15:37 ` Leif Lindholm
2015-08-25 15:45 ` Ard Biesheuvel
2015-08-25 15:45 ` Ard Biesheuvel
2015-08-25 15:45 ` Ard Biesheuvel
2015-08-26 2:41 ` Haojian Zhuang
2015-08-26 2:41 ` Haojian Zhuang
2015-08-26 2:41 ` Haojian Zhuang
2015-08-25 16:00 ` Leo Yan
2015-08-25 16:00 ` Leo Yan
2015-08-25 16:00 ` Leo Yan
2015-08-26 1:25 ` Haojian Zhuang
2015-08-26 1:25 ` Haojian Zhuang
2015-08-26 1:25 ` Haojian Zhuang
2015-08-26 6:59 ` Leo Yan
2015-08-26 6:59 ` Leo Yan
2015-08-26 6:59 ` Leo Yan
2015-08-27 16:31 ` Mark Rutland
2015-08-27 16:31 ` Mark Rutland
2015-08-27 16:31 ` Mark Rutland
2015-08-28 6:37 ` Leo Yan
2015-08-28 6:37 ` Leo Yan
2015-08-28 6:37 ` Leo Yan
2015-08-27 15:54 ` Daniel Thompson
2015-08-27 15:54 ` Daniel Thompson
2015-08-27 15:54 ` Daniel Thompson
2015-08-27 16:46 ` Mark Rutland
2015-08-27 16:46 ` Mark Rutland
2015-08-27 16:46 ` Mark Rutland
2015-08-24 12:48 ` Mark Rutland
2015-08-24 12:48 ` Mark Rutland
2015-08-24 12:48 ` Mark Rutland
2015-08-25 8:04 ` Haojian Zhuang
2015-08-25 8:04 ` Haojian Zhuang
2015-08-25 8:04 ` Haojian Zhuang
2015-08-25 11:09 ` Mark Rutland
2015-08-25 11:09 ` Mark Rutland
2015-08-25 11:09 ` Mark Rutland
2015-08-25 11:36 ` Sudeep Holla [this message]
2015-08-25 11:36 ` Sudeep Holla
2015-08-25 11:36 ` Sudeep Holla
2015-08-25 14:04 ` Leo Yan
2015-08-25 14:04 ` Leo Yan
2015-08-25 14:04 ` Leo Yan
2015-08-25 14:13 ` Sudeep Holla
2015-08-25 14:13 ` Sudeep Holla
2015-08-25 14:13 ` Sudeep Holla
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=55DC532C.3020005@arm.com \
--to=sudeep.holla@arm.com \
--cc=linux-arm-kernel@lists.infradead.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.