From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Stefan Roese <sr@denx.de>, linux-mmc@vger.kernel.org
Cc: Adrian Hunter <adrian.hunter@intel.com>
Subject: Re: SDIO "SD2" vs. SD-card "SD3" interface on BayTrail
Date: Tue, 04 Jul 2017 16:53:51 +0300 [thread overview]
Message-ID: <1499176431.22624.255.camel@linux.intel.com> (raw)
In-Reply-To: <d7249bf2-b057-0535-334e-71cdc957e9b5@denx.de>
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.
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2017-07-04 13:53 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 [this message]
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
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=1499176431.22624.255.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=adrian.hunter@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 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.