From: Adrian Hunter <adrian.hunter@intel.com>
To: Raul Rangel <rrangel@chromium.org>
Cc: linux-mmc@vger.kernel.org, ernest.zhang@bayhubtech.com,
djkurtz@chromium.org, linux-kernel@vger.kernel.org,
Ulf Hansson <ulf.hansson@linaro.org>
Subject: Re: [PATCH 2/3] mmc: sdhci: sdhci-pci-o2micro: Check if controller supports 8-bit width
Date: Thu, 13 Jun 2019 11:40:14 +0300 [thread overview]
Message-ID: <94fa2a5e-e96d-acb3-46c2-5f6b1dea6711@intel.com> (raw)
In-Reply-To: <20190612150832.GB27989@google.com>
On 12/06/19 6:08 PM, Raul Rangel wrote:
> On Wed, Jun 12, 2019 at 04:09:47PM +0300, Adrian Hunter wrote:
>> On 10/06/19 9:53 PM, Raul E Rangel wrote:
>>> The O2 controller supports 8-bit EMMC access. mmc_select_bus_width()
>>> will be used to determine if the MMC supports 8-bit or 4-bit access.
>>
>> The problem is that the bit indicates a host controller capability, not how
>> many data lines there actually are on the board. Will this break something
>> that does not have 8 lines?
>
> So I asked the controller vendor about that:
>> The capability shows the host controller can support 1,4,and 8 bit bus
>> data transfer but it also depends on if HW can support it. Driver or FW
>> should implement the bus testing procedure that is defined in A.6.3.a
>> in JESD84-B51 spec to decide the real bus width that is supported in HW.
>
> This seems to be what `mmc_select_bus_width()` is doing.
Good point. Can you add this information to the commit message and add a
comment in the code.
>
> I don't actually have any 4-bit hardware to test with though.
>
> Thanks for the review!
>
next prev parent reply other threads:[~2019-06-13 16:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-10 18:53 [PATCH 1/3] mmc: sdhci: sdhci-pci-o2micro: Correctly set bus width when tuning Raul E Rangel
2019-06-10 18:53 ` [PATCH 2/3] mmc: sdhci: sdhci-pci-o2micro: Check if controller supports 8-bit width Raul E Rangel
2019-06-12 13:09 ` Adrian Hunter
2019-06-12 15:08 ` Raul Rangel
2019-06-13 8:40 ` Adrian Hunter [this message]
2019-06-10 18:53 ` [PATCH 3/3] mmc: sdhci: Fix indenting on SDHCI_CTRL_8BITBUS Raul E Rangel
2019-06-12 13:12 ` Adrian Hunter
2019-06-12 13:42 ` Ulf Hansson
2019-06-12 12:53 ` [PATCH 1/3] mmc: sdhci: sdhci-pci-o2micro: Correctly set bus width when tuning Adrian Hunter
2019-06-12 13:36 ` Ulf Hansson
2019-06-12 15:01 ` Raul Rangel
2019-06-17 10:26 ` Ulf Hansson
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=94fa2a5e-e96d-acb3-46c2-5f6b1dea6711@intel.com \
--to=adrian.hunter@intel.com \
--cc=djkurtz@chromium.org \
--cc=ernest.zhang@bayhubtech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=rrangel@chromium.org \
--cc=ulf.hansson@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox