linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Beer <dlbeer@gmail.com>
To: Ben Chuang <benchuanggli@gmail.com>
Cc: adrian.hunter@intel.com, ben.chuang@genesyslogic.com.tw,
	linux-kernel@vger.kernel.org, linux-mmc@vger.kernel.org,
	ulf.hansson@linaro.org
Subject: Re: [PATCH] mmc: sdhci-pci-gli: increase 1.8V regulator wait
Date: Mon, 26 Apr 2021 20:25:26 +1200	[thread overview]
Message-ID: <20210426082526.GA16240@nyquist.nev> (raw)
In-Reply-To: <20210426073251.7726-1-benchuanggli@gmail.com>

On Mon, Apr 26, 2021 at 03:32:51PM +0800, Ben Chuang wrote:
> > The driver currently waits 5ms after switching on the 1.8V regulator for
> > it to become stable. Increasing this to 10ms gets rid of the warning
> > about stability, but most cards still fail. Increasing it to 20ms gets
> > some cards working (a 32GB Samsung micro SD works, a 128GB ADATA
> > doesn't). At 50ms, the ADATA works most of the time, and at 100ms both
> > cards work reliably.
> 
> If it is convenient, can you provide the appearance pictures and product
> links of these two cards? We want to buy them.

Hi Ben,

The first is a Samsung EVO microSDXC 32GB:

    https://www.samsung.com/nz/memory-storage/memory-card/evo-plus-microsd-card-95-mbs-sd-adapter-32gb-mb-mc32ga-apc/

The second is an ADATA Premier Pro SDXC UHS-I U3 Class 10 (V30S) 128GB:

    https://www.adata.com/us/consumer/289

The images on those two pages match what I have in front of me here.

Cheers,
Daniel

-- 
Daniel Beer <dlbeer@gmail.com> http://dlbeer.co.nz/
PGP: BA6E 0B26 1F89 246C E3F3  C910 1E58 C43A 160A 553B

  reply	other threads:[~2021-04-26  8:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-24  8:16 [PATCH] mmc: sdhci-pci-gli: increase 1.8V regulator wait Daniel Beer
2021-04-26  7:32 ` Ben Chuang
2021-04-26  8:25   ` Daniel Beer [this message]
2021-05-11 10:56   ` Ulf Hansson

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=20210426082526.GA16240@nyquist.nev \
    --to=dlbeer@gmail.com \
    --cc=adrian.hunter@intel.com \
    --cc=ben.chuang@genesyslogic.com.tw \
    --cc=benchuanggli@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).