From: Gary Thomas <gary@mlbassoc.com>
To: meta-freescale@yoctoproject.org
Subject: Re: [meta-fsl-arm/V2][PATCH 1/2] linux-imx_3.14.28: fix initial MMC device detection
Date: Mon, 08 Jun 2015 10:29:24 -0600 [thread overview]
Message-ID: <5575C2E4.7030805@mlbassoc.com> (raw)
In-Reply-To: <5575C074.4040902@boundarydevices.com>
On 2015-06-08 10:19, Eric Nelson wrote:
> Hi Andreas,
>
> On 06/08/2015 05:48 AM, Andreas Müller wrote:
>> On Variscite Varsom we have three devices connected to MMC
>>
>> * MMC1: eMMC
>> * MMC2: SDCard
>> * MMC3: Wifi
>>
>> Without this patch only the first device was detected properly.
>> I found two workarounds which can be removed by this patch:
>>
>> 1. Variscite: booting from SDCard made possible by renumbering MMC devices [1].
>> 2. BoundaryDevices: Add workqueues for each mmc_host [2]. This had been tested
>> here too but causes crashing sdcard for huge storage traffic.
Can you (Andreas) elaborate on this? Is there a procedure to show this failure?
I'd like to test it on my board(s) that have multiple [active] MMC devices.
>>
>> [1] https://github.com/varigit/linux-2.6-imx/blob/imx_3.10.53_1.1.0_ga_var01/arch/arm/boot/dts/imx6qdl.dtsi / Line 879
>> [2] https://github.com/boundarydevices/linux-imx6/commit/1d40159a995a298f16901bfb14ae3e0294c65691
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2015-06-08 16:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-08 12:48 [meta-fsl-arm/V2][PATCH 0/2] linux-imx-3.14.28 important bugfixes by applying mainline patches Andreas Müller
2015-06-08 12:48 ` [meta-fsl-arm/V2][PATCH 1/2] linux-imx_3.14.28: fix initial MMC device detection Andreas Müller
2015-06-08 16:19 ` Eric Nelson
2015-06-08 16:29 ` Gary Thomas [this message]
2015-06-08 19:48 ` Andreas Müller
2015-06-08 12:48 ` [meta-fsl-arm/V2][PATCH 2/2] linux-imx-3.14.28: FEC: fix garbage send for huge data blocks Andreas Müller
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=5575C2E4.7030805@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=meta-freescale@yoctoproject.org \
/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.