linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pratyush Anand <panand@redhat.com>
To: dongbo4@huawei.com, bhelgaas@google.com, jingoohan1@gmail.com
Cc: linux-pci@vger.kernel.org, Pratyush Anand <panand@redhat.com>
Subject: [PATCH 0/2] pcie/designware: Viewport assignment update
Date: Mon,  4 Jul 2016 21:44:41 +0530	[thread overview]
Message-ID: <cover.1467647958.git.panand@redhat.com> (raw)

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(-)

-- 
2.5.5


             reply	other threads:[~2016-07-04 16:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-04 16:14 Pratyush Anand [this message]
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 ` [PATCH 0/2] pcie/designware: Viewport assignment update Bjorn Helgaas

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=cover.1467647958.git.panand@redhat.com \
    --to=panand@redhat.com \
    --cc=bhelgaas@google.com \
    --cc=dongbo4@huawei.com \
    --cc=jingoohan1@gmail.com \
    --cc=linux-pci@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).