From: Kevin Hao <haokexin@gmail.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: <linux-pci@vger.kernel.org>
Subject: [PATCH 0/2] fix the pci device malfunction if a wrong bus address is assigned by firmware
Date: Tue, 14 May 2013 21:07:54 +0800 [thread overview]
Message-ID: <1368536876-27307-1-git-send-email-haokexin@gmail.com> (raw)
On a fsl p2020rdb-pc board, the onboard pci device is assigned the bus address
0xa0000000 by firmware. But the kernel allocate the cpu address 0xa0000000 ~ 0xbfffffff
to this PCIe controller and use 0xe0000000 ~ 0xdfffffff as its bus address.
In this case the kernel would think that the bus address in this pci device
is correct and leave it unchanged. Then causes this device not work.
Even though this looks like a mismatch of the address space between firmware
and kernel. I think we should detect this kind of error and fix it automatically
if we don't want just to probe only (PCI_PROBE_ONLY is not set).
Kevin Hao (2):
PCI: make pcibios_bus_to_resource return either success or failure
PCI: unset the resource if we can't get the correct CPU address
drivers/pci/host-bridge.c | 5 ++++-
drivers/pci/probe.c | 9 ++++++---
include/linux/pci.h | 2 +-
3 files changed, 11 insertions(+), 5 deletions(-)
--
1.8.1.4
next reply other threads:[~2013-05-14 13:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-14 13:07 Kevin Hao [this message]
2013-05-14 13:07 ` [PATCH 1/2] PCI: make pcibios_bus_to_resource return either success or failure Kevin Hao
2013-05-14 13:07 ` [PATCH 2/2] PCI: unset the resource if we can't get the correct CPU address Kevin Hao
2013-05-16 16:18 ` Liu Jiang
2013-05-17 2:11 ` Kevin Hao
2013-05-17 14:51 ` Liu Jiang
2013-05-19 2:24 ` Kevin Hao
2013-05-20 15:27 ` Liu Jiang
2013-05-23 20:22 ` Bjorn Helgaas
2013-05-24 2:54 ` Kevin Hao
2013-05-24 17:13 ` Bjorn Helgaas
2013-05-25 11:17 ` Kevin Hao
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=1368536876-27307-1-git-send-email-haokexin@gmail.com \
--to=haokexin@gmail.com \
--cc=bhelgaas@google.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).