From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 2/3] ARM: dts: imx6: extend PCIe interrupt list for MSI
Date: Fri, 28 Feb 2014 11:22:26 +0100 [thread overview]
Message-ID: <59506012.lKQmfIR71j@wuerfel> (raw)
In-Reply-To: <1393582776.5219.2.camel@weser.hi.pengutronix.de>
On Friday 28 February 2014 11:19:36 Lucas Stach wrote:
> Am Donnerstag, den 27.02.2014, 17:44 +0100 schrieb Arnd Bergmann:
> > On Thursday 27 February 2014 17:41:44 Lucas Stach wrote:
> > > num-lanes = <1>;
> > > - interrupts = <0 123 0x04>;
> > > + interrupt-names = "inta", "intb", "intc", "intd/msi";
> > > + interrupts = <0 123 0x04>, <0 122 0x04>, <0 121 0x04>, <0 120 0x04>;
> > > clocks = <&clks 189>, <&clks 187>, <&clks 206>, <&clks 144>;
> > >
> >
> > The standard PCI interrupts should not be listed here, you need to
> > put them into the "interrupt-map" property so the of_irq_parse_and_map_pci()
> > function can translate them.
> >
>
> So as INTA is already listed and implemented in the driver this way,
> this means the binding is totally bogus (taking into account that it
> didn't match the documented designware binding in more places).
>
> I wonder if we should just break the binding to sort things out, given
> that there are not that many users of imx-pcie yet.
That may be best, yes. If we have to provide backwards compatibility,
the driver can have a fallback for the case where no interrupt-map
property is present, but it should not try to handle multiple
interrupt lines that way, only the trivial case where you have a single
IntA line for all devices.
Arnd
next prev parent reply other threads:[~2014-02-28 10:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-27 16:41 [PATCH v3 1/3] PCI: designware: split samsung and fsl bindings Lucas Stach
2014-02-27 16:41 ` [PATCH v3 2/3] ARM: dts: imx6: extend PCIe interrupt list for MSI Lucas Stach
2014-02-27 16:44 ` Arnd Bergmann
2014-02-28 10:19 ` Lucas Stach
2014-02-28 10:22 ` Arnd Bergmann [this message]
2014-02-27 16:41 ` [PATCH v3 3/3] PCI: imx6: add support " Lucas Stach
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=59506012.lKQmfIR71j@wuerfel \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.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