1. 20 2月, 2014 1 次提交
    • J
      kbuild: dtbs_install: new make target · f4d4ffc0
      Jason Cooper 提交于
      Unlike other build products in the Linux kernel, there is no 'make
      *install' mechanism to put devicetree blobs in a standard place.
      
      This commit adds a new 'dtbs_install' make target which copies all of
      the dtbs into the INSTALL_DTBS_PATH directory. INSTALL_DTBS_PATH can be
      set before calling make to change the default install directory. If not
      set then it defaults to:
      
      	$INSTALL_PATH/dtbs/$KERNELRELEASE.
      
      This is done to keep dtbs from different kernel versions separate until
      things have settled down.  Once the dtbs are stable, and not so strongly
      linked to the kernel version, the devicetree files will most likely move
      to their own repo.  Users will need to upgrade install scripts at that
      time.
      
      v7: (reworked by Grant Likely)
      - Moved rules from arch/arm/Makefile to arch/arm/boot/dts/Makefile so
        that each dtb install could have a separate target and be reported as
        part of the make output.
      - Fixed dependency problem to ensure $KERNELRELEASE is calculated before
        attempting to install
      - Removed option to call external script. Copying the files should be
        sufficient and a build system can post-process the install directory.
        Despite the fact an external script is used for installing the kernel,
        I don't think that is a pattern that should be encouraged. I would
        rather see buildroot type tools post process the install directory to
        rename or move dtb files after installing to a staging directory.
        - Plus it is easy to add a hook after the fact without blocking the
          rest of this feature.
      - Move the helper targets into scripts/Makefile.lib with the rest of the
        common dtb rules
      Signed-off-by: NJason Cooper <jason@lakedaemon.net>
      Signed-off-by: NGrant Likely <grant.likely@linaro.org>
      Cc: Michal Marek <mmarek@suse.cz>
      Cc: Russell King <linux@arm.linux.org.uk>
      Cc: Rob Herring <robh+dt@kernel.org>
      f4d4ffc0
  2. 01 2月, 2014 3 次提交
  3. 29 1月, 2014 2 次提交
  4. 27 1月, 2014 2 次提交
  5. 24 1月, 2014 1 次提交
  6. 21 1月, 2014 2 次提交
    • S
      regulator: tps6586x: Add and use correct voltage table · 844a4f0d
      Stefan Agner 提交于
      Depending on the regulator version, the voltage table might be
      different. Use version specific regulator tables in order to select
      correct voltage table. For the following regulator versions different
      voltage tables are now used:
      
        * TPS658623: Use correct voltage table for SM2
        * TPS658643: New voltage table for SM2
      
      Both versions are in use on the Colibri T20 module. Make use of the
      correct tables by requesting the correct SM2 voltage of 1.8V.
      
      This change is not backward compatible since an old driver is not able
      to correctly set that value. The value 1.8V is out of range for the old
      driver and will refuse to probe the device. The regulator starts with
      default settings and the driver shows appropriate error messages.
      
      On Colibri T20, the old value used to work with TPS658623 since the
      driver applied a wrong voltage table too. However, the TPS658643 used
      on V1.2 devices uses yet another voltage table and those broke that
      pseudo-compatibility. The regulator driver now has the correct voltage
      table for both regulator versions and those the correct voltage can be
      used in the device tree.
      Signed-off-by: NStefan Agner <stefan@agner.ch>
      Reviewed-by: NThierry Reding <treding@nvidia.com>
      Acked-by: NMark Brown <broonie@linaro.org>
      Acked-by: NStephen Warren <swarren@nvidia.com>
      Signed-off-by: NLee Jones <lee.jones@linaro.org>
      844a4f0d
    • B
      ARM: shmobile: r8a7790.dtsi: ficx i2c[0-3] clock reference · 2450badf
      Ben Dooks 提交于
      The R8A7790's dtsi file i2c0, i2c1, i2c2, and i2c3 nodes have clock
      references to the mstp3_clks clock node, however these clocks are in the
      mstp9_clks node.
      
      The error was introducted in 72197ca7 ("ARM: shmobile: r8a7790:
       Reference clocks") which is in Simon's current development tree.
      
      This patch fixes the following error:
      
      of_clk_src_onecell_get: invalid clock index 31
      i2c-rcar e6508000.i2c: cannot get clock
      i2c-rcar: probe of e6508000.i2c failed with error -2
      Signed-off-by: NBen Dooks <ben.dooks@codethink.co.uk>
      Acked-by: NLaurent Pinchart <laurent.pinchart@ideasonboard.com>
      Signed-off-by: NSimon Horman <horms+renesas@verge.net.au>
      2450badf
  7. 18 1月, 2014 10 次提交
  8. 17 1月, 2014 1 次提交
    • G
      dt/bindings: remove device_type "network" references · 35129175
      Grant Likely 提交于
      device_type is deprecated and the kernel doesn't require it in most
      cases. The only exceptions for flat tree users are the "gianfar",
      "ucc_geth" and "ibm,emac" bindings, and arguably that requirement could
      be relaxed for ucc_geth and ibm,emac (that is a task for separate
      patches though).
      
      This patch removes references to device_type="network" from the binding
      documentation where possible and removes the properties from ARM and
      microblaze dts files. This patch does not modify the powerpc .dts files
      since there are a much larger number of them affected and I think the
      ucc_geth, ibm,emac and gianfar users should be addressed before clearing
      out the references to reduce the chance of breakage.
      Signed-off-by: NGrant Likely <grant.likely@linaro.org>
      Acked-by: NMichal Simek <monstr@monstr.eu>
      Cc: Rob Herring <rob.herring@calxeda.com>
      Cc: Pawel Moll <pawel.moll@arm.com>
      Cc: Mark Rutland <mark.rutland@arm.com>
      Cc: Ian Campbell <ijc+devicetree@hellion.org.uk>
      Cc: Kumar Gala <galak@codeaurora.org>
      35129175
  9. 16 1月, 2014 2 次提交
  10. 15 1月, 2014 1 次提交
  11. 13 1月, 2014 1 次提交
  12. 11 1月, 2014 1 次提交
  13. 09 1月, 2014 12 次提交
  14. 08 1月, 2014 1 次提交