Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1343143
| From | Mark Rutland <mark.rutland@arm.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH 2/2] PCI: generic: add description of property "interrupt-skip-mask" |
| Date | 2016-02-25 13:30 +0100 |
| Message-ID | <r63dn-3IP-5@gated-at.bofh.it> (permalink) |
| References | <r62Kl-3eF-1@gated-at.bofh.it> <r62Km-3eF-7@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
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 >
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCH 1/2] pci/of: to support explicitly declare interrupt pins unused Zhen Lei <thunder.leizhen@huawei.com> - 2016-02-25 13:00 +0100
[PATCH 2/2] PCI: generic: add description of property "interrupt-skip-mask" Zhen Lei <thunder.leizhen@huawei.com> - 2016-02-25 13:00 +0100
Re: [PATCH 2/2] PCI: generic: add description of property "interrupt-skip-mask" Mark Rutland <mark.rutland@arm.com> - 2016-02-25 13:30 +0100
Re: [PATCH 2/2] PCI: generic: add description of property "interrupt-skip-mask" "Leizhen (ThunderTown)" <thunder.leizhen@huawei.com> - 2016-02-26 08:30 +0100
Re: [PATCH 2/2] PCI: generic: add description of property "interrupt-skip-mask" Mark Rutland <mark.rutland@arm.com> - 2016-02-26 12:50 +0100
csiph-web