public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: stefan@agner.ch (Stefan Agner)
To: linux-arm-kernel@lists.infradead.org
Subject: imx7: mmc_select_hs200 failed, error -74
Date: Wed, 17 May 2017 11:23:26 -0700	[thread overview]
Message-ID: <a548e1627b3a18382958fc66a3829289@agner.ch> (raw)
In-Reply-To: <CAOMZO5BeE_Lm+VM8d9TKv0b21cL6dVNYgBai3wBjjm=bssXWCA@mail.gmail.com>

On 2017-05-17 11:02, Fabio Estevam wrote:
> Hi Haibo,
> 
> On Tue, May 16, 2017 at 11:10 PM, Bough Chen <haibo.chen@nxp.com> wrote:
> 
>> Hi Fabio,
>>
>> Can you open the mmc debug and show the full log?
>> By the way, you should first make sure whether the eMMC chip you used support HS200, and double
>> check whether the vccq voltage is 1.8v or 1.2v, HS200 mode can't work on 3.3v I/O voltage.
> 
> The imx7s warp board supplies 3.15V to VCCQ eMMC pins, so it cannot
> work in HS200 mode as you said.
> 
> In this case it should still be able to work in DDR52 mode though.

Maybe I missed something, but shouldn't that all be part of the device
tree these days?

E.g. mark that it is only 3.3V capable (no-1-8-v) and maybe other
capabilities (see Documentation/devicetree/bindings/mmc/mmc.txt).

> 
> Please see the patch I sent:
> http://marc.info/?l=linux-mmc&m=149495763808805&w=2

Afaict, the hardware tries to use whatever is the greatest common
denominator... If the board has restrictions, they should be specified
in the DT, and the driver should respect them.

--
Stefan

  reply	other threads:[~2017-05-17 18:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-16 13:58 imx7: mmc_select_hs200 failed, error -74 Fabio Estevam
2017-05-16 15:37 ` Fabio Estevam
2017-05-16 17:57   ` Fabio Estevam
2017-05-17  2:10   ` Bough Chen
2017-05-17 18:02     ` Fabio Estevam
2017-05-17 18:23       ` Stefan Agner [this message]
2017-05-17 18:40         ` Fabio Estevam

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=a548e1627b3a18382958fc66a3829289@agner.ch \
    --to=stefan@agner.ch \
    --cc=linux-arm-kernel@lists.infradead.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