| Message ID | 1456401208-10136-2-git-send-email-thunder.leizhen@huawei.com (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
Hi, In future, please send the binding document first in a series, per point 3 of Documentation/devicetree/bindings/submitting-patches.txt. It makes review easier/faster. On Thu, Feb 25, 2016 at 07:53:28PM +0800, Zhen Lei wrote: > Interrupt Pin register is read-only and optional. Some pci devices may use > msi/msix but leave the value of Interrupt Pin non-zero. Is that permitted by the spec? Surely 'optional' means it must be zero if not implemented? > In this case, the driver will print information as below: pci > 0000:40:00.0: of_irq_parse_pci() failed with rc=-22 > > It's easily lead to misinterpret. If this is limited to a subset of devices which we know are broken in this regard, can we not handle these cases explicitly? > Signed-off-by: Zhen Lei <thunder.leizhen@huawei.com> > --- > Documentation/devicetree/bindings/pci/host-generic-pci.txt | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/Documentation/devicetree/bindings/pci/host-generic-pci.txt b/Documentation/devicetree/bindings/pci/host-generic-pci.txt > index 3f1d3fc..0f10978 100644 > --- a/Documentation/devicetree/bindings/pci/host-generic-pci.txt > +++ b/Documentation/devicetree/bindings/pci/host-generic-pci.txt > @@ -70,6 +70,8 @@ Practice: Interrupt Mapping' and requires the following properties: > > - interrupt-map-mask : <see aforementioned specification> > > +- interrupt-skip-mask: Explicitly declare which pci devices only use msi/msix > +but leave the value of Interrupt Pin non-zero. Unlike the rest of the interrupt mapping properties, this is not described in `Open Firmware Recommended Practice: Interrupt Mapping'. This needs a far more complete description. This also doesn't strike me as th right approach. The interrupt-map-mask property describe as relationship between the host-controller-provided interrupt lines and endpoints, while this seems to be a bug completely contained within an endpoint. Thanks, Mark. > > Example: > > -- > 2.5.0 > > > -- > To unsubscribe from this list: send the line "unsubscribe devicetree" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html >
On 2016/2/25 20:20, Mark Rutland wrote: > Hi, > > In future, please send the binding document first in a series, per point > 3 of Documentation/devicetree/bindings/submitting-patches.txt. It makes > review easier/faster. Thank you for your reminding. > > On Thu, Feb 25, 2016 at 07:53:28PM +0800, Zhen Lei wrote: >> Interrupt Pin register is read-only and optional. Some pci devices may use >> msi/msix but leave the value of Interrupt Pin non-zero. > > Is that permitted by the spec? Surely 'optional' means it must be zero > if not implemented? In <PCI Local Bus Specification Revision 3.0>: Devices (or device functions) that do not use an interrupt pin must put a 0 in this register. This register is read-only. So, do you think this is a hardware bug? But these pci-devices are not produced by our company. In function init_service_irqs, it try msix first, then msi, Interrupt PIN is the last attemption. But of_irq_parse_pci() happened before this. In fact, there also a familiar problem exist. As below: pci 0000:42:00.0: BAR 7: no space for [io size 0x1000] pci 0000:42:00.0: BAR 7: failed to assign [io size 0x1000] There no "io space" on arm64, maybe only exist on X86. And the Memory Space Indicator also read-only in BAR register. > >> In this case, the driver will print information as below: pci >> 0000:40:00.0: of_irq_parse_pci() failed with rc=-22 >> >> It's easily lead to misinterpret. > > If this is limited to a subset of devices which we know are broken in > this regard, can we not handle these cases explicitly? Actually, we have another way to block this warning. Use "interrupt-map" to map it to a pesudo IRQ. But I think it will also be misunderstanded. > >> Signed-off-by: Zhen Lei <thunder.leizhen@huawei.com> >> --- >> Documentation/devicetree/bindings/pci/host-generic-pci.txt | 2 ++ >> 1 file changed, 2 insertions(+) >> >> diff --git a/Documentation/devicetree/bindings/pci/host-generic-pci.txt b/Documentation/devicetree/bindings/pci/host-generic-pci.txt >> index 3f1d3fc..0f10978 100644 >> --- a/Documentation/devicetree/bindings/pci/host-generic-pci.txt >> +++ b/Documentation/devicetree/bindings/pci/host-generic-pci.txt >> @@ -70,6 +70,8 @@ Practice: Interrupt Mapping' and requires the following properties: >> >> - interrupt-map-mask : <see aforementioned specification> >> >> +- interrupt-skip-mask: Explicitly declare which pci devices only use msi/msix >> +but leave the value of Interrupt Pin non-zero. > > Unlike the rest of the interrupt mapping properties, this is not > described in `Open Firmware Recommended Practice: Interrupt Mapping'. > > This needs a far more complete description. > > This also doesn't strike me as th right approach. The interrupt-map-mask > property describe as relationship between the host-controller-provided > interrupt lines and endpoints, while this seems to be a bug completely > contained within an endpoint. In <host-generic-pci.txt>: // PCI_DEVICE(3) INT#(1) CONTROLLER(PHANDLE) CONTROLLER_DATA(3) interrupt-map = < 0x0 0x0 0x0 0x1 &gic 0x0 0x4 0x1 PCI_DEVICE contain 3 cells. But only the first one be used in function of_irq_parse_pci. laddr[0] = cpu_to_be32((pdev->bus->number << 16) | (pdev->devfn << 8)); laddr[1] = laddr[2] = cpu_to_be32(0); And for INT#, I don't think there will some Pins used but others unused on a pci-device. So I can ommit it. So, only laddr[0] mask need to be described. > > Thanks, > Mark. > >> >> Example: >> >> -- >> 2.5.0 >> >> >> -- >> To unsubscribe from this list: send the line "unsubscribe devicetree" in >> the body of a message to majordomo@vger.kernel.org >> More majordomo info at http://vger.kernel.org/majordomo-info.html >> > > . >
On Fri, Feb 26, 2016 at 03:19:55PM +0800, Leizhen (ThunderTown) wrote: > > On 2016/2/25 20:20, Mark Rutland wrote: > > Hi, > > > > In future, please send the binding document first in a series, per point > > 3 of Documentation/devicetree/bindings/submitting-patches.txt. It makes > > review easier/faster. > Thank you for your reminding. > > > On Thu, Feb 25, 2016 at 07:53:28PM +0800, Zhen Lei wrote: > >> Interrupt Pin register is read-only and optional. Some pci devices may use > >> msi/msix but leave the value of Interrupt Pin non-zero. > > > > Is that permitted by the spec? Surely 'optional' means it must be zero > > if not implemented? > > In <PCI Local Bus Specification Revision 3.0>: > Devices (or device functions) that do not use an interrupt pin must put a 0 in this register. This register is read-only. > > So, do you think this is a hardware bug? Per the above, that does appear to be the case. > But these pci-devices are not produced by our company. > > In function init_service_irqs, it try msix first, then msi, Interrupt > PIN is the last attemption. But of_irq_parse_pci() happened before > this. I assume that for devices with 0 in this register we do not produce a warning. So where do we check the interrupt pin register, and when does this happen relative to of_irq_parse_pci such that we do not produce that warning? I als assume that all instances of these particular devices broken in this regard? If so, I think we need to identify them by Device ID and Vendor ID, and treat them as if the interrupt pin register read as zero, in the place we normally check the interrupt pin register. Note that this is completely independent of the RID/BDF, so the interrupt-*-mask approach is insufficient. > In fact, there also a familiar problem exist. As below: > pci 0000:42:00.0: BAR 7: no space for [io size 0x1000] > pci 0000:42:00.0: BAR 7: failed to assign [io size 0x1000] > > There no "io space" on arm64, maybe only exist on X86. And the Memory Space Indicator also read-only in BAR register. I'm not entirely sure, but I thought we handled the PCI I/O space as an MMIO region on ARM64. Do you have many devices/functions attached? It may be that our VA carveout of 16M is too small. This is probably worth a separate thread. > >> In this case, the driver will print information as below: pci > >> 0000:40:00.0: of_irq_parse_pci() failed with rc=-22 > >> > >> It's easily lead to misinterpret. > > > > If this is limited to a subset of devices which we know are broken in > > this regard, can we not handle these cases explicitly? > Actually, we have another way to block this warning. Use "interrupt-map" to map it to a pesudo IRQ. But I think it will also be misunderstanded. This is very fragile, as it depends on the RIDs/addresses assigned by the host controller. If devices are plugged into different slots then that could change, you get the warning, and other devices may be prevented from using wired interrupts. As I mentioned above, I think we need to identify the buggy devices by ID, rather than by topology. Thanks, Mark.
diff --git a/Documentation/devicetree/bindings/pci/host-generic-pci.txt b/Documentation/devicetree/bindings/pci/host-generic-pci.txt index 3f1d3fc..0f10978 100644 --- a/Documentation/devicetree/bindings/pci/host-generic-pci.txt +++ b/Documentation/devicetree/bindings/pci/host-generic-pci.txt @@ -70,6 +70,8 @@ Practice: Interrupt Mapping' and requires the following properties: - interrupt-map-mask : <see aforementioned specification> +- interrupt-skip-mask: Explicitly declare which pci devices only use msi/msix +but leave the value of Interrupt Pin non-zero. Example:
Interrupt Pin register is read-only and optional. Some pci devices may use msi/msix but leave the value of Interrupt Pin non-zero. In this case, the driver will print information as below: pci 0000:40:00.0: of_irq_parse_pci() failed with rc=-22 It's easily lead to misinterpret. Signed-off-by: Zhen Lei <thunder.leizhen@huawei.com> --- Documentation/devicetree/bindings/pci/host-generic-pci.txt | 2 ++ 1 file changed, 2 insertions(+) -- 2.5.0