Stuart-B08248
> Subject: Re: [PATCH 2/3] Docs: dt: Add PCI MSI map bindings
>
> On Fri, Sep 04, 2015 at 11:33:35PM +0100, David Daney wrote:
> > Hi Mark,
>
> Hi David,
>
> > I now have a prototype implementation for irq-gic-v3-its.c that is using
> > this bind
On Fri, Sep 04, 2015 at 11:33:35PM +0100, David Daney wrote:
> Hi Mark,
Hi David,
> I now have a prototype implementation for irq-gic-v3-its.c that is using
> this binding on Cavium's ThunderX platform.
>
> Q: Have you guys had any more thoughts on this that might require
> changing the bindin
> > +PCI root complex
> > +
> > +
> > +Optional properties
> > +---
> > +
> > +- msi-map: Maps a Requester ID to an MSI controller and associated
> > + msi-specifier data. The property is an arbitrary number of tuples of
> > + (rid-base,msi-controller,msi-base,leng
Hi Mark,
First of all: Thanks for working on this.
I now have a prototype implementation for irq-gic-v3-its.c that is using
this binding on Cavium's ThunderX platform.
Q: Have you guys had any more thoughts on this that might require
changing the binding?
If not, I will be sending out my
.@lists.infradead.org;
> majun...@huawei.com; Yoder Stuart-B08248
> Subject: Re: [PATCH 2/3] Docs: dt: Add PCI MSI map bindings
>
> On Wed, Aug 05, 2015 at 05:39:33PM +0100, Varun Sethi wrote:
> > Hi Mark
> > Thanks for the patch. Please find my comment inline.
>
.kernel.org;
> dda...@caviumnetworks.com; iommu@lists.linux-foundation.org;
> tirumalesh.chalama...@caviumnetworks.com;
> laurent.pinch...@ideasonboard.com; thunder.leiz...@huawei.com;
> tred...@nvidia.com; linux-arm-
> ker...@lists.infradead.org; majun...@huawei.com
> Subject: Re: [PATCH 2/3
[...]
> > +PCI root complex
> > +
> > +
> > +Optional properties
> > +---
> > +
> > +- msi-map: Maps a Requester ID to an MSI controller and associated
> > + msi-specifier data. The property is an arbitrary number of tuples of
> > + (rid-base,msi-controller,msi-ba
r...@vger.kernel.org; dda...@caviumnetworks.com; iommu@lists.linux-
> > foundation.org; tirumalesh.chalama...@caviumnetworks.com;
> > laurent.pinch...@ideasonboard.com; thunder.leiz...@huawei.com;
> > tred...@nvidia.com; linux-arm-ker...@lists.infradead.org;
> > majun...@huawei.com
> >
> From: Mark Rutland
> Date: Thu, Jul 23, 2015 at 11:52 AM
[cut]
> diff --git a/Documentation/devicetree/bindings/pci/pci-msi.txt
> b/Documentation/devicetree/bindings/pci/pci-msi.txt
> new file mode 100644
> index 000..9b3cc81
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/pci/pc
rent.pinch...@ideasonboard.com; thunder.leiz...@huawei.com;
> tred...@nvidia.com; linux-arm-ker...@lists.infradead.org;
> majun...@huawei.com
> Subject: [PATCH 2/3] Docs: dt: Add PCI MSI map bindings
>
> Currently msi-parent is used by a few bindings to describe the relationship
> betwee
> > +Example (5)
> > +===
> > +
> > +/ {
> > + #address-cells = <1>;
> > + #size-cells = <1>;
> > +
> > + msi_a: msi-controller@a {
> > + reg = <0xa 0x1>;
> > + compatible = "vendor,some-controller";
> > + msi-controller;
> > + #msi-cells = <1>;
On 23/07/15 17:52, Mark Rutland wrote:
> Currently msi-parent is used by a few bindings to describe the
> relationship between a PCI root complex and a single MSI controller, but
> this property does not have a generic binding document.
>
> Additionally, msi-parent is insufficient to describe more
looks good. possible to describe the chip we have.
> On Jul 23, 2015, at 9:52 AM, Mark Rutland wrote:
>
> Currently msi-parent is used by a few bindings to describe the
> relationship between a PCI root complex and a single MSI controller, but
> this property does not have a generic binding docum
Currently msi-parent is used by a few bindings to describe the
relationship between a PCI root complex and a single MSI controller, but
this property does not have a generic binding document.
Additionally, msi-parent is insufficient to describe more complex
relationships between MSI controllers an
14 matches
Mail list logo
