From: shawn.lin@rock-chips•com (Shawn Lin)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 2/2] ARM: dts: support Highspeed for rk3066a platform
Date: Sat, 12 Sep 2015 07:44:37 +0800 [thread overview]
Message-ID: <55F36765.2040703@rock-chips.com> (raw)
In-Reply-To: <25757012.mQz0HMffNZ@diego>
? 2015/9/12 6:45, Heiko St?bner ??:
> Hi Shawn,
>
> Am Freitag, 11. September 2015, 15:25:41 schrieb Shawn Lin:
>> Add cap-sd-highspeed and cap-mmc-highspeed for rk3066a
>> platform to make sd cards running faster.
>>
>> Signed-off-by: Shawn Lin <shawn.lin@rock-chips•com>
>> ---
>>
>> arch/arm/boot/dts/rk3066a.dtsi | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/arch/arm/boot/dts/rk3066a.dtsi b/arch/arm/boot/dts/rk3066a.dtsi
>> index 946f187..b50a785 100644
>> --- a/arch/arm/boot/dts/rk3066a.dtsi
>> +++ b/arch/arm/boot/dts/rk3066a.dtsi
>> @@ -595,6 +595,8 @@
>> &mmc0 {
>> pinctrl-names = "default";
>> pinctrl-0 = <&sd0_clk &sd0_cmd &sd0_cd &sd0_bus4>;
>> + cap-mmc-highspeed;
>> + cap-sd-highspeed;
>> };
>>
>
> Currently we're setting the dw_mmc capabilities in the individual board files
> and patch1 also correctly adds the cap to the radxarock file.
>
Thanks, Heiko. :)
Right, I was condering add caps in rk3066a for all boards which include
it or for each individual board. Unfortunately, I chose the wrong one.:(
Done in the v2.
> So I'd think we should stay with one scheme and probably add the rk3066 caps
> to the bqcurie2, marsboard and rayeager where applicable.
>
>
> Heiko
>
>
>
--
Best Regards
Shawn Lin
prev parent reply other threads:[~2015-09-11 23:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-11 7:24 [PATCH 1/2] ARM: dts: support Highspeed for rk3188-radxarock Shawn Lin
2015-09-11 7:25 ` [PATCH 2/2] ARM: dts: support Highspeed for rk3066a platform Shawn Lin
2015-09-11 22:45 ` Heiko Stübner
2015-09-11 23:44 ` Shawn Lin [this message]
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=55F36765.2040703@rock-chips.com \
--to=shawn.lin@rock-chips$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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