1. 05 10月, 2007 2 次提交
    • S
      [POWERPC] cpm: Describe multi-user ram in its own device node. · 15f8c604
      Scott Wood 提交于
      The way the current CPM binding describes available multi-user (a.k.a.
      dual-ported) RAM doesn't work well when there are multiple free regions,
      and it doesn't work at all if the region doesn't begin at the start of
      the muram area (as the hardware needs to be programmed with offsets into
      this area).  The latter situation can happen with SMC UARTs on CPM2, as its
      parameter RAM is relocatable, u-boot puts it at zero, and the kernel doesn't
      support moving it.
      
      It is now described with a muram node, similar to QE.  The current CPM
      binding is sufficiently recent (i.e. never appeared in an official release)
      that compatibility with existing device trees is not an issue.
      
      The code supporting the new binding is shared between cpm1 and cpm2, rather
      than remain separated.  QE should be able to use this code as well, once
      minor fixes are made to its device trees.
      Signed-off-by: NScott Wood <scottwood@freescale.com>
      Signed-off-by: NKumar Gala <galak@kernel.crashing.org>
      15f8c604
    • S
      [POWERPC] Document local bus nodes in the device tree, and update cuboot-pq2. · 96fca1de
      Scott Wood 提交于
      The localbus node is used to describe devices that are connected via a chip
      select or similar mechanism.  The advantages over placing the devices under
      the root node are that it can be probed without probing other random things
      under the root, and that the description of which chip select a given device
      uses can be used to set up mappings if the firmware failed to do so in a
      useful manner.
      
      cuboot-pq2 is updated to match the binding; previously, it called itself
      chipselect rather than localbus, and used phandle linkage between the
      actual bus node and the control node (the current agreement is to simply use
      the fully-qualified address of the control registers, and ignore the overlap
      with the IMMR node).
      Signed-off-by: NScott Wood <scottwood@freescale.com>
      Signed-off-by: NKumar Gala <galak@kernel.crashing.org>
      96fca1de
  2. 04 10月, 2007 1 次提交
    • S
      [POWERPC] Introduce new CPM device bindings. · e631ae3b
      Scott Wood 提交于
      This introduces a new device binding for the CPM and other devices on
      these boards.  Some of the changes include:
      
      1. Proper namespace scoping for Freescale compatibles and properties.
      
      2. Use compatible rather than things like device_type and model
      to determine which particular variant of a device is present.
      
      3. Give the drivers the relevant CPM command word directly, rather than
      requiring it to have a lookup table based on device-id, SCC v. SMC, and
      CPM version.
      
      4. Specify the CPCR and the usable DPRAM region in the CPM's reg property.
      
      Boards that do not require the legacy bindings should select
      CONFIG_PPC_CPM_NEW_BINDING to enable the of_platform CPM devices. Once
      all existing boards are converted and tested, the config option can
      become default y to prevent new boards from using the old model.  Once
      arch/ppc is gone, the config option can be removed altogether.
      Signed-off-by: NScott Wood <scottwood@freescale.com>
      Acked-by: NDavid Gibson <david@gibson.dropbear.id.au>
      Signed-off-by: NKumar Gala <galak@kernel.crashing.org>
      e631ae3b
  3. 13 9月, 2007 1 次提交
  4. 19 7月, 2007 1 次提交
  5. 03 7月, 2007 2 次提交
  6. 28 6月, 2007 1 次提交
    • D
      [POWERPC] In booting-without-of.txt, clarify that properties must precede subnodes · eff2ebd2
      David Gibson 提交于
      A strict reading of the flattened device tree format defined in
      booting-without-of.txt does in fact require that all the tags defining
      properties for a node go before any definitions of subnodes, however
      it's not particularly emphasised.  Although allowing intermingled
      properties and subnodes would not be ambiguous in meaning, the kernel
      parser does currently require that properties precede subnodes.
      Furthermore, keeping this constraint makes life easier for various
      device tree scanning tools.
      
      Therefore, re-emphasise in booting-without-of.txt that this is a
      strict requirement of the flattened device tree format.
      Signed-off-by: NDavid Gibson <david@gibson.dropbear.id.au>
      Signed-off-by: NPaul Mackerras <paulus@samba.org>
      eff2ebd2
  7. 07 6月, 2007 2 次提交
  8. 09 5月, 2007 2 次提交
  9. 02 5月, 2007 1 次提交
  10. 27 4月, 2007 1 次提交
  11. 21 3月, 2007 1 次提交
  12. 16 3月, 2007 1 次提交
    • D
      [POWERPC] Update documentation for flat device tree format v17 · 0e0293c8
      David Gibson 提交于
      This patch updates booting-without-of.txt to describe version 17 of
      the flattened device tree format.  Version 17 is a small, backwards
      compatible change from version 16, adding an extra field giving the
      size of the device tree's structure block.  At this time, the kernel
      has no use for the extra information, however its presence can make
      life easier for bootloaders or other software manipulating the tree.
      
      In addition this patch adds information on the size_dt_strings field
      of the device tree header, present since version 3 of the flattened
      tree format, but omitted from the documentation.  It also makes
      changes to consistently refer to versions 16 and 17 as versions 16 and
      17 in decimal, rather than version 0x10 which was occasionally used
      for version 16 previously.
      
      Finally, we also add the new field to the definition of the device
      tree header structure in prom.h
      Signed-off-by: NDavid Gibson <david@gibson.dropbear.id.au>
      Acked-by: NJon Loeliger <jdl@freescale.com>
      Signed-off-by: NPaul Mackerras <paulus@samba.org>
      0e0293c8
  13. 09 3月, 2007 1 次提交
  14. 08 3月, 2007 1 次提交
  15. 17 2月, 2007 1 次提交
  16. 16 2月, 2007 1 次提交
  17. 08 2月, 2007 1 次提交
  18. 20 12月, 2006 1 次提交
  19. 04 12月, 2006 1 次提交
  20. 30 11月, 2006 1 次提交
  21. 04 10月, 2006 8 次提交
  22. 30 8月, 2006 1 次提交
  23. 18 8月, 2006 1 次提交
  24. 04 7月, 2006 1 次提交
  25. 28 3月, 2006 1 次提交
  26. 23 3月, 2006 1 次提交
  27. 10 2月, 2006 1 次提交
  28. 07 2月, 2006 1 次提交
  29. 02 2月, 2006 1 次提交