From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751813AbaKFEu4 (ORCPT ); Wed, 5 Nov 2014 23:50:56 -0500 Received: from avon.wwwdotorg.org ([70.85.31.133]:45146 "EHLO avon.wwwdotorg.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751084AbaKFEuz (ORCPT ); Wed, 5 Nov 2014 23:50:55 -0500 Message-ID: <545AFE2C.5050105@wwwdotorg.org> Date: Wed, 05 Nov 2014 21:50:52 -0700 From: Stephen Warren User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Scott Branden , Ulf Hansson , Russell King , Peter Griffin , Chris Ball , Piotr Krol CC: linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org, Joe Perches , linux-rpi-kernel@lists.infradead.org, Ray Jui , bcm-kernel-feedback-list@broadcom.com Subject: Re: [PATCHv2 5/5] mmc: sdhci-bcm2835: add sdhci quirk SDHCI_QUIRK_MULTIBLOCK_READ_ACMD12 References: <1414651017-3545-1-git-send-email-sbranden@broadcom.com> <1414651017-3545-6-git-send-email-sbranden@broadcom.com> <5459AEEA.8050503@wwwdotorg.org> <5459CB76.3060601@broadcom.com> In-Reply-To: <5459CB76.3060601@broadcom.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 11/05/2014 12:02 AM, Scott Branden wrote: > On 14-11-04 09:00 PM, Stephen Warren wrote: >> On 10/30/2014 12:36 AM, Scott Branden wrote: >>> SDHCI_QUIRK_MULTIBLOCK_READ_ACMD12 is missing and needed for this >>> controller. >> >> This seems fine, although any explanation of why this quirk is needed >> would be useful. >> > I don't know who to talk to at Arasan about this. Will try hunting > around a little for more info as to why this is needed to have eMMC and > SD work properly through our internal testing on other non-2835 chipset > that shares the same SDHCI controller as 2835. I thought I heard that this wasn't a bug in the controller itself, but rather an integration issue between the IP core and the register bus it's attached to. Consequently, it may be SoC-specific or at least have SoC-specific variations?