From: Adrian Hunter <adrian.hunter@intel.com>
To: Bean Huo <huobean@gmail.com>, Ulf Hansson <ulf.hansson@linaro.org>
Cc: Bean Huo <beanhuo@micron.com>,
linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 2/2] mmc: sdhci: Use the SW timer when the HW timer cannot meet the timeout value required by the device
Date: Thu, 30 Sep 2021 11:59:34 +0300 [thread overview]
Message-ID: <6d57e6bd-24ba-f07e-678c-691f202549d5@intel.com> (raw)
In-Reply-To: <3078b365b5ddfad198a5c8a097f2e7edb9730e2c.camel@gmail.com>
On 30/09/2021 11:34, Bean Huo wrote:
> Hi Adrian,
>
>
> Thanks.
> I want to give a short conclusion for our discussion:
>
> Based on your information, these sounds disable of HW timer timeout
> interrupt will make eMMC host controller malfunction, in another word,
> the disable of timeout interrupt will make the eMMC host cannot
> correctly provide the completion interrupt. And unless only when the
> SOC vendor signals that their SOC supports that the host side SW can
> disable this HW timeout interrupt, as TI does.
>
> I studied the SDHCI Spec, and tried to see if there is this kind of
> support statement, but not been found yet. I will check with other SOC
> vendors.
>
> I have one more question, if you know, please give me your information.
>
> I did testing on HW timer bahevior in case CQE is on. Currently, we
> always set the HW timer with the maximum timeout value if CQE is on.
> Based on my testing, the HW timer will never timeout when we enable
> CQE. I changed the HW timer value to be lower, it is the same result.
> Do you know that the HW timer will be inactivated in case CQE is
> on? but its timeout interrupt is still enabled.
No I don't know how different CQE handle timeouts.
>
> Kind regards,
> Bean
>
next prev parent reply other threads:[~2021-09-30 8:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210917172727.26834-1-huobean@gmail.com>
2021-09-17 17:27 ` [PATCH v1 1/2] mmc: sdhci: Return true only when timeout exceeds capacity of the HW timer Bean Huo
2021-09-24 6:32 ` Adrian Hunter
2021-09-27 22:31 ` Ulf Hansson
2021-09-17 17:27 ` [PATCH v1 2/2] mmc: sdhci: Use the SW timer when the HW timer cannot meet the timeout value required by the device Bean Huo
2021-09-24 5:29 ` Adrian Hunter
2021-09-24 9:17 ` Bean Huo
2021-09-24 10:07 ` Adrian Hunter
2021-09-24 11:45 ` Bean Huo
2021-09-24 12:17 ` Adrian Hunter
2021-09-24 13:08 ` Bean Huo
2021-09-24 13:26 ` Adrian Hunter
2021-09-24 21:33 ` Bean Huo
2021-09-28 9:39 ` Bean Huo
2021-09-28 10:18 ` Adrian Hunter
2021-09-29 10:49 ` Bean Huo
2021-09-29 12:38 ` Adrian Hunter
2021-09-30 8:34 ` Bean Huo
2021-09-30 8:59 ` Adrian Hunter [this message]
2021-09-30 9:02 ` Bean Huo
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=6d57e6bd-24ba-f07e-678c-691f202549d5@intel.com \
--to=adrian.hunter@intel.com \
--cc=beanhuo@micron.com \
--cc=huobean@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.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 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.