1. 20 7月, 2012 1 次提交
  2. 13 7月, 2012 2 次提交
  3. 10 7月, 2012 2 次提交
  4. 02 7月, 2012 3 次提交
  5. 18 6月, 2012 1 次提交
    • R
      SPI: fix over-eager devm_xxx() conversion · 10aa5a35
      Russell King 提交于
      1a77b127 (OMAP : SPI : use devm_* functions) converted the SPI
      device controller state to use devm_kzalloc().  Unfortunately, this
      is used against an unbound struct device, which results in the
      following when the device is bound to its driver:
      
      ------------[ cut here ]------------
      WARNING: at /home/rmk/git/linux-rmk/drivers/base/dd.c:257 driver_probe_device+0x78/0x21c()
      Modules linked in:
      Backtrace:
      [<c0017d0c>] (dump_backtrace+0x0/0x10c) from [<c033e208>] (dump_stack+0x18/0x1c) r7:00000000 r6:c01ff28c r5:c040050c r4:00000101
      [<c033e1f0>] (dump_stack+0x0/0x1c) from [<c00337ec>] (warn_slowpath_common+0x58/0x70)
      [<c0033794>] (warn_slowpath_common+0x0/0x70) from [<c0033828>] (warn_slowpath_null+0x24/0x2c)
      [<c0033804>] (warn_slowpath_null+0x0/0x2c) from [<c01ff28c>] (driver_probe_device+0x78/0x21c)
      [<c01ff214>] (driver_probe_device+0x0/0x21c) from [<c01ff49c>] (__driver_attach+0x6c/0x90)
      [<c01ff430>] (__driver_attach+0x0/0x90) from [<c01fda70>] (bus_for_each_dev+0x58/0x98)
      [<c01fda18>] (bus_for_each_dev+0x0/0x98) from [<c01ff0f4>] (driver_attach+0x20/0x28)
      [<c01ff0d4>] (driver_attach+0x0/0x28) from [<c01fe2f4>] (bus_add_driver+0xb4/0x230)
      [<c01fe240>] (bus_add_driver+0x0/0x230) from [<c01ffb24>] (driver_register+0xac/0x138)
      [<c01ffa78>] (driver_register+0x0/0x138) from [<c0215d4c>] (spi_register_driver+0x4c/0x60)
      [<c0215d00>] (spi_register_driver+0x0/0x60) from [<c045414c>] (ks8851_init+0x14/0x1c)
      [<c0454138>] (ks8851_init+0x0/0x1c) from [<c0008770>] (do_one_initcall+0x9c/0x164)
      [<c00086d4>] (do_one_initcall+0x0/0x164) from [<c0436410>] (kernel_init+0x128/0x210)
      [<c04362e8>] (kernel_init+0x0/0x210) from [<c0038754>] (do_exit+0x0/0x72c)
      ---[ end trace 4dcda79f5e89dd84 ]---
      ks8851 spi1.0: message enable is 0
      ks8851 spi1.0: eth0: revision 0, MAC 08:00:28:01:4d:c6, IRQ 194, has EEPROM
      
      Fix this by partially reverting the original commit.
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      10aa5a35
  6. 21 5月, 2012 1 次提交
  7. 20 5月, 2012 7 次提交
  8. 12 5月, 2012 1 次提交
  9. 11 5月, 2012 1 次提交
  10. 10 5月, 2012 1 次提交
  11. 09 5月, 2012 1 次提交
  12. 28 4月, 2012 12 次提交
  13. 25 4月, 2012 2 次提交
    • S
      spi i.MX: do not depend on grouped clocks · aa29d840
      Sascha Hauer 提交于
      the current i.MX clock support groups together unrelated clocks
      to a single clock which is then used by the driver. This can't
      be accomplished with the generic clock framework so we instead
      request the individual clocks in the driver. For i.MX there are
      generally three different clocks:
      
      ipg: bus clock (needed to access registers)
      ahb: dma relevant clock, sometimes referred to as hclk in the datasheet
      per: bit clock, pixel clock
      
      This patch changes the driver to request the individual clocks.
      Currently all clk_get will get the same clock until the SoCs
      are converted to the generic clock framework
      Signed-off-by: NSascha Hauer <s.hauer@pengutronix.de>
      aa29d840
    • H
      spi/s3c64xx: Allow usage for ARCH_S3C24XX · c4bec603
      Heiko Stuebner 提交于
      Newer SoCs from the S3C24XX line, namely S3C2416/2443/2450 contain
      hsspi-controllers compatible with the s3c64xx type.
      
      The previous patches enabled platform support for it, so make the
      driver also usable for the S3C24xx architecture.
      Signed-off-by: NHeiko Stuebner <heiko@sntech.de>
      Acked-by: NGrant Likely <grant.likely@secretlab.ca>
      Signed-off-by: NKukjin Kim <kgene.kim@samsung.com>
      c4bec603
  14. 18 4月, 2012 1 次提交
  15. 14 4月, 2012 1 次提交
  16. 13 4月, 2012 1 次提交
    • M
      ARM: 7366/3: amba: Remove AMBA level regulator support · 1e45860f
      Mark Brown 提交于
      The AMBA bus regulator support is being used to model on/off switches
      for power domains which isn't terribly idiomatic for modern kernels with
      the generic power domain code and creates integration problems on platforms
      which don't use regulators for their power domains as it's hard to tell
      the difference between a regulator that is needed but failed to be provided
      and one that isn't supposed to be there (though DT does make that easier).
      
      Platforms that wish to use the regulator API to manage their power domains
      can indirect via the power domain interface.
      
      This feature is only used with the vape supply of the db8500 PRCMU
      driver which supplies the UARTs and MMC controllers, none of which have
      support for managing vcore at runtime in mainline (only pl022 SPI
      controller does).  Update that supply to have an always_on constraint
      until the power domain support for the system is updated so that it is
      enabled for these users, this is likely to have no impact on practical
      systems as probably at least one of these devices will be active and
      cause AMBA to hold the supply on anyway.
      Signed-off-by: NMark Brown <broonie@opensource.wolfsonmicro.com>
      Acked-by: NLinus Walleij <linus.walleij@linaro.org>
      Tested-by: NShawn Guo <shawn.guo@linaro.org>
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      1e45860f
  17. 11 4月, 2012 2 次提交