Thread (24 messages) 24 messages, 4 authors, 2015-10-15

[PATCH v10 4/6] PCI: hisi: Add PCIe host support for HiSilicon SoC Hip05

From: arnd@arndb.de (Arnd Bergmann)
Date: 2015-10-13 11:13:11
Also in: linux-devicetree, linux-pci, lkml

On Monday 12 October 2015 16:35:45 Bjorn Helgaas wrote:
quoted
+{
+     u64 addr;
+     struct device_node *msi_node;
+     struct resource res;
+     struct device_node *np = pp->dev->of_node;
+     struct hisi_pcie *pcie = to_hisi_pcie(pp);
+
+     msi_node = of_parse_phandle(np, "msi-parent", 0);
+     if (!msi_node) {
+             dev_err(pp->dev, "failed to find msi-parent\n");
+             return -EINVAL;
+     }
+     of_address_to_resource(msi_node, 0, &res);
Does this use the "msi-parent" node in the same way as other drivers
do?  I'm sure there must be other places where we extract struct
resource information from an "msi-parent" node, but I don't see them.

I'm trying to verify that this isn't some kind of incompatible
extension of the "msi-parent" property.  I cc'd Arnd and Rob (DT
experts).
This is not ok, what this does is that it relies on a particular
implementation of the MSI controller and directly accesses its
registers.

Instead, it should reference only the msi irq domain and let the
driver for the MSI controller access the registers. Otherwise this
code has to be rewritten once the same PCI host code appears in
a machine that has a real GICv2m or GICv3.

	Arnd
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help