linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rafał Miłecki" <zajec5@gmail.com>
To: Bjorn Helgaas <bhelgaas@google.com>, Ray Jui <rjui@broadcom.com>,
	Scott Branden <sbranden@broadcom.com>,
	Jon Mason <jonmason@broadcom.com>
Cc: linux-pci@vger.kernel.org, "Hauke Mehrtens" <hauke@hauke-m.de>,
	linux-arm-kernel@lists.infradead.org,
	bcm-kernel-feedback-list@broadcom.com,
	"Rafał Miłecki" <zajec5@gmail.com>
Subject: [PATCH 2/2] PCI: iproc: Enable hooking abort handler on devices with bcma
Date: Sat,  9 Apr 2016 23:50:24 +0200	[thread overview]
Message-ID: <1460238624-2086-2-git-send-email-zajec5@gmail.com> (raw)
In-Reply-To: <1460238624-2086-1-git-send-email-zajec5@gmail.com>

This seems to be mostly needed by devices with more than 2 devices, e.g.
Netgear R8000 which is known to suffer from this issue.

Signed-off-by: Rafał Miłecki <zajec5@gmail.com>
---
 drivers/pci/host/pcie-iproc-bcma.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/pci/host/pcie-iproc-bcma.c b/drivers/pci/host/pcie-iproc-bcma.c
index 0d7bee4..f9ee077 100644
--- a/drivers/pci/host/pcie-iproc-bcma.c
+++ b/drivers/pci/host/pcie-iproc-bcma.c
@@ -56,6 +56,7 @@ static int iproc_pcie_bcma_probe(struct bcma_device *bdev)
 
 	pcie->base = bdev->io_addr;
 	pcie->base_addr = bdev->addr;
+	pcie->hook_abort_handler = true;
 
 	res_mem.start = bdev->addr_s[0];
 	res_mem.end = bdev->addr_s[0] + SZ_128M - 1;
-- 
1.8.4.5


  reply	other threads:[~2016-04-09 21:50 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-09 21:50 [PATCH 1/2] PCI: iproc: Support DT property for ignoring aborts when probing Rafał Miłecki
2016-04-09 21:50 ` Rafał Miłecki [this message]
2016-04-10  2:59 ` kbuild test robot
2016-04-10 10:54   ` Rafał Miłecki
2016-04-11  1:43 ` Florian Fainelli
     [not found]   ` <4768648c-841b-490d-a752-f31cba545f74@broadcom.com>
2016-04-11 21:55     ` Florian Fainelli
     [not found]       ` <ccabf53c-c035-be4b-a016-389bb7531557@broadcom.com>
     [not found]         ` <570C24B3.4080104@broadcom.com>
     [not found]           ` <18045be8-9ee3-7644-6fbb-d352e107d111@broadcom.com>
2016-04-11 22:41             ` Florian Fainelli
     [not found]               ` <0464ed02-5d41-f111-b8c1-aa9aa638c872@broadcom.com>
2016-04-11 22:51                 ` Florian Fainelli
2016-04-17 15:54                   ` Rafał Miłecki
2016-04-17 14:02   ` Arnd Bergmann
     [not found]     ` <ae624772-9306-50ee-3dc1-df8156eaa16d@broadcom.com>
     [not found]       ` <acccb06d-14b9-33bd-466b-47dd3689e537@broadcom.com>
2016-10-28 15:31         ` Rafał Miłecki
     [not found]           ` <1b58db80-c9ff-d4d6-0df1-d80d1c03bc45@broadcom.com>
2016-10-28 17:04             ` Florian Fainelli
2016-10-29  6:14             ` Rafał Miłecki
2016-04-11  8:57 ` Mark Rutland
2016-04-17 15:43   ` Rafał Miłecki

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=1460238624-2086-2-git-send-email-zajec5@gmail.com \
    --to=zajec5@gmail.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=bhelgaas@google.com \
    --cc=hauke@hauke-m.de \
    --cc=jonmason@broadcom.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=rjui@broadcom.com \
    --cc=sbranden@broadcom.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).