lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAD=FV=Vw_+HJc+onc6h+b3Fv5faRc0+=W+e3sJv2OLQJeysQLQ@mail.gmail.com>
Date:	Thu, 16 Jun 2016 08:31:25 -0700
From:	Doug Anderson <dianders@...omium.org>
To:	Marc Zyngier <marc.zyngier@....com>
Cc:	Shawn Lin <shawn.lin@...k-chips.com>,
	Bjorn Helgaas <bhelgaas@...gle.com>, linux-pci@...r.kernel.org,
	Arnd Bergmann <arnd@...db.de>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"open list:ARM/Rockchip SoC..." <linux-rockchip@...ts.infradead.org>,
	Heiko Stuebner <heiko@...ech.de>,
	Wenrui Li <wenrui.li@...k-chips.com>,
	Rob Herring <robh+dt@...nel.org>,
	"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>
Subject: Re: [PATCH v2 1/2] Documentation: bindings: add dt doc for Rockchip
 PCIe controller

Marc,

On Fri, Jun 10, 2016 at 12:32 AM, Marc Zyngier <marc.zyngier@....com> wrote:
> On Wed, 8 Jun 2016 16:05:17 +0800
> Shawn Lin <shawn.lin@...k-chips.com> wrote:
>
>> This patch adds a binding that describes the Rockchip PCIe controller
>> found on Rockchip SoCs PCIe interface.
>>
>> Signed-off-by: Shawn Lin <shawn.lin@...k-chips.com>
>>
>> ---
>>
>> Changes in v2:
>> - fix lots clk/reset stuff suggested by Heiko
>> - remove msi-parent and add msi-map suggested by Marc
>
> I noticed this ^^^^ ...
>
>> - drop phy related stuff
>> - some others minor fixes
>>
>>  .../devicetree/bindings/pci/rockchip-pcie.txt      | 86 ++++++++++++++++++++++
>>  1 file changed, 86 insertions(+)
>>  create mode 100644 Documentation/devicetree/bindings/pci/rockchip-pcie.txt
>>
>> diff --git a/Documentation/devicetree/bindings/pci/rockchip-pcie.txt b/Documentation/devicetree/bindings/pci/rockchip-pcie.txt
>> new file mode 100644
>> index 0000000..eb92e29
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/pci/rockchip-pcie.txt
>> @@ -0,0 +1,86 @@
>> +* Rockchip AXI PCIe Root Port Bridge DT description
>> +
>> +Required properties:
>> +- #address-cells: Address representation for root ports, set to <3>
>> +- #size-cells: Size representation for root ports, set to <2>
>> +- #interrupt-cells: specifies the number of cells needed to encode an
>> +             interrupt source. The value must be 1.
>> +- compatible: Should contain "rockchip,rk3399-pcie"
>> +- reg: Two register ranges as listed in the reg-names property
>> +- reg-names: Must include the following names
>> +     - "axi-base"
>> +     - "apb-base"
>> +- clocks: Must contain an entry for each entry in clock-names.
>> +             See ../clocks/clock-bindings.txt for details.
>> +- clock-names: Must include the following entries:
>> +     - "aclk"
>> +     - "aclk-perf"
>> +     - "hclk"
>> +     - "pm"
>> +- phys: From PHY bindings: Phandle for the Generic PHY for PCIe.
>> +- phy-names:  MUST be "pcie-phy".
>> +- interrupts: Three interrupt entries must be specified.
>> +- interrupt-names: Must include the following names
>> +     - "sys"
>> +     - "legacy"
>> +     - "client"
>> +- resets: Must contain five entries for each entry in reset-names.
>> +        See ../reset/reset.txt for details.
>> +- reset-names: Must include the following names
>> +     - "core"
>> +     - "mgmt"
>> +     - "mgmt-sticky"
>> +     - "pipe"
>> +- pinctrl-names : The pin control state names
>> +- pinctrl-0: The "default" pinctrl state
>> +- interrupt-map-mask and interrupt-map: standard PCI properties
>> +- interrupt-controller: identifies the node as an interrupt controller
>> +
>> +Optional Property:
>> +- ep-gpios: contain the entry for pre-reset gpio
>> +- num-lanes: number of lanes to use
>> +- vpcie3v3-supply: The phandle to the 3.3v regulator to use for pcie. If this
>> +  is specified we'll defer probe until we can find this regulator.
>> +- vpcie1v8-supply: The phandle to the 1.8v regulator to use for pcie. If this
>> +  is specified we'll defer probe until we can find this regulator.
>> +- vpcie0v9-supply: The phandle to the 0.9v regulator to use for pcie. If this
>> +  is specified we'll defer probe until we can find this regulator.
>> +
>> +Example:
>> +
>> +pcie0: pcie@...00000 {
>> +     compatible = "rockchip,rk3399-pcie";
>> +     #address-cells = <3>;
>> +     #size-cells = <2>;
>> +     clocks = <&cru ACLK_PCIE>, <&cru ACLK_PERF_PCIE>,
>> +              <&cru PCLK_PCIE>;
>> +     clock-names = "aclk", "aclk-perf",
>> +                   "hclk";
>> +     bus-range = <0x0 0x1>;
>> +     interrupts = <GIC_SPI 49 IRQ_TYPE_LEVEL_HIGH>, <GIC_SPI 50 IRQ_TYPE_LEVEL_HIGH>,
>> +                  <GIC_SPI 51 IRQ_TYPE_LEVEL_HIGH>;
>> +     interrupt-names: "sys", "legacy", "client";
>> +     assigned-clocks = <&cru SCLK_PCIEPHY_REF>;
>> +     assigned-clock-parents = <&cru SCLK_PCIEPHY_REF100M>;
>> +     assigned-clock-rates = <100000000>;
>> +     ep-gpios = <&gpio3 13 GPIO_ACTIVE_HIGH>;
>> +     ranges = < 0x82000000 0 0xfa000000 0x0 0xfa000000 0 0x600000
>> +                0x81000000 0 0xfa600000 0x0 0xfa600000 0 0x100000 >;
>> +     num-lanes = <4>;
>> +     reg = < 0x0 0xf8000000 0x0 0x2000000 >, < 0x0 0xfd000000 0x0 0x1000000 >;
>> +     reg-name = "axi-base", "apb-base";
>> +     resets = <&cru SRST_PCIEPHY>, <&cru SRST_PCIE_CORE>, <&cru SRST_PCIE_MGMT>,
>> +              <&cru SRST_PCIE_MGMT_STICKY>, <&cru SRST_PCIE_PIPE>;
>> +     reset-names = "core", "mgmt", "mgmt-sticky", "pipe";
>> +     phys = <&pcie_phy>;
>> +     phy-names = "pcie-phy";
>> +     pinctrl-names = "default";
>> +     pinctrl-0 = <&pcie_clkreq>;
>> +     #interrupt-cells = <1>;
>> +     interrupt-controller;
>> +     interrupt-map-mask = <0 0 0 7>;
>> +     interrupt-map = <0 0 0 1 &pcie0 1>,
>> +                     <0 0 0 2 &pcie0 2>,
>> +                     <0 0 0 3 &pcie0 3>,
>> +                     <0 0 0 4 &pcie0 4>;
>> +};
>
>
> And yet I don't see anything related to msi-map in the binding or in
> the example. As Doug mentioned issues with MSIs being delivered, I
> wonder if the two are related...

With Shawn's latest patches and following his latest example dts
snippet (which includes the msi-map), things worked much better.  :)

Thank you for your help!

-Doug

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ