1. 08 10月, 2007 1 次提交
  2. 05 10月, 2007 4 次提交
  3. 04 10月, 2007 2 次提交
    • 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
    • S
      [POWERPC] CPM: Change from fsl,brg-frequency to brg/clock-frequency · 6d817aa7
      Scott Wood 提交于
      As suggested by David Gibson, now that we have a separate node
      for the baud rate generators, it's better to use the standard
      clock-frequency property than a cpm-node-level fsl,brg-frequency
      property.
      
      This patch updates existing places where fsl,brg-frequency is
      used.
      Signed-off-by: NScott Wood <scottwood@freescale.com>
      Signed-off-by: NKumar Gala <galak@kernel.crashing.org>
      6d817aa7
  4. 14 9月, 2007 2 次提交
  5. 18 8月, 2007 1 次提交
  6. 17 8月, 2007 1 次提交
  7. 26 7月, 2007 1 次提交
  8. 19 7月, 2007 1 次提交
    • A
      Fix RGMII-ID handling in gianfar · 7132ab7f
      Andy Fleming 提交于
      The TSEC/eTSEC can detect the interface to the PHY automatically,
      but it isn't able to detect whether the RGMII connection needs internal
      delay.  So we need to detect that change in the device tree, propagate
      it to the platform data, and then check it if we're in RGMII.  This fixes
      a bug on the 8641D HPCN board where the Vitesse PHY doesn't use the delay
      for RGMII.
      Signed-off-by: NAndy Fleming <afleming@freescale.com>
      7132ab7f
  9. 10 7月, 2007 1 次提交
  10. 09 5月, 2007 1 次提交
  11. 13 4月, 2007 1 次提交
  12. 17 2月, 2007 1 次提交
  13. 08 2月, 2007 1 次提交
  14. 07 2月, 2007 1 次提交
  15. 13 11月, 2006 1 次提交
  16. 07 10月, 2006 1 次提交
    • O
      [POWERPC] Fix fsl_soc build breaks · 2b00b254
      Olof Johansson 提交于
      Hrm, there's no way this ever built at time of merge. There's a missing } and
      the wrong type on phy_irq.
      
      Also, another const for get_property().
      
        CC      arch/powerpc/sysdev/fsl_soc.o
      arch/powerpc/sysdev/fsl_soc.c: In function 'fs_enet_of_init':
      arch/powerpc/sysdev/fsl_soc.c:625: error: assignment of read-only variable 'phy_irq'
      arch/powerpc/sysdev/fsl_soc.c:625: warning: assignment makes integer from pointer without a cast
      arch/powerpc/sysdev/fsl_soc.c:661: warning: assignment discards qualifiers from pointer target type
      arch/powerpc/sysdev/fsl_soc.c:684: error: subscripted value is neither array nor pointer
      arch/powerpc/sysdev/fsl_soc.c:687: error: subscripted value is neither array nor pointer
      arch/powerpc/sysdev/fsl_soc.c:722: warning: ISO C90 forbids mixed declarations and code
      arch/powerpc/sysdev/fsl_soc.c:728: error: invalid storage class for function 'cpm_uart_of_init'
      arch/powerpc/sysdev/fsl_soc.c:798: error: initializer element is not constant
      arch/powerpc/sysdev/fsl_soc.c:798: error: expected declaration or statement at end of input
      make[1]: *** [arch/powerpc/sysdev/fsl_soc.o] Error 1
      Signed-off-by: NOlof Johansson <olof@lixom.net>
      Signed-off-by: NPaul Mackerras <paulus@samba.org>
      2b00b254
  17. 04 10月, 2006 1 次提交
  18. 22 9月, 2006 3 次提交
    • V
      POWERPC: Bring the fs_no calculation to the relevant SoC enumeration · 611a15af
      Vitaly Bordug 提交于
      The fs_no mean used to be fs_enet driver driven, hence it was an
      enumeration across all the possible fs_enet "users" in the SoC. Now, with
      QE on the pipeline, and to make DTS descriptions more clear, fs_no features
      relevant SoC part number, with additional field to describe the SoC type.
      
      Another reason for that is now not only fs_enet is going to utilize those
      stuff. There might be UART, HLDC, and even USB, so to prevent confusion and
      be ready for upcoming OF_device transfer, fs_enet and cpm_uart drivers were
      updated in that concern, as well as the relevant DTS.
      Signed-off-by: NVitaly Bordug <vbordug@ru.mvista.com>
      611a15af
    • V
      POWERPC: overhaul with cpm2_map mechanism · d3465c92
      Vitaly Bordug 提交于
      Incorporating the new way of cpm2 immr access, introduced in the previous
      patch, into CPM2 peripheral devices (fs_enet and cpm_uart). Both ppc and
      powerpc approved working( real actions taken in powerpc only, ppc just
      has a wrapper to keep init stuff consistent).
      Signed-off-by: NVitaly Bordug <vbordug@ru.mvista.com>
      d3465c92
    • V
      POWERPC: Get rid of remapping the whole immr · fc8e50e3
      Vitaly Bordug 提交于
      The stuff below cleans up the code attempting to remap the whole cpm2_immr
      early, as well as places happily assuming that fact. This is more like the 2.4
      legacy stuff, and is at least confusing and unclear now.
      
      To keep the world comfortable, a new mechanism is introduced: before accessing
      specific immr register/register set, one needs to map it, using cpm2_map(<reg>),
      for instance, access to CPM command register will look like
      	volatile cpm_cpm2_t *cp = cpm2_map(im_cpm);
      keeping the code clear, yet without "already defined somewhere" cpm2_immr.
      
      So far, unmapping code is not implemented, but it's not a big deal to add it,
      if the whole idea makes sense.
      Signed-off-by: NVitaly Bordug <vbordug@ru.mvista.com>
      fc8e50e3
  19. 21 9月, 2006 1 次提交
  20. 23 8月, 2006 1 次提交
  21. 18 8月, 2006 1 次提交
  22. 08 8月, 2006 1 次提交
  23. 31 7月, 2006 1 次提交
  24. 01 7月, 2006 1 次提交
  25. 22 6月, 2006 1 次提交
  26. 07 2月, 2006 2 次提交
  27. 14 1月, 2006 1 次提交