From: Sascha Hauer <s.hauer@pengutronix.de>
To: Markus Niebel <list-09_barebox@tqsc.de>
Cc: barebox@lists.infradead.org, Markus Niebel <Markus.Niebel@tqs.de>
Subject: Re: [PATCH 1/3] mci: add DSR support
Date: Mon, 13 Jan 2014 09:19:11 +0100 [thread overview]
Message-ID: <20140113081911.GG16215@pengutronix.de> (raw)
In-Reply-To: <52CFE00B.6090108@tqsc.de>
On Fri, Jan 10, 2014 at 12:56:59PM +0100, Markus Niebel wrote:
> Hello Sascha,
> Am 10.01.2014 12:18, wrote Sascha Hauer:
> > Hi Markus,
> >
> > On Fri, Jan 10, 2014 at 10:29:49AM +0100, Markus Niebel wrote:
> >> From: Markus Niebel <Markus.Niebel@tqs.de>
> >>
> >> The eMMC and the SD-Card specifications describe the optional SET_DSR command.
> >> During measurements at our lab we found that some cards implementing this feature
> >> having really strong driver strengts per default. This can lead to voltage peaks
> >> above the specification of the host on signal edges for data sent from a card to
> >> the host.
> >>
> >> Since availability of a given card type may be shorter than the time a certain
> >> hardware will be produced it is useful to have support for this command (Alternative
> >> would be changing termination resistors and adapting the driver strength of the
> >> host to the used card.)
> >
> > So not all cards support this command. Have you tested it with cards
> > that do not support it to make sure they still work? With eMMC you know
> > at board level whether or not this command is supported, but with SD
> > cards you don't.
> >
>
> No tests done with SD-cards (SD card spec states, that DSR can be implemented,
> but we found no card, that implements this feature).
>
> On the eMMC side we did tests with TQMa53 (barebox and u-boot) and TQMa6
> (u-boot only) and also with i.MX28 based platform:
>
> if a card does not support DSR - CMD4 is never sent
> if a card supports DSR but board does not activate the feature - CMD4 is never sent
> if a card supports DSR and board code requests the feature - CMD4 is sent with the
> configured value.
>
> Would it be a good idea to document the feature as intended for non removable cards
> where the exact value is known?
My only concern was that this feature might be enabled on slots where
cards are used that do not support the DSR feature and do not work
anymore. As this doesn't seem to be the case I'm fine with your patch.
Adding devicetree support is a good idea though as Alexander mentioned.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2014-01-13 8:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-10 9:29 [RFC] " Markus Niebel
2014-01-10 9:29 ` [PATCH 1/3] " Markus Niebel
2014-01-10 11:18 ` Sascha Hauer
2014-01-10 11:56 ` Markus Niebel
2014-01-13 8:19 ` Sascha Hauer [this message]
2014-01-10 9:29 ` [PATCH 2/3] mci: imx-esdhc: " Markus Niebel
2014-01-10 9:25 ` Alexander Shiyan
2014-01-10 10:23 ` Markus Niebel
2014-01-10 9:29 ` [PATCH 3/3] boards: tqma53: add DSR support for eMMC Markus Niebel
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=20140113081911.GG16215@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=Markus.Niebel@tqs.de \
--cc=barebox@lists.infradead.org \
--cc=list-09_barebox@tqsc.de \
/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