From: Adrian Hunter <adrian.hunter@intel.com>
To: Stefan Roese <sr@denx.de>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: linux-mmc@vger.kernel.org
Subject: Re: SDIO "SD2" vs. SD-card "SD3" interface on BayTrail
Date: Thu, 31 Aug 2017 15:41:45 +0300 [thread overview]
Message-ID: <dc49d8be-dd15-167b-2ab4-d09d1b6ea83d@intel.com> (raw)
In-Reply-To: <8a909116-5fec-e7d0-5d30-de8de42612df@denx.de>
On 31/08/17 12:38, Stefan Roese wrote:
> Hi Andy, Hi Adrian,
>
> On 04.07.2017 15:53, Andy Shevchenko wrote:
>> On Tue, 2017-07-04 at 14:53 +0200, Stefan Roese wrote:
>>> Hi,
>>>
>>> we are currently investigating, if its possible to connect a SDIO
>>> device (WLAN module) to the SD-card interface "SD3" of the BayTrail
>>> SoC instead of the SDIO interface "SD2". The BayTrail manual states,
>>> that the SDIO interface is capable of connecting SDIO devices. Is
>>> this also possible for the SD-card interface "SD3", even if its not
>>> explicitly mentioned in the manual? If not, why is this not possible?
>>>
>>> Any insight on this would be really helpful.
>>
>> Hmm... I have no documentation for SD/SDIO/eMMC for BayTrail except the
>> public one. Internally I found some charts that shows similarities
>> between two. So, taking that into consideration I would suggest to try
>> it out on real hardware (MinnowBoard MAX, for example), only impediment
>> I can see is the absence of support in the drivers in Linux OS. If you
>> need it only in U-Boot, you perhaps may fix it easily.
>>
>> P.S. Adrian on vacation.
>
> I hope your vacation was great!
>
> Sorry for getting back to this, but I would really like to get some
> more feedback on this. Perhaps Adrian has some additional comments
> about the SDIO usage of the SD interface (SD3 - PCI Device ID 0x0f16)
> on BayTrail.
>
> I'm now running latest mainline Linux on this board and am trying to
> get the Linux MMC / SDIO subsystem to just detect a device on this
> SD PCI interface. For this I have added quite a bit of debug code to
> the MMC / SDIO code to see, if any device is detected on the SDIO
> port. But all command queries return timeout as far as I can tell.
I would usually interpret that to mean the SDIO card is not turned on.
> Adrian, do you have some additional information, if this mode of
> operation is possible at all on this SD-card interface, even if
> its not explicitly mentioned in the BayTrail datasheet?
I have used removable SDIO cards in SD slots before. It should work.
> Or do you
> have some suggestions, how I could test such a basic SDIO connection
> (without integrating of the WLAN driver first) in the simplest way?
Only to try a removable SDIO card.
next prev parent reply other threads:[~2017-08-31 12:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-04 12:53 SDIO "SD2" vs. SD-card "SD3" interface on BayTrail Stefan Roese
2017-07-04 13:53 ` Andy Shevchenko
2017-07-04 14:12 ` Stefan Roese
2017-07-04 15:56 ` Andy Shevchenko
2017-08-31 9:38 ` Stefan Roese
2017-08-31 12:41 ` Adrian Hunter [this message]
2017-08-31 15:24 ` Stefan Roese
2017-10-07 8:25 ` Stefan Roese
2017-10-09 8:07 ` Adrian Hunter
[not found] ` <CAG8K7gQNmpMhLdnpua6cds1s7s3aq8B1kS7-z+hg6fjty6Hqxg@mail.gmail.com>
2017-10-16 9:40 ` Stefan Roese
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=dc49d8be-dd15-167b-2ab4-d09d1b6ea83d@intel.com \
--to=adrian.hunter@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-mmc@vger.kernel.org \
--cc=sr@denx.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