From: Bjorn Helgaas <helgaas@kernel.org>
To: Pratyush Anand <panand@redhat.com>
Cc: dongbo4@huawei.com, bhelgaas@google.com, jingoohan1@gmail.com,
linux-pci@vger.kernel.org
Subject: Re: [PATCH 0/2] pcie/designware: Viewport assignment update
Date: Mon, 22 Aug 2016 13:49:15 -0500 [thread overview]
Message-ID: <20160822184915.GH18628@localhost> (raw)
In-Reply-To: <cover.1467647958.git.panand@redhat.com>
On Mon, Jul 04, 2016 at 09:44:41PM +0530, Pratyush Anand wrote:
> Most of the designware PCIe platforms have more than 2 viewports. So, patch
> 1/2 allows to fix viewport-2 for IO transaction for such cases.
> When we have only two viewports, then patch 2/2 exchange viewport
> assignment of memory and cfg transaction. It helps to fix a possibility of
> corruption for memory transaction. However, there still exist possibility
> of an IO transaction to be corrupted. We can not do much for <=2 viewports.
> See, patch log for detail.
>
> Dong Bo (1):
> pcie/designware: Exchange viewport of `MEMORYs' and `CFGs/IOs'
>
> Pratyush Anand (1):
> pcie/designware: Keep viewport fixed for IO transaction if
> num_viewport > 2
>
> .../devicetree/bindings/pci/designware-pcie.txt | 3 ++
> drivers/pci/host/pcie-designware.c | 32 +++++++++++++++-------
> drivers/pci/host/pcie-designware.h | 1 +
> 3 files changed, 26 insertions(+), 10 deletions(-)
Applied (with Rob's ack on 1/2) to pci/host-designware for v4.9, thanks!
prev parent reply other threads:[~2016-08-22 18:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-04 16:14 [PATCH 0/2] pcie/designware: Viewport assignment update Pratyush Anand
2016-07-04 16:14 ` [PATCH 1/2] pcie/designware: Keep viewport fixed for IO transaction if num_viewport > 2 Pratyush Anand
2016-07-05 16:23 ` Rob Herring
2016-07-04 16:14 ` [PATCH 2/2] pcie/designware: Exchange viewport of `MEMORYs' and `CFGs/IOs' Pratyush Anand
2016-08-22 18:49 ` Bjorn Helgaas [this message]
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=20160822184915.GH18628@localhost \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=dongbo4@huawei.com \
--cc=jingoohan1@gmail.com \
--cc=linux-pci@vger.kernel.org \
--cc=panand@redhat.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).