linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Oh <poh@codeaurora.org>
To: Johannes Berg <johannes@sipsolutions.net>,
	Peter Oh <poh@qca.qualcomm.com>
Cc: linux-wireless@vger.kernel.org, Bob Copeland <me@bobcopeland.com>,
	ath10k@lists.infradead.org
Subject: Re: [PATCH] ath10k: Replace ioread with wmb for data sync
Date: Mon, 02 Feb 2015 11:15:27 -0800	[thread overview]
Message-ID: <54CFCCCF.900@codeaurora.org> (raw)
In-Reply-To: <1422903279.8755.1.camel@sipsolutions.net>


On 02/02/2015 10:54 AM, Johannes Berg wrote:
> On Mon, 2015-02-02 at 09:33 -0800, Peter Oh wrote:
>
>>> The code (as it is before your patch) implies that it's trying to make
>>> sure that before it continues, any previous writes to the PCIe
> device's
>>> registers are posted. The only way to ensure that is to do a read to
> the
>>> registers, as the code does now.
>> Do you know how the read ensure that although the read code does not
>> check the return value?
>> Can you explain how a read ensures that posted write reaches PCIe
> device?
>
> You basically have the following sequence:
>
> iowrite()
> ioread()
>
> If you look, you'll see that iowrite() is actually done (or should be,
> or perhaps with appropriate syncs) on an uncached mapping.
since it's mmio, iowrite will be map to write, not out which is cached 
mapping.
That's why we address "posted write" here.
If it's un-cached mapping which is volatile, we don't even need ioread.
>   As a result,
> the only thing you care about here is the PCIe bus, not the CPU cache
> flush. And from there on that's just a question of PCIe bus semantics.
So how does ioread guarantee PCIe bus transaction done?
>
> johannes
>
>
> _______________________________________________
> ath10k mailing list
> ath10k@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/ath10k
Regards,
Peter

  reply	other threads:[~2015-02-02 19:15 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-26 22:25 [PATCH] ath10k: Replace ioread with wmb for data sync Peter Oh
2015-01-27 21:33 ` Bob Copeland
2015-01-27 23:53   ` Peter Oh
2015-01-28  4:30     ` Bob Copeland
2015-01-28  5:39       ` Peter Oh
2015-01-28  7:37         ` Johannes Berg
2015-01-30 22:53           ` Peter Oh
2015-01-31  1:16             ` Sujith Manoharan
2015-01-31  1:56               ` Peter Oh
2015-01-31  2:06                 ` Sujith Manoharan
2015-02-02 17:25                   ` Peter Oh
2015-02-02 22:26                   ` Adrian Chadd
2015-02-02 23:04                     ` Peter Oh
2015-02-02 13:02             ` Johannes Berg
2015-02-02 17:33               ` Peter Oh
2015-02-02 18:54                 ` Johannes Berg
2015-02-02 19:15                   ` Peter Oh [this message]
2015-02-02 19:22                     ` Johannes Berg
2015-02-02 19:36                       ` Peter Oh
2015-02-02 19:47                         ` Johannes Berg
2015-02-02 22:06                           ` Peter Oh
2015-02-02 23:25                             ` Florian Fainelli
2015-02-02 23:49                               ` Peter Oh

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=54CFCCCF.900@codeaurora.org \
    --to=poh@codeaurora.org \
    --cc=ath10k@lists.infradead.org \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=me@bobcopeland.com \
    --cc=poh@qca.qualcomm.com \
    /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;
as well as URLs for NNTP newsgroup(s).