From: Arnd Bergmann <arnd@arndb.de>
To: Doug Anderson <dianders@chromium.org>
Cc: Heiko Stuebner <heiko@sntech.de>,
Seungwon Jeon <tgih.jun@samsung.com>,
Jaehoon Chung <jh80.chung@samsung.com>,
Chris Ball <chris@printf.net>,
Ulf Hansson <ulf.hansson@linaro.org>,
Addy Ke <addy.ke@rock-chips.com>,
Kever Yang <kever.yang@rock-chips.com>,
Sonny Rao <sonnyrao@chromium.org>,
linux-arm-kernel@lists.infradead.org, linux-mmc@vger.kernel.org,
mark.rutland@arm.com, devicetree@vger.kernel.org,
linux@arm.linux.org.uk, pawel.moll@arm.com,
ijc+devicetree@hellion.org.uk, linux-kernel@vger.kernel.org,
robh+dt@kernel.org, galak@codeaurora.org
Subject: Re: [PATCH 0/5] Add eMMC and SD card support for rk3288-evb
Date: Tue, 29 Jul 2014 22:42:51 +0200 [thread overview]
Message-ID: <2167758.ZBctteP0VZ@wuerfel> (raw)
In-Reply-To: <1406665916-23396-1-git-send-email-dianders@chromium.org>
On Tuesday 29 July 2014 13:31:51 Doug Anderson wrote:
> This series adds basic eMMC and SD card support for the rk3288-evb
> board based on Addy's posted dw_mmc patch from:
> https://patchwork.kernel.org/patch/4520631/
>
> The series is a little tricky because:
> * Addy's patch has a bug w/ DDR50 (see my response there), so I've
> posted the original support without DDR50 and then a fix (that could
> be squashed) enabling DDR50.
> * Jaehoon has some outstanding patches to remove the slot node. Since
> those haven't landed yet, I've posted my original patch with the
> slot node and then some future patches that can land with Jaehoon's
> patches.
>
> Note that we don't have regulators specified yet (no regulator driver
> for rk808-based board). We also don't yet support UHS modes (which
> require regulator support plus dw_mmc driver support for tuning).
> Those features can come later.
Looks good to me,
Acked-by: Arnd Bergmann <arnd@arndb.de>
I wonder whether something can be done to generalize the tuning
support. Is this just about the clock phase, or something else?
Arnd
prev parent reply other threads:[~2014-07-29 20:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-29 20:31 [PATCH 0/5] Add eMMC and SD card support for rk3288-evb Doug Anderson
[not found] ` <1406665916-23396-1-git-send-email-dianders-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2014-07-29 20:31 ` [PATCH 1/5] ARM: dts: Add emmc and sdmmc to the rk3288 device tree Doug Anderson
2014-07-29 20:31 ` [PATCH 2/5] ARM: dts: Enable emmc and sdmmc on the rk3288-evb boards Doug Anderson
2014-07-29 20:31 ` [PATCH 3/5] ARM: dts: Enable DDR50 mode on the eMMC Doug Anderson
2014-07-29 20:31 ` [PATCH 4/5] ARM: dts: Take the mmc slot node out of rk3288-evb Doug Anderson
2014-07-29 20:31 ` [PATCH 5/5] ARM: dts: mmc slot node gone on rk3288 => no more address / size cells Doug Anderson
2014-07-29 20:42 ` Arnd Bergmann [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=2167758.ZBctteP0VZ@wuerfel \
--to=arnd@arndb.de \
--cc=addy.ke@rock-chips.com \
--cc=chris@printf.net \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=galak@codeaurora.org \
--cc=heiko@sntech.de \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jh80.chung@samsung.com \
--cc=kever.yang@rock-chips.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=sonnyrao@chromium.org \
--cc=tgih.jun@samsung.com \
--cc=ulf.hansson@linaro.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