From: "Huang, Tao" <huangtao-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
To: "Paweł Jarosz"
<paweljarosz3691-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH] ARM: dts: rockchip: Reserve unusable memory region on rk3066
Date: Wed, 5 Oct 2016 10:27:15 +0800 [thread overview]
Message-ID: <6239b970-09d3-f7ee-e6f5-c019eaedb725@rock-chips.com> (raw)
In-Reply-To: <20161001140939.GA31220@vaio-ubuntu>
Hi, Paweł:
On 2016年10月01日 22:09, =?UTF-8?q?Pawe=C5=82=20Jarosz?= wrote:
> For some reason accessing memory region above 0xfe000000 freezes
> system on rk3066. There is similiar bug on later rockchip soc (rk3288)
RK3066 only support 2GB memory from 0x60000000 to 0xE0000000, can not access
above 0xfe000000. I think you mean 0x9F000000?
> solved same way.
>
> Signed-off-by: Paweł Jarosz <paweljarosz3691@gmail.com>
> ---
> arch/arm/boot/dts/rk3066a.dtsi | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
>
> diff --git a/arch/arm/boot/dts/rk3066a.dtsi b/arch/arm/boot/dts/rk3066a.dtsi
> index 0d0dae3..44c8956 100644
> --- a/arch/arm/boot/dts/rk3066a.dtsi
> +++ b/arch/arm/boot/dts/rk3066a.dtsi
> @@ -93,6 +93,19 @@
> };
> };
>
> + reserved-memory {
> + #address-cells = <1>;
> + #size-cells = <1>;
> + ranges;
> + /*
> + * The rk3066 cannot use the memory area above 0x9F000000
> + * for some unknown reason.
> + */
I don't remember RK3066 has such limit. I will double check with our IC
design team.
Do you know which master can not access this memory area
[0x9F000000~0xA0000000)?
> + unusable@9F000000 {
> + reg = <0x9F000000 0x1000000>;
> + };
> + };
> +
> i2s0: i2s@10118000 {
> compatible = "rockchip,rk3066-i2s";
> reg = <0x10118000 0x2000>;
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2016-10-05 2:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-01 14:09 [PATCH] ARM: dts: rockchip: Reserve unusable memory region on rk3066 =?UTF-8?q?Pawe=C5=82=20Jarosz?=
2016-10-01 18:17 ` Mark Rutland
2016-10-01 19:18 ` Heiko Stuebner
2016-10-01 19:59 ` Paweł Jarosz
2016-10-03 10:20 ` Mark Rutland
2016-10-03 10:54 ` Heiko Stuebner
2016-10-04 11:56 ` Paweł Jarosz
[not found] ` <81d1fb8b-ee0e-35a7-77db-5e15c3f46449-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-10-04 18:56 ` Heiko Stübner
2016-10-05 2:27 ` Huang, Tao [this message]
[not found] ` <6239b970-09d3-f7ee-e6f5-c019eaedb725-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-10-05 6:09 ` Paweł Jarosz
[not found] ` <f8aba48d-6c69-b246-4cb2-48a2770c80e4-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-10-10 7:18 ` Huang, Tao
[not found] ` <67831fd0-76af-a793-0b2f-958e45633fe8-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-10-10 9:11 ` Paweł Jarosz
2016-10-13 7:12 ` Huang, Tao
[not found] ` <e3746f9a-084e-163e-a412-1a1fc66926d5-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-10-13 8:55 ` Paweł Jarosz
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=6239b970-09d3-f7ee-e6f5-c019eaedb725@rock-chips.com \
--to=huangtao-tnx95d0mmh7dzftrwevzcw@public.gmane.org \
--cc=heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=paweljarosz3691-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox