From: Otavio Salvador <otavio@ossystems.com.br>
To: Fabio Estevam <festevam@gmail.com>
Cc: ulf.hansson@linaro.org, aisheng.dong@freescale.com,
Kevin Lemoi <kevin.lemoi@savant.com>,
kernel@pengutronix.de, Russell King <linux@arm.linux.org.uk>,
chuanxiao.dong@intel.com, linux-mmc@vger.kernel.org,
Fabio Estevam <fabio.estevam@freescale.com>
Subject: Re: [PATCH v2] mmc: core: Do not set mmc voltage to 1.8V when 'no-1-8-v' is present
Date: Mon, 15 Jun 2015 08:44:35 -0300 [thread overview]
Message-ID: <CAP9ODKp5c9fq+og8pcYAK0LvZKQVj62e+-xa2seVM+dWTky+SA@mail.gmail.com> (raw)
In-Reply-To: <1434227067-9600-1-git-send-email-festevam@gmail.com>
On Sat, Jun 13, 2015 at 5:24 PM, Fabio Estevam <festevam@gmail.com> wrote:
> From: Fabio Estevam <fabio.estevam@freescale.com>
>
> Since commit 312449efd16bb06 ("mmc: core: Fix sequence for I/O voltage
> in DDR mode for eMMC") the mmc voltage is set to 1.8V inside
> mmc_select_hs_ddr(), even if 'no-1-8-v' property is present.
>
> This causes the following error on a mx6sl board with the 'no-1-8-v'
> property passed in the device tree:
>
> mmc0: power class selection to bus width 8 ddr 4 failed
> mmc0: error -110 whilst initialising MMC card
>
> Fix this problem by only setting the mmc voltage to 1.8V if the
> 'no-1-8-v' property is absent.
>
> Reported-by: Kevin Lemoi <kevin.lemoi@savant.com>
> Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
Acked-by: Otavio Salvador <otavio@ossystems.com.br>
--
Otavio Salvador O.S. Systems
http://www.ossystems.com.br http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750
next prev parent reply other threads:[~2015-06-15 11:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-13 20:24 [PATCH v2] mmc: core: Do not set mmc voltage to 1.8V when 'no-1-8-v' is present Fabio Estevam
2015-06-15 11:44 ` Otavio Salvador [this message]
2015-06-15 12:08 ` Ulf Hansson
2015-06-15 12:23 ` Fabio Estevam
2015-06-15 12:49 ` Fabio Estevam
2015-06-16 9:31 ` Ulf Hansson
2015-06-17 16:25 ` Fabio Estevam
2015-06-18 7:58 ` Ulf Hansson
2015-06-18 14:25 ` Dong Aisheng
2015-06-18 14:03 ` Dong Aisheng
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=CAP9ODKp5c9fq+og8pcYAK0LvZKQVj62e+-xa2seVM+dWTky+SA@mail.gmail.com \
--to=otavio@ossystems.com.br \
--cc=aisheng.dong@freescale.com \
--cc=chuanxiao.dong@intel.com \
--cc=fabio.estevam@freescale.com \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=kevin.lemoi@savant.com \
--cc=linux-mmc@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.