1. 06 7月, 2012 1 次提交
  2. 01 7月, 2012 3 次提交
  3. 13 6月, 2012 1 次提交
  4. 18 5月, 2012 1 次提交
  5. 13 1月, 2012 1 次提交
    • R
      ARM: Add arm_memblock_steal() to allocate memory away from the kernel · 716a3dc2
      Russell King 提交于
      Several platforms are now using the memblock_alloc+memblock_free+
      memblock_remove trick to obtain memory which won't be mapped in the
      kernel's page tables.  Most platforms do this (correctly) in the
      ->reserve callback.  However, OMAP has started to call these functions
      outside of this callback, and this is extremely unsafe - memory will
      not be unmapped, and could well be given out after memblock is no
      longer responsible for its management.
      
      So, provide arm_memblock_steal() to perform this function, and ensure
      that it panic()s if it is used inappropriately.  Convert everyone
      over, including OMAP.
      
      As a result, OMAP with OMAP4_ERRATA_I688 enabled will panic on boot
      with this change.  Mark this option as BROKEN and make it depend on
      BROKEN.  OMAP needs to be fixed, or 137d105d (ARM: OMAP4: Fix
      errata i688 with MPU interconnect barriers.) reverted until such
      time it can be fixed correctly.
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      716a3dc2
  6. 05 1月, 2012 1 次提交
  7. 03 1月, 2012 1 次提交
  8. 02 11月, 2011 1 次提交
  9. 01 11月, 2011 1 次提交
    • M
      backlight: fix broken regulator API usage in l4f00242t03 · 0556dc34
      Mark Brown 提交于
      The regulator support in the l4f00242t03 is very non-idiomatic.  Rather
      than requesting the regulators based on the device name and the supply
      names used by the device the driver requires boards to pass system
      specific supply names around through platform data.  The driver also
      conditionally requests the regulators based on this platform data, adding
      unneeded conditional code to the driver.
      
      Fix this by removing the platform data and converting to the standard
      idiom, also updating all in tree users of the driver.  As no datasheet
      appears to be available for the LCD I'm guessing the names for the
      supplies based on the existing users and I've no ability to do anything
      more than compile test.
      
      The use of regulator_set_voltage() in the driver is also problematic,
      since fixed voltages are required the expectation would be that the
      voltages would be fixed in the constraints set by the machines rather than
      manually configured by the driver, but is less problematic.
      Signed-off-by: NMark Brown <broonie@opensource.wolfsonmicro.com>
      Tested-by: NFabio Estevam <fabio.estevam@freescale.com>
      Cc: Richard Purdie <rpurdie@rpsys.net>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      0556dc34
  10. 25 10月, 2011 1 次提交
  11. 24 10月, 2011 2 次提交
  12. 26 9月, 2011 1 次提交
  13. 22 8月, 2011 1 次提交
  14. 07 7月, 2011 1 次提交
    • F
      ARM: mach-imx/mx31_3ds: Fix IOMUX for SPI1 signals · b2a08e3e
      Fabio Estevam 提交于
      Original code was assuming that the CSPI1 pins on the
      MX31PDK were the primary pin function, which is incorrect.
      
      On MX31PDK board these are the pins that provide CSPI1 functionality:
      
      DSR_DCE1 (ALT mode 1) --> CSPI1_CLK
      RI_DCE1 (ALT mode 1) --> CSPI1_RDY
      
      DTR_DTE1  -->CSI1_MOSI
      DSR_DTE1 --> CSPI1_MISO
      DTR_DCE2 ---> CSPI1_SS2
      
      The 3 IOMUX settings above are done via GPR as per Table A-1 of the MX31RM.
      
      This patch fixes the CSPI1 IOMUX and makes the LCD to be functional.
      Signed-off-by: NFabio Estevam <fabio.estevam@freescale.com>
      Signed-off-by: NSascha Hauer <s.hauer@pengutronix.de>
      b2a08e3e
  15. 22 6月, 2011 1 次提交
    • A
      net: remove mm.h inclusion from netdevice.h · b7f080cf
      Alexey Dobriyan 提交于
      Remove linux/mm.h inclusion from netdevice.h -- it's unused (I've checked manually).
      
      To prevent mm.h inclusion via other channels also extract "enum dma_data_direction"
      definition into separate header. This tiny piece is what gluing netdevice.h with mm.h
      via "netdevice.h => dmaengine.h => dma-mapping.h => scatterlist.h => mm.h".
      Removal of mm.h from scatterlist.h was tried and was found not feasible
      on most archs, so the link was cutoff earlier.
      
      Hope people are OK with tiny include file.
      
      Note, that mm_types.h is still dragged in, but it is a separate story.
      Signed-off-by: NAlexey Dobriyan <adobriyan@gmail.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      b7f080cf
  16. 07 6月, 2011 1 次提交
  17. 19 5月, 2011 3 次提交
  18. 23 3月, 2011 1 次提交
    • A
      mfd: mfd_cell is now implicitly available to mc13xxx drivers · 4ec1b54c
      Andres Salomon 提交于
      The cell's platform_data is now accessed with a helper function;
      change clients to use that, and remove the now-unused data_size.
      
      Note that mfd-core no longer makes a copy of platform_data, but the
      mc13xxx-core driver creates the pdata structures on the stack.  In
      order to get around that, the various ARM mach types that set the
      pdata have been changed to hold the variable in static (global) memory.
      Also note that __initdata references in aforementioned pdata structs
      have been dropped.
      Signed-off-by: NAndres Salomon <dilinger@queued.net>
      Signed-off-by: NSamuel Ortiz <sameo@linux.intel.com>
      4ec1b54c
  19. 08 3月, 2011 5 次提交
  20. 12 2月, 2011 2 次提交
  21. 11 2月, 2011 1 次提交
  22. 10 2月, 2011 3 次提交
  23. 28 1月, 2011 1 次提交
  24. 14 1月, 2011 1 次提交
  25. 12 1月, 2011 1 次提交
  26. 03 1月, 2011 2 次提交
  27. 14 12月, 2010 1 次提交