public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: Marc Gonzalez <marc_gonzalez@sigmadesigns.com>
To: Alan Cooper <alcooperx@gmail.com>, Arnd Bergmann <arnd@arndb.de>
Cc: linux-mmc <linux-mmc@vger.kernel.org>,
	Ulf Hansson <ulf.hansson@linaro.org>,
	Soren Brinkmann <soren.brinkmann@xilinx.com>,
	Michal Simek <michal.simek@xilinx.com>,
	Russell King <linux@arm.linux.org.uk>,
	Suman Tripathi <stripathi@apm.com>
Subject: Re: Correct DT properties for Arasan controller
Date: Fri, 20 Nov 2015 14:21:16 +0100	[thread overview]
Message-ID: <564F1E4C.4030703@sigmadesigns.com> (raw)
In-Reply-To: <CAOGqxeUVJ_MFcKw3SMHMyg1PSLhhMOi4=HxuEZ7=L_PfFajEYA@mail.gmail.com>

On 19/11/2015 22:42, Alan Cooper wrote:

>>>                       cap-sd-highspeed;
>>>                       sd-uhs-sdr12;
>>>                       sd-uhs-sdr25;
>>>                       sd-uhs-sdr50;
>>>                       sd-uhs-ddr50;
>>>                       sd-uhs-sdr104;
> 
> These values normally come from the Host Controllers CAPS registers
> and are only needed if the CAPS register setting are incorrect.

Using a 4 GB microSDHC card + SD adapter, I get read speeds of
17.3 MB/s (4072669184 bytes in 236 seconds).
Is that an expected value? SDR25 should be 25 MB/s.
Perhaps I need to buy a better card.

>>> - cap-mmc-hw-reset: eMMC hardware reset is supported
> 
> This is only set if the driver supplies a hw_reset callback and the
> Arasan driver does not.

OK.

>>> - cap-sdio-irq: enable SDIO IRQ signalling on this interface
> 
> This is only set if the driver supplies a enable_sdio_irq and the
> Arasan driver does not.

Can't it use a generic implementation, such as sdhci_enable_sdio_irq?

Regards.


  reply	other threads:[~2015-11-20 13:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-19 16:37 Correct DT properties for Arasan controller Marc Gonzalez
2015-11-19 20:56 ` Arnd Bergmann
2015-11-19 21:42   ` Alan Cooper
2015-11-20 13:21     ` Marc Gonzalez [this message]
2015-11-20 12:53   ` Marc Gonzalez

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=564F1E4C.4030703@sigmadesigns.com \
    --to=marc_gonzalez@sigmadesigns.com \
    --cc=alcooperx@gmail.com \
    --cc=arnd@arndb.de \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=michal.simek@xilinx.com \
    --cc=soren.brinkmann@xilinx.com \
    --cc=stripathi@apm.com \
    --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