public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: Simon Horman <horms@verge.net.au>
Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>,
	linux-renesas-soc@vger.kernel.org, linux-mmc@vger.kernel.org
Subject: Re: [RFT] arm64: dts: renesas: salvator-common: enable SDR104 for SD cards
Date: Tue, 29 Aug 2017 17:42:37 +0200	[thread overview]
Message-ID: <20170829154237.vdt3hbtjnos2eu2c@ninjato> (raw)
In-Reply-To: <20170808185445.GA2170@katana>

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


> As discussed in a chat, I tried SDR104 with my SDIO WiFi cards:
> 
> H3:
> - one slot worked flawlessly
> - one slot could load FW but failed to read status
> (with SDR50: both slots work)
> 
> M3-W:
> - both slots could not load the firmware
> (with SDR50: one slot works, one fails to load FW)

Update for my H3-ES2.0:

 - both slots could not load the firmware with SDR104
 (with SDR50: both slots work)

> The cards, however, were correctly identified as SDR104 and there were
> no tuning errors and no other SDHI related warnings.

This still holds true.


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

      parent reply	other threads:[~2017-08-29 15:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-02 20:13 [RFT] arm64: dts: renesas: salvator-common: enable SDR104 for SD cards Wolfram Sang
2017-08-03  7:43 ` Simon Horman
2017-08-03 15:54   ` Simon Horman
2017-08-03 15:55     ` Simon Horman
2017-08-08 18:54       ` Wolfram Sang
2017-08-14  5:10         ` Simon Horman
2017-08-14 15:46           ` Wolfram Sang
2017-08-17  8:44             ` Simon Horman
2017-08-29 15:42         ` Wolfram Sang [this message]

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=20170829154237.vdt3hbtjnos2eu2c@ninjato \
    --to=wsa@the-dreams.de \
    --cc=horms@verge.net.au \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=wsa+renesas@sang-engineering.com \
    /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