From: Dinh Nguyen <dinguyen@altera.com>
To: Jaehoon Chung <jh80.chung@samsung.com>
Cc: linux-mmc@vger.kernel.org, chris@printf.net,
ulf.hansson@linaro.org, tgih.jun@samsung.com,
zhangfei.gao@linaro.org
Subject: Re: [PATCH 2/5] mmc: dw_mmc: remove the "supports-highspeed" property.
Date: Wed, 14 May 2014 15:17:08 -0500 [thread overview]
Message-ID: <1400098628.23670.3.camel@linux-builds1> (raw)
In-Reply-To: <5372F740.3020401@samsung.com>
On Wed, 2014-05-14 at 13:55 +0900, Jaehoon Chung wrote:
> Hi, Dinh.
>
> On 05/13/2014 12:48 AM, Dinh Nguyen wrote:
> > On Mon, 2014-05-12 at 20:14 +0900, Jaehoon Chung wrote:
> >> Remove the "support-highspeed" property in dw-mmc.
> >> "support-highspeed" property can be replaced to "cap-sd/mmc-highspeed".
> >>
> >> Signed-off-by: Jaehoon Chung <jh80.chung@samsung.com>
> >> ---
> >> .../devicetree/bindings/mmc/exynos-dw-mshc.txt | 1 -
> >> .../devicetree/bindings/mmc/k3-dw-mshc.txt | 1 -
> >> .../devicetree/bindings/mmc/synopsys-dw-mshc.txt | 3 ---
> >> arch/arm/boot/dts/exynos4412-odroidx.dts | 2 +-
> >> arch/arm/boot/dts/exynos4412-origen.dts | 2 +-
> >> arch/arm/boot/dts/exynos4412-trats2.dts | 2 +-
> >> arch/arm/boot/dts/exynos5250-arndale.dts | 4 ++--
> >> arch/arm/boot/dts/exynos5250-cros-common.dtsi | 6 +++---
> >> arch/arm/boot/dts/exynos5250-smdk5250.dts | 4 ++--
> >> arch/arm/boot/dts/exynos5420-arndale-octa.dts | 4 ++--
> >> arch/arm/boot/dts/exynos5420-smdk5420.dts | 4 ++--
> >> arch/arm/boot/dts/socfpga_arria5.dtsi | 3 ++-
> >> arch/arm/boot/dts/socfpga_cyclone5.dtsi | 3 ++-
> >> arch/arm/boot/dts/socfpga_vt.dts | 3 ++-
> >> drivers/mmc/host/dw_mmc.c | 3 ---
> >> 15 files changed, 20 insertions(+), 25 deletions(-)
> >>
> >
> > Should exynos5260-xyref5260.dts and exynos5420-peach-pit.dts also get
> > updated?
>
> I didn't find them..? Is it included into dts folder.
Ah sorry, I tested this patch series against linux-next, which has these
2 patches.
81141a027c5d ARM: dts: add dts files for exynos5260-xyref5260 board
3528dd34b2d3 ARM: dts: Add exynos5420 peach-pit board support
Not sure if you want to fix those two boards up too, but just thought I
point them out to you.
Dinh
>
> Best Regards,
> Jaehoon Chung
> >
> > Dinh
> >
> >
>
next prev parent reply other threads:[~2014-05-14 20:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-12 11:14 [PATCH 0/5] mmc: dw_mmc: minor code cleanup Jaehoon Chung
2014-05-12 11:14 ` [PATCH 1/5] mmc: dw_mmc: fix the wrong condition checking Jaehoon Chung
2014-05-12 11:14 ` [PATCH 2/5] mmc: dw_mmc: remove the "supports-highspeed" property Jaehoon Chung
2014-05-12 15:48 ` Dinh Nguyen
2014-05-14 4:55 ` Jaehoon Chung
2014-05-14 20:17 ` Dinh Nguyen [this message]
2014-05-12 17:43 ` Dinh Nguyen
2014-05-14 4:55 ` Jaehoon Chung
2014-05-12 11:14 ` [PATCH 3/5] mmc: dw_mmc-exynos: add the MMC_CAP_ERASE by default Jaehoon Chung
2014-05-13 11:15 ` Seungwon Jeon
2014-05-13 12:27 ` Jaehoon Chung
2014-05-12 11:14 ` [PATCH 4/5] mmc: dw_mmc: add the specified capbilities2 of controller Jaehoon Chung
2014-05-12 11:14 ` [PATCH 5/5] mmc: dw_mmc: use the mmc regulator API into core.c Jaehoon Chung
2014-05-12 17:41 ` Dinh Nguyen
2014-05-14 4:55 ` Jaehoon Chung
2014-05-14 9:48 ` Yuvaraj Cd
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=1400098628.23670.3.camel@linux-builds1 \
--to=dinguyen@altera.com \
--cc=chris@printf.net \
--cc=jh80.chung@samsung.com \
--cc=linux-mmc@vger.kernel.org \
--cc=tgih.jun@samsung.com \
--cc=ulf.hansson@linaro.org \
--cc=zhangfei.gao@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