From: Shawn Lin <shawn.lin@rock-chips.com>
To: Heiko Stuebner <heiko@sntech.de>
Cc: shawn.lin@rock-chips.com, mark.rutland@arm.com,
devicetree@vger.kernel.org, Randy Li <ayaka@soulik.info>,
linux@armlinux.org.uk, linux-kernel@vger.kernel.org,
linux-rockchip@lists.infradead.org, robh+dt@kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: dts: add rk3288-firefly-reload
Date: Mon, 8 Aug 2016 10:29:52 +0800 [thread overview]
Message-ID: <bd51b3c3-b312-babb-b57d-7e6e5a8ee948@rock-chips.com> (raw)
In-Reply-To: <1815189.oGy6GHMbyM@phil>
在 2016/8/7 22:44, Heiko Stuebner 写道:
> Hi Shawn,
>
> Am Sonntag, 7. August 2016, 11:40:21 schrieb Shawn Lin:
>> On 2016/7/19 3:46, Heiko Stübner wrote:
>>> Am Montag, 18. Juli 2016, 23:32:32 schrieb Randy Li:
>>>> The Firefly RK3288 Reload is a combination Firefly rk3288 core board
>>>> with the Reload baseboard. Add a dtsi for the Firefly rk3288 core
>>>> which can be included into the dts for the various baseboards
>>>> in the future and dts for Reload base board.
>>>>
>>>> Currently supported are serial console, wired networking, eMMC and
>>>> SD storage, SPFIF, IR receiver, LEDs, SDIO wifi and USB. But only
>>>> the OTG could work on the host mode now, the other USB host can't
>>>> work now, additional patches are required.
>>>>
>>>> Signed-off-by: Randy Li <ayaka@soulik.info>
>>>> Acked-by: Rob Herring <robh@kernel.org>
>>>
>>> applied [0], after some minor reordering - please double check.
>>>
>>> Also, while the branch is named 4.8 this will only go into 4.9, as the
>>> merge- window supposedly opens on the weekend.
>>
>> Sorry for the noise here:), but I find there is some mmc stuff
>> which confuse me. Maybe Randy could elaborate more?
>>
>> Your sdmmc claims to support UHS-I mode like sd-uhs-sdr104, etc, which
>> will ask dw_mmc to switch vqmmc from 3V3 to 1V8 after sending CMD11.
>>
>> But the vqmmc is vccio_sd which is fixed as 3V3? :)
>
> so far we have only been able to achieve UHS speeds on devices based on the
> rk808 pmic (I had sucess on veyron and popmetal). The act8846-based boards
> seem to have some issue when trying to do the switch to 1.8V, resulting in
> mmc errors and the mmc-core switching back to 3.3V.
Interesting.... I will have a look at it this weekend with Randy face 2
face....
>
> I think this might be caused by a bug in the act8846 driver or some dts
> mistake. But so far nobody had the time and enthusiasm to investigate :-)
>
>
> Heiko
>
> _______________________________________________
> Linux-rockchip mailing list
> Linux-rockchip@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-rockchip
>
--
Best Regards
Shawn Lin
next prev parent reply other threads:[~2016-08-08 2:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1549971.ctkvOGm2xW@diego>
2016-07-18 15:32 ` [PATCH v2] " Randy Li
2016-07-18 15:32 ` [PATCH] " Randy Li
2016-07-18 19:46 ` Heiko Stübner
2016-08-07 3:40 ` Shawn Lin
2016-08-07 14:44 ` Heiko Stuebner
2016-08-08 2:29 ` Shawn Lin [this message]
2016-08-09 9:28 ` 陈豪
2016-08-09 10:02 ` 陈豪
2016-08-09 10:06 ` Randy Li
2016-08-09 10:58 ` Heiko Stübner
2016-08-10 1:12 ` Randy Li
2016-08-14 11:27 ` [PATCH 0/2] ARM: dts: rockchip: correct the regulators in firefly reload Randy Li
2016-08-14 11:27 ` [PATCH 1/2] ARM: dts: rockchip: remove excess sd properties for " Randy Li
2016-08-14 12:30 ` Heiko Stuebner
2016-08-14 12:38 ` ayaka
2016-08-17 14:10 ` Heiko Stübner
2016-08-17 17:03 ` [PATCH 0/2 v2] ARM: dts: rockchip: correct the regulators in " Randy Li
2016-08-17 17:03 ` [PATCH 1/2] ARM: dts: rockchip: remove excess sd properties for " Randy Li
2016-08-18 13:35 ` Heiko Stübner
2016-08-18 14:20 ` ayaka
2016-08-17 17:03 ` [PATCH 2/2] ARM: dts: rockchip: add missing regulators for firefly reload board Randy Li
2016-08-18 16:47 ` Heiko Stübner
2016-08-14 11:27 ` Randy Li
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=bd51b3c3-b312-babb-b57d-7e6e5a8ee948@rock-chips.com \
--to=shawn.lin@rock-chips.com \
--cc=ayaka@soulik.info \
--cc=devicetree@vger.kernel.org \
--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®