On Wed, Dec 16, 2015 at 4:07 AM, Ulf Hansson wrote:
> To find the improved card detection times, I just used the kernel boot
> log and checked the time stamps for when the cards get detected. I ran
> the tests ~10 times and picked up some average values.
>
> To notice the
On Fri, Nov 13, 2015 at 9:56 AM, Holger Schurig wrote:
> There have been some attempts to add FFU (field firmware update). The last
> AFAIK in Nov 2014, http://www.spinics.net/lists/linux-mmc/msg29324.html
>
> But it seems that the committers weren't persistent enought.
On Thu, Nov 19, 2015 at 3:56 PM, Arnd Bergmann wrote:
>> cap-sd-highspeed;
>> sd-uhs-sdr12;
>> sd-uhs-sdr25;
>> sd-uhs-sdr50;
>> sd-uhs-ddr50;
>>
On Fri, Nov 13, 2015 at 4:31 AM, Ulf Hansson <ulf.hans...@linaro.org> wrote:
> On 12 November 2015 at 20:44, Alan Cooper <alcoop...@gmail.com> wrote:
>> On Thu, Nov 12, 2015 at 4:35 AM, Ulf Hansson <ulf.hans...@linaro.org> wrote:
>>> On 6 November 2015 at 1
On Thu, Nov 12, 2015 at 4:35 AM, Ulf Hansson wrote:
> On 6 November 2015 at 19:56, Al Cooper wrote:
>> Add support for "broken-ddr50", "broken-64-bit-dma"
>> and "broken-timeout-value" device tree properties.
>> The properties will cause the
On Fri, Nov 6, 2015 at 3:14 AM, Ulf Hansson wrote:
> No thanks! No more quirks please!
OK, I'll move this functionality into the sdhci-brcmstb driver and
re-submit the patch set.
Thanks
Al
--
To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
the
On Tue, Aug 25, 2015 at 8:04 AM, Ulf Hansson wrote:
> Thanks for the info. I am okay going forward with this patchset,
> though I think it's a bit late (my fault) for 4.3. Could you perhaps
> repost once 4.3 rc1 is out!?
Thanks!
I'll re-post after 4.3 rc1.
Al
--
To
I understand. For an API that accepts sectors that are not erase block
aligned the correct answer really is 1 sector for this eMMC/Host
controller combination. Unfortunately this hangs mkfs.ext4 for about
10 hours. Have there been any other suggested solutions?
On Wed, Feb 25, 2015 at 4:55 PM, Al
Has there been any discussion of adding support for lock/unlock
functionality (CMD42) for SD?
Thanks
Al
--
To unsubscribe from this list: send the line unsubscribe linux-mmc in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
I recently added a patch that prevents the switch to 1.8v if the host
capabilities register does not indicate support for any of the UHS
speeds (SDR50, DDR50, SDR104). This allowed our controller to work
with UHS cards in HS mode (50MHz, 3.3v).
Al
On Sun, May 27, 2012 at 9:36 PM,
Still hoping for comments on the patch.
Thanks
Al
On Fri, Mar 16, 2012 at 3:54 PM, Al Cooper acoo...@gmail.com wrote:
The driver should not try to switch to 1.8V when the SD 3.0 host
controller does not have any UHS capabilities bits set (SDR50, DDR50
or SDR104). See page 72 of SD
I have a 3.0 host controller on a board that only does 3.3V. The
capabilities registers don't specify support for any UHS modes and
also don't show support for 1.8V. When I insert a UHS card the driver
tries to switch to 1.8V and fails to init the card. I was hoping I
could set the CAP registers
12 matches
Mail list logo