From: Stephen Warren <swarren@wwwdotorg.org>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: linux-sh@vger.kernel.org, linux-mmc@vger.kernel.org,
Magnus Damm <magnus.damm@gmail.com>, Chris Ball <cjb@laptop.org>,
devicetree@vger.kernel.org, Simon Horman <horms@verge.net.au>,
Ian Campbell <ian.campbell@citrix.com>,
Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <Mark.Rutland@arm.com>,
Rob Herring <rob.herring@calxeda.com>
Subject: Re: [PATCH 1/2] mmc: add Device Tree properties for UHS modes
Date: Fri, 26 Jul 2013 11:10:58 -0600 [thread overview]
Message-ID: <51F2ADA2.2030503@wwwdotorg.org> (raw)
In-Reply-To: <Pine.LNX.4.64.1307261747210.22137@axis700.grange>
On 07/26/2013 09:51 AM, Guennadi Liakhovetski wrote:
> Add DT properties for UHS SDR12, SDR25, SDR50, SDR104 and DDR50 modes and
> for supported by the host in DDR mode VccQ values. Adding them to DT will
> automatically enable respective MMC host capabilities.
> diff --git a/Documentation/devicetree/bindings/mmc/mmc.txt b/Documentation/devicetree/bindings/mmc/mmc.txt
> +- uhs-sdr12: the host supports UHS SDR12 mode
> +- uhs-sdr25: the host supports UHS SDR25 mode
> +- uhs-sdr50: the host supports UHS SDR50 mode
> +- uhs-sdr104: the host supports UHS SDR104 mode
> +- uhs-ddr50: the host supports UHS DDR50 mode
> +- ddr-1v2: the host can support DDR, using 1.2V VccQ
> +- ddr-1v8: the host can support DDR, using 1.8V VccQ
Surely the driver for the host controller already knows this, so there's
no need to represent it in DT?
next prev parent reply other threads:[~2013-07-26 17:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-26 15:51 [PATCH 1/2] mmc: add Device Tree properties for UHS modes Guennadi Liakhovetski
2013-07-26 15:51 ` [PATCH/RFC 2/2] ARM: shmobile: kzm9g: support DDR50 mode with 1.8V VccQ on MMCIF Guennadi Liakhovetski
2013-07-30 2:18 ` Simon Horman
2013-07-26 17:10 ` Stephen Warren [this message]
2013-07-26 20:23 ` [PATCH 1/2] mmc: add Device Tree properties for UHS modes Guennadi Liakhovetski
2013-07-26 21:36 ` Stephen Warren
2013-07-29 6:20 ` Guennadi Liakhovetski
2013-07-29 7:18 ` Guennadi Liakhovetski
2013-07-29 10:50 ` Pawel Moll
2013-07-29 11:27 ` Guennadi Liakhovetski
2013-07-29 11:42 ` Pawel Moll
2013-07-29 12:05 ` Guennadi Liakhovetski
2013-07-29 13:07 ` Pawel Moll
2013-07-29 13:30 ` Guennadi Liakhovetski
2013-07-29 13:37 ` Pawel Moll
2013-07-29 17:21 ` Stephen Warren
2013-07-29 13:39 ` Rob Herring
2013-07-29 14:40 ` Guennadi Liakhovetski
2013-07-29 17:28 ` Stephen Warren
2013-07-29 10:57 ` Pawel Moll
2013-07-29 11:10 ` Guennadi Liakhovetski
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=51F2ADA2.2030503@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=Mark.Rutland@arm.com \
--cc=cjb@laptop.org \
--cc=devicetree@vger.kernel.org \
--cc=g.liakhovetski@gmx.de \
--cc=horms@verge.net.au \
--cc=ian.campbell@citrix.com \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=pawel.moll@arm.com \
--cc=rob.herring@calxeda.com \
/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;
as well as URLs for NNTP newsgroup(s).