public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Anholt <eric@anholt.net>
To: Stefan Wahren <stefan.wahren@i2se.com>,
	Gerd Hoffmann <kraxel@redhat.com>,
	Adrian Hunter <adrian.hunter@intel.com>,
	Ulf Hansson <ulf.hansson@linaro.org>
Cc: Ray Jui <rjui@broadcom.com>,
	Scott Branden <sbranden@broadcom.com>,
	linux-mmc@vger.kernel.org, bcm-kernel-feedback-list@broadcom.com,
	linux-arm-kernel@lists.infradead.org,
	linux-rpi-kernel@lists.infradead.org,
	Jon Mason <jonmason@broadcom.com>
Subject: Re: [PATCH 1/2] mmc: sdhci-iproc: Apply caps from bcm2835-mmc driver
Date: Wed, 04 Jan 2017 10:16:06 -0800	[thread overview]
Message-ID: <871swi8zdl.fsf@eliezer.anholt.net> (raw)
In-Reply-To: <1751352115.251342.1483474996021@email.1und1.de>

[-- Attachment #1: Type: text/plain, Size: 1390 bytes --]

Stefan Wahren <stefan.wahren@i2se.com> writes:

> Hi Eric,
>
>> Eric Anholt <eric@anholt.net> hat am 3. Januar 2017 um 19:27 geschrieben:
>> 
>> 
>> Stefan Wahren <stefan.wahren@i2se.com> writes:
>> 
>> > Since the mmc module on bcm2835 neither provide a capabilities register nor 
>> > free documentation we must rely on the downstream implementation [1].
>> 
>> Yeah, caps reg is wired to 0, but it can do high speed.
>> 
>> Since we're VDD_330 only, I'm not sure the driver type flags do
>> anything, but I'm still good with having consistency.
>
> yes, the driver type flags currently have no benefit.
>
>> 
>> Reviewed-by: Eric Anholt <eric@anholt.net>
>> 
>> Interested in porting over the DMA support? :)
>
> AFAIK the sdhci doesn't support external DMA (required for bcm2835).
> So DMA support would result in a new driver, which i'm currently not interested.
>
> But i've prepared a fixup patch series for the sdhost driver i want to send to Gerd.
>
>> 
>> I also noticed that the emmc wrapper module claims it can run with a
>> clock from 50-100mhz, and the arasan says it can run at up to 50, 52, or
>> 208mhz depending on SD/MMC mode.  Could we get a boost from running the
>> module at a higher clock rate?
>
> Sorry, i can't follow. Do you mean DDR mode?

Apparently I what I was reading about was SDR104 mode, which also
requires 1.8V.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2017-01-04 18:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-30 15:24 [PATCH 0/2] mmc: sdhci-iproc: Improve bcm2835 performance Stefan Wahren
2016-12-30 15:24 ` [PATCH 1/2] mmc: sdhci-iproc: Apply caps from bcm2835-mmc driver Stefan Wahren
2017-01-03 18:27   ` Eric Anholt
2017-01-03 20:23     ` Stefan Wahren
2017-01-04 18:16       ` Eric Anholt [this message]
2017-01-05  9:53   ` Adrian Hunter
2016-12-30 15:24 ` [PATCH 2/2] mmc: sdhci-iproc: Increase max_blk_size for bcm2835 Stefan Wahren
2017-01-03 18:04   ` Eric Anholt
2017-01-04 18:47     ` Scott Branden
2017-01-05  9:53   ` Adrian Hunter
2017-01-10 15:38 ` [PATCH 0/2] mmc: sdhci-iproc: Improve bcm2835 performance 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=871swi8zdl.fsf@eliezer.anholt.net \
    --to=eric@anholt.net \
    --cc=adrian.hunter@intel.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=jonmason@broadcom.com \
    --cc=kraxel@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-rpi-kernel@lists.infradead.org \
    --cc=rjui@broadcom.com \
    --cc=sbranden@broadcom.com \
    --cc=stefan.wahren@i2se.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