From: Shawn Lin <shawn.lin@rock-chips.com>
To: Eddie Cai <eddie.cai.linux@gmail.com>,
heiko@sntech.de, robh+dt@kernel.org, mark.rutland@arm.com,
linux@armlinux.org.uk
Cc: shawn.lin@rock-chips.com, linux-rockchip@lists.infradead.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: rockchip:remove hs200 support for firefly reload
Date: Wed, 24 May 2017 16:00:53 +0800 [thread overview]
Message-ID: <65c7a442-4b2e-65e4-ea5e-0a723c257397@rock-chips.com> (raw)
In-Reply-To: <1495612242-28873-1-git-send-email-eddie.cai.linux@gmail.com>
Hi,
On 2017/5/24 15:50, Eddie Cai wrote:
> due to layout limitation. not all of the reload board can support hs200.
> so remove hs200 support to make all board can boot up.
You now also remove DDR52, so all reload boards run at high speed mode?
I'm curious about what was the layout limitation that mmc tuning
process could never help?
>
> Signed-off-by: Eddie Cai <eddie.cai.linux@gmail.com>
> ---
> arch/arm/boot/dts/rk3288-firefly-reload-core.dtsi | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/arch/arm/boot/dts/rk3288-firefly-reload-core.dtsi b/arch/arm/boot/dts/rk3288-firefly-reload-core.dtsi
> index 4cfa109..56ac1e6f 100644
> --- a/arch/arm/boot/dts/rk3288-firefly-reload-core.dtsi
> +++ b/arch/arm/boot/dts/rk3288-firefly-reload-core.dtsi
> @@ -75,8 +75,6 @@
> bus-width = <8>;
> cap-mmc-highspeed;
> disable-wp;
> - mmc-ddr-1_8v;
> - mmc-hs200-1_8v;
> non-removable;
> num-slots = <1>;
> pinctrl-names = "default";
>
next prev parent reply other threads:[~2017-05-24 8:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-24 7:50 Eddie Cai
2017-05-24 8:00 ` Shawn Lin [this message]
2017-05-24 8:55 ` Eddie Cai
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=65c7a442-4b2e-65e4-ea5e-0a723c257397@rock-chips.com \
--to=shawn.lin@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=eddie.cai.linux@gmail.com \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.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
all inboxes | Powered by JetHome®