1. 09 7月, 2016 1 次提交
  2. 06 7月, 2016 1 次提交
  3. 07 5月, 2016 1 次提交
  4. 06 5月, 2016 1 次提交
  5. 04 5月, 2016 1 次提交
  6. 29 4月, 2016 1 次提交
  7. 27 4月, 2016 1 次提交
  8. 26 4月, 2016 2 次提交
  9. 25 4月, 2016 3 次提交
  10. 20 4月, 2016 1 次提交
  11. 19 4月, 2016 1 次提交
  12. 13 4月, 2016 2 次提交
  13. 10 4月, 2016 1 次提交
  14. 05 4月, 2016 1 次提交
  15. 04 4月, 2016 1 次提交
  16. 02 4月, 2016 2 次提交
  17. 01 4月, 2016 2 次提交
  18. 31 3月, 2016 1 次提交
  19. 30 3月, 2016 1 次提交
  20. 29 3月, 2016 3 次提交
  21. 07 3月, 2016 3 次提交
  22. 04 3月, 2016 2 次提交
  23. 01 3月, 2016 1 次提交
  24. 26 2月, 2016 2 次提交
    • T
      arm64: dts: marvell: add Device Tree files for Armada 7K/8K · ec7e5a56
      Thomas Petazzoni 提交于
      This commit adds the base Device Tree files for the Armada 7K and 8K
      SoCs, as well as the Armada 8040 DB board.
      
      The Armada 7020, 7040 (7K family) and 8020, 8040 (8K family) are
      composed of:
      
       - An AP806 block that contains the CPU core and a few basic
         peripherals. The AP806 is available in dual core configurations
         (used in 7020 and 8020) and quad core configurations (used in 8020
         and 8040).
      
       - One or two CP110 blocks that contain all the high-speed interfaces
         (SATA, PCIe, Ethernet, etc.). The 7K family chips have one CP110,
         and the 8K family chips have two CP110, giving them twice the
         number of HW interfaces.
      
      In order to represent this from a Device Tree point of view, this
      commit creates the following hierarchy:
      
       * armada-ap806.dtsi - definitions common to dual/quad ap806
         * armada-ap806-dual.dtsi - description of the two CPUs
           * armada-7020.dtsi - description of the 7020 SoC
           * armada-8020.dtsi - description of the 8020 SoC
         * armada-ap806-quad.dtsi - description of the four CPUs
           * armada-7040.dtsi - description of the 7040 SoC
             * armada-7040-db.dts - description of the 7040 board
           * armada-8040.dtsi - description of the 8040 SoC
      
      The CP110 blocks are not described yet, and will be part of future
      patch series.
      
      [gregory.clement@free-electrons.com: Fix commit title by adding ' dts:']
      Signed-off-by: NThomas Petazzoni <thomas.petazzoni@free-electrons.com>
      Signed-off-by: NGregory CLEMENT <gregory.clement@free-electrons.com>
      ec7e5a56
    • N
      ARM: keystone: Create new binding for K2G SoC · 3b2d3dc9
      Nishanth Menon 提交于
      K2G SoC family is the newest version of the Keystone family of processors.
      
      The technical reference manual for K2G can be found here:
      http://www.ti.com/lit/ug/spruhy8/spruhy8.pdf
      
      Add new bindings for K2G and the K2G evm. Also document these new bindings.
      Acked-by: NRob Herring <robh@kernel.org>
      Signed-off-by: NNishanth Menon <nm@ti.com>
      Signed-off-by: NFranklin S Cooper Jr <fcooper@ti.com>
      Signed-off-by: NSantosh Shilimkar <ssantosh@kernel.org>
      3b2d3dc9
  25. 25 2月, 2016 1 次提交
  26. 24 2月, 2016 2 次提交
    • S
      devicetree: bindings: Document qcom board compatible format · b32e592d
      Stephen Boyd 提交于
      Some qcom based bootloaders identify the dtb blob based on a set
      of device properties like SoC, platform, PMIC, and revisions of
      those components. In downstream kernels, these values are added
      to the different component dtsi files (i.e. pmic dtsi file, SoC
      dtsi file, board dtsi file, etc.) via qcom specific DT
      properties. The dtb files are parsed by a program called dtbTool
      that picks out these properties and creates a table of contents
      binary blob with the property information and some offsets into
      the concatenation of all the dtbs (termed a QCDT image).
      
      The suggestion is to do this via the board compatible string
      instead, because these qcom specific properties are never used by
      the kernel. Add a document describing the format of the
      compatible string that encodes all this information that's
      currently encoded in the qcom,{msm-id,board-id,pmic-id}
      properties in downstream devicetrees. Future bootloaders may be
      updated to look at the compatible field instead of looking for
      the table of contents image. For non-updateable bootloaders, a
      new dtbTool program will parse the compatible string and generate
      a QCDT image from it.
      Signed-off-by: NStephen Boyd <sboyd@codeaurora.org>
      Acked-by: NRob Herring <robh@kernel.org>
      Signed-off-by: NAndy Gross <andy.gross@linaro.org>
      b32e592d
    • S
      devicetree: bindings: Document Kryo cpu · bd301eee
      Stephen Boyd 提交于
      Document the compatible string for the Kryo family of qcom cpus.
      
      Cc: <devicetree@vger.kernel.org>
      Signed-off-by: NStephen Boyd <sboyd@codeaurora.org>
      Acked-by: NRob Herring <robh@kernel.org>
      Signed-off-by: NAndy Gross <andy.gross@linaro.org>
      bd301eee
  27. 21 2月, 2016 1 次提交