1. 18 7月, 2009 1 次提交
    • H
      [ARM] pxa: fix gpio issue in zylonite · eb906911
      Haojian Zhuang 提交于
      WARNING: at drivers/gpio/gpiolib.c:83 gpio_ensure_requested+0x58/0xbc()
       autorequest GPIO-71
       Modules linked in:
       [<c0028bd0>] (unwind_backtrace+0x0/0xe8) from [<c003c328>] (warn_slowpath_common+0x48/0x78)
       [<c003c328>] (warn_slowpath_common+0x48/0x78) from [<c003c394>] (warn_slowpath_fmt+0x28/0x38)
       [<c003c394>] (warn_slowpath_fmt+0x28/0x38) from [<c0146128>] (gpio_ensure_requested+0x58/0xbc)
       [<c0146128>] (gpio_ensure_requested+0x58/0xbc) from [<c0146308>] (gpio_direction_input+0x80/0xf4)
       [<c0146308>] (gpio_direction_input+0x80/0xf4) from [<c000c668>] (zylonite_pxa300_init+0x108/0x214)
       [<c000c668>] (zylonite_pxa300_init+0x108/0x214) from [<c000c4e4>] (zylonite_init+0x8/0x84)
       [<c000c4e4>] (zylonite_init+0x8/0x84) from [<c00097cc>] (customize_machine+0x18/0x24)
       [<c00097cc>] (customize_machine+0x18/0x24) from [<c00222e0>] (do_one_initcall+0x30/0x1b0)
       [<c00222e0>] (do_one_initcall+0x30/0x1b0) from [<c00083f4>] (kernel_init+0xa4/0x11c)
       [<c00083f4>] (kernel_init+0xa4/0x11c) from [<c0023f3c>] (kernel_thread_exit+0x0/0x8)
       ---[ end trace 1b75b31a2719ed1c ]---
      
      This issue is caused by using gpio pin without request. Add gpio_request()
      into zylonite. To simplify the code, error checking is omitted since this
      is being performed early.
      Signed-off-by: NHaojian Zhuang <haojian.zhuang@marvell.com>
      Signed-off-by: NEric Miao <eric.y.miao@gmail.com>
      eb906911
  2. 27 4月, 2009 1 次提交
  3. 09 3月, 2009 1 次提交
    • E
      [ARM] pxa: introduce pxa{25x,27x,300,320,930}.h for board usage · 51c62982
      Eric Miao 提交于
      Considering the header mess ATM, it is not always possible to include
      the correct header files within board code. Let's keep this simple:
      
        <mach/pxa25x.h>  - for pxa25x based platforms
        <mach/pxa27x.h>  - for pxa27x based platforms
        <mach/pxa300.h>  - for pxa300 based platforms
        <mach/pxa320.h>  - for pxa320 based platforms
        <mach/pxa930.h>  - for pxa930 based platforms
      
      NOTE:
      
      1. one header one board file, they are not compatible (i.e. they have
         conflicting definitions which won't compile if included together).
      
      2. Unless strictly necessary, the following header files are considered
         to be SoC files use _only_, and is not recommended to be included in
         board code:
      
          <mach/hardware.h>
          <mach/pxa-regs.h>
          <mach/pxa2xx-regs.h>
          <mach/pxa3xx-regs.h>
          <mach/mfp.h>
          <mach/mfp-pxa2xx.h>
          <mach/mfp-pxa25x.h>
          <mach/mfp-pxa27x.h>
          <mach/mfp-pxa3xx.h>
          <mach/mfp-pxa300.h>
          <mach/mfp-pxa320.h>
          <mach/mfp-pxa930.h>
      Signed-off-by: NEric Miao <eric.miao@marvell.com>
      51c62982
  4. 02 12月, 2008 1 次提交
  5. 08 10月, 2008 1 次提交
  6. 27 8月, 2008 1 次提交
  7. 07 8月, 2008 1 次提交
  8. 10 7月, 2008 1 次提交
  9. 03 7月, 2008 1 次提交
  10. 19 4月, 2008 2 次提交
  11. 26 1月, 2008 3 次提交
  12. 31 10月, 2007 1 次提交
  13. 16 10月, 2007 1 次提交