Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1255827 > unrolled thread
| Started by | Jisheng Zhang <jszhang@marvell.com> |
|---|---|
| First post | 2015-10-26 12:10 +0100 |
| Last post | 2015-10-26 12:10 +0100 |
| Articles | 1 — 1 participant |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
[RFC PATCH 2/3] PCI: tegra: generate proper configuration access cycles Jisheng Zhang <jszhang@marvell.com> - 2015-10-26 12:10 +0100
| From | Jisheng Zhang <jszhang@marvell.com> |
|---|---|
| Date | 2015-10-26 12:10 +0100 |
| Subject | [RFC PATCH 2/3] PCI: tegra: generate proper configuration access cycles |
| Message-ID | <qnNP4-7uf-37@gated-at.bofh.it> |
Inspired by Russell King's patch[1], I found current tegra also has the
same issue of "reading 32-bits from the command register, modifying the
command register, and then writing it back has the effect of clearing
any status bits that were indicating at that time" as pointed out by
Russell. This patch fix this issue by using the pci_generic_config_write.
[1]http://www.spinics.net/lists/linux-pci/msg44869.html
Signed-off-by: Jisheng Zhang <jszhang@marvell.com>
---
drivers/pci/host/pci-tegra.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/pci/host/pci-tegra.c b/drivers/pci/host/pci-tegra.c
index 81df0c1..d926e3e 100644
--- a/drivers/pci/host/pci-tegra.c
+++ b/drivers/pci/host/pci-tegra.c
@@ -483,7 +483,7 @@ static void __iomem *tegra_pcie_conf_address(struct pci_bus *bus,
static struct pci_ops tegra_pcie_ops = {
.map_bus = tegra_pcie_conf_address,
.read = pci_generic_config_read32,
- .write = pci_generic_config_write32,
+ .write = pci_generic_config_write,
};
static unsigned long tegra_pcie_port_get_pex_ctrl(struct tegra_pcie_port *port)
--
2.6.2
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Back to top | Article view | linux.kernel
csiph-web