All of lore.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, 8 Aug 2017 20:54:45 +0200	[thread overview]
Message-ID: <20170808185445.GA2170@katana> (raw)
In-Reply-To: <20170803155520.GB3826@verge.net.au>

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


> As it is an "RFT" I'm happy to apply it if you repost
> it or otherwise indicate that is what you would like to happen.

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)

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

Changing TDSEL in the PFC did not change anything.

The manual of the WiFi card (u-blox EMMY-W1) mentions a maximum line
length of 100mm. Measuring a direct line from the SoC to the slots,
I'd think we are very much on the edge of that. And given the length
of the SDIO adapter, we are surely exceeding that :(

Maybe we should do more tests with more boards? On the other hand, it
seems the WiFi card is running out of the specs.

So much for now. I'll sleep over it and try to get more data tomorrow.

Regards,

   Wolfram


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

  reply	other threads:[~2017-08-08 18:54 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 [this message]
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

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=20170808185445.GA2170@katana \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.