| Message ID | 1442801587-3812-6-git-send-email-lftan@altera.com (mailing list archive) |
|---|---|
| State | New, archived |
| Delegated to: | Bjorn Helgaas |
| Headers | show |
On 09/20/2015 09:13 PM, Ley Foon Tan wrote: > This patch adds the bindings for Altera PCIe host controller driver and > Altera PCIe MSI driver. > > Signed-off-by: Ley Foon Tan <lftan@altera.com> > --- > .../devicetree/bindings/pci/altera-pcie-msi.txt | 28 +++++++++++++ > .../devicetree/bindings/pci/altera-pcie.txt | 49 ++++++++++++++++++++++ > 2 files changed, 77 insertions(+) > create mode 100644 Documentation/devicetree/bindings/pci/altera-pcie-msi.txt > create mode 100644 Documentation/devicetree/bindings/pci/altera-pcie.txt > > diff --git a/Documentation/devicetree/bindings/pci/altera-pcie-msi.txt b/Documentation/devicetree/bindings/pci/altera-pcie-msi.txt > new file mode 100644 > index 0000000..53ad2388 > --- /dev/null > +++ b/Documentation/devicetree/bindings/pci/altera-pcie-msi.txt > @@ -0,0 +1,28 @@ > +* Altera PCIe MSI controller > + > +Required properties: > +- compatible: should contain "altr,msi-1.0" > +- reg: specifies the physical base address of the controller and > + the length of the memory mapped region. > +- reg-names: must include the following entries: > + "csr": CSR registers > + "vector_slave": vectors slave port region > +- interrupt-parent: interrupt source phandle. > +- interrupts: specifies the interrupt source of the parent interrupt > + controller. The format of the interrupt specifier depends on the > + parent interrupt controller. > +- num-vectors: number of vectors, range 1 to 32. > +- msi-controller: indicates that this is MSI controller node > + > + > +Example > +msi0: msi@0xFF200000 { > + compatible = "altr,msi-1.0"; > + reg = <0xFF200000 0x00000010 > + 0xFF200010 0x00000080>; > + reg-names = "csr", "vector_slave"; > + interrupt-parent = <&hps_0_arm_gic_0>; > + interrupts = <0 42 4>; > + msi-controller = <1>; This should not have a value. > + num-vectors = <32>; > +}; > diff --git a/Documentation/devicetree/bindings/pci/altera-pcie.txt b/Documentation/devicetree/bindings/pci/altera-pcie.txt > new file mode 100644 > index 0000000..4440db1 > --- /dev/null > +++ b/Documentation/devicetree/bindings/pci/altera-pcie.txt > @@ -0,0 +1,49 @@ > +* Altera PCIe controller > + > +Required properties: > +- compatible : should contain "altr,pcie-root-port-1.0" > +- reg: a list of physical base address and length for TXS and CRA. > +- reg-names: must include the following entries: > + "Txs" or "txs": TX slave port region > + "Cra" or "cra": Control register access region Why both cases? Can we please just have one (or none is better IMO). txs contains the config space? > +- interrupt-parent: interrupt source phandle. > +- interrupts: specifies the interrupt source of the parent interrupt controller. > + The format of the interrupt specifier depends on the parent interrupt > + controller. > +- device_type: must be "pci" > +- #address-cells: set to <3> > +- #size-cells: set to <2> > +- #interrupt-cells: set to <1> > +- ranges: describes the translation of addresses for root ports and standard > + PCI regions. > +- interrupt-map-mask and interrupt-map: standard PCI properties to define the > + mapping of the PCIe interface to interrupt numbers. > + > +Optional properties: > +- msi-parent: Link to the hardware entity that serves as the MSI controller for this PCIe > + controller. > +- bus-range: PCI bus numbers covered > + > +Example > + pcie_0: pcie@0xc00000000 { > + compatible = "altr,pcie-root-port-1.0"; > + reg = <0xc0000000 0x20000000>, > + <0xff220000 0x00004000>; > + reg-names = "Txs", "Cra"; > + interrupt-parent = <&hps_0_arm_gic_0>; > + interrupts = <0 40 4>; > + interrupt-controller; > + #interrupt-cells = <1>; > + bus-range = <0x0 0xFF>; > + device_type = "pci"; > + msi-parent = <&msi_to_gic_gen_0>; > + #address-cells = <3>; > + #size-cells = <2>; > + interrupt-map-mask = <0 0 0 7>; > + interrupt-map = <0 0 0 1 &pcie_0 1>, > + <0 0 0 2 &pcie_0 2>, > + <0 0 0 3 &pcie_0 3>, > + <0 0 0 4 &pcie_0 4>; > + ranges = <0x82000000 0x00000000 0x00000000 0xc0000000 0x00000000 0x10000000 > + 0x82000000 0x00000000 0x10000000 0xd0000000 0x00000000 0x10000000>; > + }; > -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Sat, Sep 26, 2015 at 11:55 AM, Rob Herring <robh@kernel.org> wrote: > > On 09/20/2015 09:13 PM, Ley Foon Tan wrote: > > This patch adds the bindings for Altera PCIe host controller driver and > > Altera PCIe MSI driver. > > > > Signed-off-by: Ley Foon Tan <lftan@altera.com> > > --- > > .../devicetree/bindings/pci/altera-pcie-msi.txt | 28 +++++++++++++ > > .../devicetree/bindings/pci/altera-pcie.txt | 49 ++++++++++++++++++++++ > > 2 files changed, 77 insertions(+) > > create mode 100644 Documentation/devicetree/bindings/pci/altera-pcie-msi.txt > > create mode 100644 Documentation/devicetree/bindings/pci/altera-pcie.txt > > > > diff --git a/Documentation/devicetree/bindings/pci/altera-pcie-msi.txt b/Documentation/devicetree/bindings/pci/altera-pcie-msi.txt > > new file mode 100644 > > index 0000000..53ad2388 > > --- /dev/null > > +++ b/Documentation/devicetree/bindings/pci/altera-pcie-msi.txt > > @@ -0,0 +1,28 @@ > > +* Altera PCIe MSI controller > > + > > +Required properties: > > +- compatible: should contain "altr,msi-1.0" > > +- reg: specifies the physical base address of the controller and > > + the length of the memory mapped region. > > +- reg-names: must include the following entries: > > + "csr": CSR registers > > + "vector_slave": vectors slave port region > > +- interrupt-parent: interrupt source phandle. > > +- interrupts: specifies the interrupt source of the parent interrupt > > + controller. The format of the interrupt specifier depends on the > > + parent interrupt controller. > > +- num-vectors: number of vectors, range 1 to 32. > > +- msi-controller: indicates that this is MSI controller node > > + > > + > > +Example > > +msi0: msi@0xFF200000 { > > + compatible = "altr,msi-1.0"; > > + reg = <0xFF200000 0x00000010 > > + 0xFF200010 0x00000080>; > > + reg-names = "csr", "vector_slave"; > > + interrupt-parent = <&hps_0_arm_gic_0>; > > + interrupts = <0 42 4>; > > + msi-controller = <1>; > > This should not have a value. Okay. > > > + num-vectors = <32>; > > +}; > > diff --git a/Documentation/devicetree/bindings/pci/altera-pcie.txt b/Documentation/devicetree/bindings/pci/altera-pcie.txt > > new file mode 100644 > > index 0000000..4440db1 > > --- /dev/null > > +++ b/Documentation/devicetree/bindings/pci/altera-pcie.txt > > @@ -0,0 +1,49 @@ > > +* Altera PCIe controller > > + > > +Required properties: > > +- compatible : should contain "altr,pcie-root-port-1.0" > > +- reg: a list of physical base address and length for TXS and CRA. > > +- reg-names: must include the following entries: > > + "Txs" or "txs": TX slave port region > > + "Cra" or "cra": Control register access region > > Why both cases? Can we please just have one (or none is better IMO). The PCIe IP on different device families use different register names. And our device tree generator will auto generate the register names based on the hardware description name. Too bad we can't change the hardware description names now. > > txs contains the config space? It is not the config space, but a memory slave port. > > > +- interrupt-parent: interrupt source phandle. > > +- interrupts: specifies the interrupt source of the parent interrupt controller. > > + The format of the interrupt specifier depends on the parent interrupt > > + controller. > > +- device_type: must be "pci" > > +- #address-cells: set to <3> > > +- #size-cells: set to <2> > > +- #interrupt-cells: set to <1> > > +- ranges: describes the translation of addresses for root ports and standard > > + PCI regions. > > +- interrupt-map-mask and interrupt-map: standard PCI properties to define the > > + mapping of the PCIe interface to interrupt numbers. > > + > > +Optional properties: > > +- msi-parent: Link to the hardware entity that serves as the MSI controller for this PCIe > > + controller. > > +- bus-range: PCI bus numbers covered > > + > > +Example > > + pcie_0: pcie@0xc00000000 { > > + compatible = "altr,pcie-root-port-1.0"; > > + reg = <0xc0000000 0x20000000>, > > + <0xff220000 0x00004000>; > > + reg-names = "Txs", "Cra"; > > + interrupt-parent = <&hps_0_arm_gic_0>; > > + interrupts = <0 40 4>; > > + interrupt-controller; > > + #interrupt-cells = <1>; > > + bus-range = <0x0 0xFF>; > > + device_type = "pci"; > > + msi-parent = <&msi_to_gic_gen_0>; > > + #address-cells = <3>; > > + #size-cells = <2>; > > + interrupt-map-mask = <0 0 0 7>; > > + interrupt-map = <0 0 0 1 &pcie_0 1>, > > + <0 0 0 2 &pcie_0 2>, > > + <0 0 0 3 &pcie_0 3>, > > + <0 0 0 4 &pcie_0 4>; > > + ranges = <0x82000000 0x00000000 0x00000000 0xc0000000 0x00000000 0x10000000 > > + 0x82000000 0x00000000 0x10000000 0xd0000000 0x00000000 0x10000000>; > > + }; > > > -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Mon, Sep 28, 2015 at 12:38 AM, Ley Foon Tan <lftan@altera.com> wrote: > On Sat, Sep 26, 2015 at 11:55 AM, Rob Herring <robh@kernel.org> wrote: >> >> On 09/20/2015 09:13 PM, Ley Foon Tan wrote: >> > This patch adds the bindings for Altera PCIe host controller driver and >> > Altera PCIe MSI driver. [...] >> > + num-vectors = <32>; >> > +}; >> > diff --git a/Documentation/devicetree/bindings/pci/altera-pcie.txt b/Documentation/devicetree/bindings/pci/altera-pcie.txt >> > new file mode 100644 >> > index 0000000..4440db1 >> > --- /dev/null >> > +++ b/Documentation/devicetree/bindings/pci/altera-pcie.txt >> > @@ -0,0 +1,49 @@ >> > +* Altera PCIe controller >> > + >> > +Required properties: >> > +- compatible : should contain "altr,pcie-root-port-1.0" >> > +- reg: a list of physical base address and length for TXS and CRA. >> > +- reg-names: must include the following entries: >> > + "Txs" or "txs": TX slave port region >> > + "Cra" or "cra": Control register access region >> >> Why both cases? Can we please just have one (or none is better IMO). > The PCIe IP on different device families use different register names. > And our device tree generator will auto generate the register names > based on the hardware description name. Too bad we can't change the > hardware description names now. Okay, your problem to maintain. Hopefully the driver just goes by index then. Strictly speaking, if you have undocumented bindings downstream that is your problem and we don't have to accept them as-is upstream. I'm not going to worry about that here. >> txs contains the config space? > It is not the config space, but a memory slave port. Then where is the config space? It should not be part of "ranges" is all I care about. Rob -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Monday 28 September 2015 12:31:36 Rob Herring wrote: > >> > + > >> > +Required properties: > >> > +- compatible : should contain "altr,pcie-root-port-1.0" > >> > +- reg: a list of physical base address and length for TXS and CRA. > >> > +- reg-names: must include the following entries: > >> > + "Txs" or "txs": TX slave port region > >> > + "Cra" or "cra": Control register access region > >> > >> Why both cases? Can we please just have one (or none is better IMO). > > The PCIe IP on different device families use different register names. > > And our device tree generator will auto generate the register names > > based on the hardware description name. Too bad we can't change the > > hardware description names now. > > Okay, your problem to maintain. Hopefully the driver just goes by index then. > > Strictly speaking, if you have undocumented bindings downstream that > is your problem and we don't have to accept them as-is upstream. I'm > not going to worry about that here. Are they always in the same order? If you don't mandate any names for the registers in the binding but just use them by index, we can keep that bit of ugliness out of the binding and the driver and still be compatible with all the devices. Arnd -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Tue, Sep 29, 2015 at 1:31 AM, Rob Herring <robh@kernel.org> wrote: > On Mon, Sep 28, 2015 at 12:38 AM, Ley Foon Tan <lftan@altera.com> wrote: >> On Sat, Sep 26, 2015 at 11:55 AM, Rob Herring <robh@kernel.org> wrote: >>> >>> On 09/20/2015 09:13 PM, Ley Foon Tan wrote: >>> > This patch adds the bindings for Altera PCIe host controller driver and >>> > Altera PCIe MSI driver. > > [...] > >>> > + num-vectors = <32>; >>> > +}; >>> > diff --git a/Documentation/devicetree/bindings/pci/altera-pcie.txt b/Documentation/devicetree/bindings/pci/altera-pcie.txt >>> > new file mode 100644 >>> > index 0000000..4440db1 >>> > --- /dev/null >>> > +++ b/Documentation/devicetree/bindings/pci/altera-pcie.txt >>> > @@ -0,0 +1,49 @@ >>> > +* Altera PCIe controller >>> > + >>> > +Required properties: >>> > +- compatible : should contain "altr,pcie-root-port-1.0" >>> > +- reg: a list of physical base address and length for TXS and CRA. >>> > +- reg-names: must include the following entries: >>> > + "Txs" or "txs": TX slave port region >>> > + "Cra" or "cra": Control register access region >>> >>> Why both cases? Can we please just have one (or none is better IMO). >> The PCIe IP on different device families use different register names. >> And our device tree generator will auto generate the register names >> based on the hardware description name. Too bad we can't change the >> hardware description names now. > > Okay, your problem to maintain. Hopefully the driver just goes by index then. Okay, we will fix our generator tool to standardize one reg-name case and driver just use one reg-name case as well. > > Strictly speaking, if you have undocumented bindings downstream that > is your problem and we don't have to accept them as-is upstream. I'm > not going to worry about that here. > >>> txs contains the config space? >> It is not the config space, but a memory slave port. > > Then where is the config space? It should not be part of "ranges" is > all I care about. The config space is not part of "ranges". Our IP uses TLP packet to access config space. Regards Ley Foon -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Tue, Sep 29, 2015 at 3:38 AM, Arnd Bergmann <arnd@arndb.de> wrote: > On Monday 28 September 2015 12:31:36 Rob Herring wrote: >> >> > + >> >> > +Required properties: >> >> > +- compatible : should contain "altr,pcie-root-port-1.0" >> >> > +- reg: a list of physical base address and length for TXS and CRA. >> >> > +- reg-names: must include the following entries: >> >> > + "Txs" or "txs": TX slave port region >> >> > + "Cra" or "cra": Control register access region >> >> >> >> Why both cases? Can we please just have one (or none is better IMO). >> > The PCIe IP on different device families use different register names. >> > And our device tree generator will auto generate the register names >> > based on the hardware description name. Too bad we can't change the >> > hardware description names now. >> >> Okay, your problem to maintain. Hopefully the driver just goes by index then. >> >> Strictly speaking, if you have undocumented bindings downstream that >> is your problem and we don't have to accept them as-is upstream. I'm >> not going to worry about that here. > > Are they always in the same order? If you don't mandate any names for the > registers in the binding but just use them by index, we can keep that > bit of ugliness out of the binding and the driver and still be compatible > with all the devices. Too bad the order might change in future devices. We will fix the tool, so only have one reg-name case. Regards Ley Foon -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Friday 02 October 2015 15:53:44 Ley Foon Tan wrote: > > Strictly speaking, if you have undocumented bindings downstream that > > is your problem and we don't have to accept them as-is upstream. I'm > > not going to worry about that here. > > > >>> txs contains the config space? > >> It is not the config space, but a memory slave port. > > > > Then where is the config space? It should not be part of "ranges" is > > all I care about. > The config space is not part of "ranges". Our IP uses TLP packet to > access config space. > It took me a bit to figure out what you mean here. To save others from reading the source, here is what I found: * The config space is accessed indirectly through registers from the "cra" register range, which is the right approach according to the point that Rob made. * hardware-wise this basically looks like bit-banged PCIe, which is both awesome and scary ;-) Arnd -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Fri, 2 Oct 2015 23:56:37 +0200 Arnd Bergmann <arnd@arndb.de> wrote: > On Friday 02 October 2015 15:53:44 Ley Foon Tan wrote: > > > Strictly speaking, if you have undocumented bindings downstream that > > > is your problem and we don't have to accept them as-is upstream. I'm > > > not going to worry about that here. > > > > > >>> txs contains the config space? > > >> It is not the config space, but a memory slave port. > > > > > > Then where is the config space? It should not be part of "ranges" is > > > all I care about. > > The config space is not part of "ranges". Our IP uses TLP packet to > > access config space. > > > > It took me a bit to figure out what you mean here. To save others > from reading the source, here is what I found: > > * The config space is accessed indirectly through registers from the > "cra" register range, which is the right approach according to the > point that Rob made. > * hardware-wise this basically looks like bit-banged PCIe, which is > both awesome and scary ;-) drivers/pcie/host/pcie-host-gpio.c anyone? ;-) M.
On Sat, Oct 3, 2015 at 5:56 AM, Arnd Bergmann <arnd@arndb.de> wrote: > On Friday 02 October 2015 15:53:44 Ley Foon Tan wrote: >> > Strictly speaking, if you have undocumented bindings downstream that >> > is your problem and we don't have to accept them as-is upstream. I'm >> > not going to worry about that here. >> > >> >>> txs contains the config space? >> >> It is not the config space, but a memory slave port. >> > >> > Then where is the config space? It should not be part of "ranges" is >> > all I care about. >> The config space is not part of "ranges". Our IP uses TLP packet to >> access config space. >> > > It took me a bit to figure out what you mean here. To save others > from reading the source, here is what I found: > > * The config space is accessed indirectly through registers from the > "cra" register range, which is the right approach according to the > point that Rob made. You are right. > * hardware-wise this basically looks like bit-banged PCIe, which is > both awesome and scary ;-) -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
diff --git a/Documentation/devicetree/bindings/pci/altera-pcie-msi.txt b/Documentation/devicetree/bindings/pci/altera-pcie-msi.txt new file mode 100644 index 0000000..53ad2388 --- /dev/null +++ b/Documentation/devicetree/bindings/pci/altera-pcie-msi.txt @@ -0,0 +1,28 @@ +* Altera PCIe MSI controller + +Required properties: +- compatible: should contain "altr,msi-1.0" +- reg: specifies the physical base address of the controller and + the length of the memory mapped region. +- reg-names: must include the following entries: + "csr": CSR registers + "vector_slave": vectors slave port region +- interrupt-parent: interrupt source phandle. +- interrupts: specifies the interrupt source of the parent interrupt + controller. The format of the interrupt specifier depends on the + parent interrupt controller. +- num-vectors: number of vectors, range 1 to 32. +- msi-controller: indicates that this is MSI controller node + + +Example +msi0: msi@0xFF200000 { + compatible = "altr,msi-1.0"; + reg = <0xFF200000 0x00000010 + 0xFF200010 0x00000080>; + reg-names = "csr", "vector_slave"; + interrupt-parent = <&hps_0_arm_gic_0>; + interrupts = <0 42 4>; + msi-controller = <1>; + num-vectors = <32>; +}; diff --git a/Documentation/devicetree/bindings/pci/altera-pcie.txt b/Documentation/devicetree/bindings/pci/altera-pcie.txt new file mode 100644 index 0000000..4440db1 --- /dev/null +++ b/Documentation/devicetree/bindings/pci/altera-pcie.txt @@ -0,0 +1,49 @@ +* Altera PCIe controller + +Required properties: +- compatible : should contain "altr,pcie-root-port-1.0" +- reg: a list of physical base address and length for TXS and CRA. +- reg-names: must include the following entries: + "Txs" or "txs": TX slave port region + "Cra" or "cra": Control register access region +- interrupt-parent: interrupt source phandle. +- interrupts: specifies the interrupt source of the parent interrupt controller. + The format of the interrupt specifier depends on the parent interrupt + controller. +- device_type: must be "pci" +- #address-cells: set to <3> +- #size-cells: set to <2> +- #interrupt-cells: set to <1> +- ranges: describes the translation of addresses for root ports and standard + PCI regions. +- interrupt-map-mask and interrupt-map: standard PCI properties to define the + mapping of the PCIe interface to interrupt numbers. + +Optional properties: +- msi-parent: Link to the hardware entity that serves as the MSI controller for this PCIe + controller. +- bus-range: PCI bus numbers covered + +Example + pcie_0: pcie@0xc00000000 { + compatible = "altr,pcie-root-port-1.0"; + reg = <0xc0000000 0x20000000>, + <0xff220000 0x00004000>; + reg-names = "Txs", "Cra"; + interrupt-parent = <&hps_0_arm_gic_0>; + interrupts = <0 40 4>; + interrupt-controller; + #interrupt-cells = <1>; + bus-range = <0x0 0xFF>; + device_type = "pci"; + msi-parent = <&msi_to_gic_gen_0>; + #address-cells = <3>; + #size-cells = <2>; + interrupt-map-mask = <0 0 0 7>; + interrupt-map = <0 0 0 1 &pcie_0 1>, + <0 0 0 2 &pcie_0 2>, + <0 0 0 3 &pcie_0 3>, + <0 0 0 4 &pcie_0 4>; + ranges = <0x82000000 0x00000000 0x00000000 0xc0000000 0x00000000 0x10000000 + 0x82000000 0x00000000 0x10000000 0xd0000000 0x00000000 0x10000000>; + };
This patch adds the bindings for Altera PCIe host controller driver and Altera PCIe MSI driver. Signed-off-by: Ley Foon Tan <lftan@altera.com> --- .../devicetree/bindings/pci/altera-pcie-msi.txt | 28 +++++++++++++ .../devicetree/bindings/pci/altera-pcie.txt | 49 ++++++++++++++++++++++ 2 files changed, 77 insertions(+) create mode 100644 Documentation/devicetree/bindings/pci/altera-pcie-msi.txt create mode 100644 Documentation/devicetree/bindings/pci/altera-pcie.txt