All of lore.kernel.org
 help / color / mirror / Atom feed
From: Faiz Abbas <faiz_abbas@ti.com>
To: Adrian Hunter <adrian.hunter@intel.com>,
	<linux-kernel@vger.kernel.org>, <linux-mmc@vger.kernel.org>
Cc: <ulf.hansson@linaro.org>, <asutoshd@codeaurora.org>,
	<riteshh@codeaurora.org>, <venkatg@codeaurora.org>
Subject: Re: [RFC] mmc: cqhci: commit descriptors before setting the doorbell
Date: Fri, 18 Oct 2019 12:52:55 +0530	[thread overview]
Message-ID: <8fba4072-a252-7397-15b2-791e2619024d@ti.com> (raw)
In-Reply-To: <2275bfdc-ff30-719e-ae78-8c8bd20b8c80@ti.com>

Adrian,

On 16/10/19 5:46 PM, Faiz Abbas wrote:
> Adrian,
> 
> On 15/10/19 7:15 PM, Adrian Hunter wrote:
>> On 15/10/19 10:55 AM, Faiz Abbas wrote:
>>> Hi,
>>>
>>> On 15/10/19 12:08 AM, Faiz Abbas wrote:
>>>> Add a write memory barrier to make sure that descriptors are actually
>>>> written to memory before ringing the doorbell.
>>>>
>>>> Signed-off-by: Faiz Abbas <faiz_abbas@ti.com>
>>>> ---
>>>>
>>>> This patch fixes a very infrequent ADMA error (1 out of 100 times) that
>>>> I have been seeing after enabling command queuing for J721e.
>>>> Also looking at memory-barriers.txt and this commit[1],
>>>> it looks like we should be doing this before any descriptor write
>>>> followed by a doorbell ring operation. It'll be nice if someone with more
>>>> expertise in memory barriers can comment.
>>>>
>>>> [1] ad1a1b9cd67a ("scsi: ufs: commit descriptors before setting the
>>>>     doorbell")
>>>
>>> So I see that cqhci_readl/writel() use readl/writel_relaxed() which
>>> seems to be causing this issue. Should I just fix this by converting
>>> those to readl/writel with memory barriers instead?
>>
>> Perhaps we could do both changes i.e. add wmb() and convert to non-relaxed
>> readl/writel
>>
> 
> readl is implemented as  readl_relaxed(); __rmb();
> and
> writel is implemented as wmb(); writel_relaxed();
> 
> I think another wmb() before writel will be redundant.
> 
> Maybe this patch is good enough in itself.
> 

Do you agree?

Thanks,
Faiz

WARNING: multiple messages have this Message-ID (diff)
From: Faiz Abbas <faiz_abbas@ti.com>
To: Adrian Hunter <adrian.hunter@intel.com>,
	linux-kernel@vger.kernel.org, linux-mmc@vger.kernel.org
Cc: ulf.hansson@linaro.org, asutoshd@codeaurora.org,
	riteshh@codeaurora.org, venkatg@codeaurora.org
Subject: Re: [RFC] mmc: cqhci: commit descriptors before setting the doorbell
Date: Fri, 18 Oct 2019 12:52:55 +0530	[thread overview]
Message-ID: <8fba4072-a252-7397-15b2-791e2619024d@ti.com> (raw)
In-Reply-To: <2275bfdc-ff30-719e-ae78-8c8bd20b8c80@ti.com>

Adrian,

On 16/10/19 5:46 PM, Faiz Abbas wrote:
> Adrian,
> 
> On 15/10/19 7:15 PM, Adrian Hunter wrote:
>> On 15/10/19 10:55 AM, Faiz Abbas wrote:
>>> Hi,
>>>
>>> On 15/10/19 12:08 AM, Faiz Abbas wrote:
>>>> Add a write memory barrier to make sure that descriptors are actually
>>>> written to memory before ringing the doorbell.
>>>>
>>>> Signed-off-by: Faiz Abbas <faiz_abbas@ti.com>
>>>> ---
>>>>
>>>> This patch fixes a very infrequent ADMA error (1 out of 100 times) that
>>>> I have been seeing after enabling command queuing for J721e.
>>>> Also looking at memory-barriers.txt and this commit[1],
>>>> it looks like we should be doing this before any descriptor write
>>>> followed by a doorbell ring operation. It'll be nice if someone with more
>>>> expertise in memory barriers can comment.
>>>>
>>>> [1] ad1a1b9cd67a ("scsi: ufs: commit descriptors before setting the
>>>>     doorbell")
>>>
>>> So I see that cqhci_readl/writel() use readl/writel_relaxed() which
>>> seems to be causing this issue. Should I just fix this by converting
>>> those to readl/writel with memory barriers instead?
>>
>> Perhaps we could do both changes i.e. add wmb() and convert to non-relaxed
>> readl/writel
>>
> 
> readl is implemented as  readl_relaxed(); __rmb();
> and
> writel is implemented as wmb(); writel_relaxed();
> 
> I think another wmb() before writel will be redundant.
> 
> Maybe this patch is good enough in itself.
> 

Do you agree?

Thanks,
Faiz

  reply	other threads:[~2019-10-18  7:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-14 18:38 [RFC] mmc: cqhci: commit descriptors before setting the doorbell Faiz Abbas
2019-10-14 18:38 ` Faiz Abbas
2019-10-15  7:55 ` Faiz Abbas
2019-10-15  7:55   ` Faiz Abbas
2019-10-15 13:45   ` Adrian Hunter
2019-10-16 12:16     ` Faiz Abbas
2019-10-16 12:16       ` Faiz Abbas
2019-10-18  7:22       ` Faiz Abbas [this message]
2019-10-18  7:22         ` Faiz Abbas
2019-10-18  7:30         ` Adrian Hunter
2019-10-18 10:58 ` Ulf Hansson
2019-10-18 11:27   ` Faiz Abbas

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=8fba4072-a252-7397-15b2-791e2619024d@ti.com \
    --to=faiz_abbas@ti.com \
    --cc=adrian.hunter@intel.com \
    --cc=asutoshd@codeaurora.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=riteshh@codeaurora.org \
    --cc=ulf.hansson@linaro.org \
    --cc=venkatg@codeaurora.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.