1. 17 5月, 2013 1 次提交
    • J
      ARM: dts: OMAP2+: Simplify NAND support · f40739fa
      Jon Hunter 提交于
      Commit 8c8a7771 (ARM: OMAP2+: Add function to read GPMC settings from
      device-tree) added a device-tree property "gpmc,device-nand" to indicate
      is the GPMC child device is NAND. This commit should have updated the
      GPMC NAND documentation (Documentation/devicetree/bindings/mtd/gpmc-nand.txt)
      to list the property "gpmc,device-nand" as a required property and also
      updated the example. However, this property is redundant and not needed
      because the GPMC child device node for NAND is called "nand". Therefore,
      remove this property.
      Signed-off-by: NJon Hunter <jon-hunter@ti.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      f40739fa
  2. 04 4月, 2013 1 次提交
    • J
      ARM: OMAP2+: Add additional GPMC timing parameters · d36b4cd4
      Jon Hunter 提交于
      Some of the GPMC timings parameters are currently missing from the GPMC
      device-tree binding. Add these parameters to the binding documentation
      as well as code to read them. Also add either "-ps" or "-ns" suffix to
      the GPMC timing properties to indicate whether the timing is in
      picoseconds or nanoseconds.
      
      The existing code in gpmc_read_timings_dt() is checking the value of
      of_property_read_u32() and only is successful storing the value read
      in the gpmc_timings structure. Checking the return value in this case
      is not necessary and we can simply read the value, if present, and
      store directly in the gpmc_timings structure. Therefore, simplify the
      code by removing these checks.
      
      The comment in the gpmc_read_timings_dt() function, "only for OMAP3430"
      is also incorrect as it is applicable to all OMAP3+ devices. So correct
      this too.
      Signed-off-by: NJon Hunter <jon-hunter@ti.com>
      Tested-by: NEzequiel Garcia <ezequiel.garcia@free-electrons.com>
      d36b4cd4
  3. 02 4月, 2013 1 次提交
  4. 16 1月, 2013 1 次提交