1. 22 10月, 2011 1 次提交
  2. 21 10月, 2011 1 次提交
  3. 15 10月, 2011 3 次提交
  4. 10 10月, 2011 1 次提交
  5. 07 10月, 2011 1 次提交
  6. 02 10月, 2011 1 次提交
  7. 01 10月, 2011 3 次提交
    • A
      ARM: OMAP: musb: Remove a redundant omap4430_phy_init call in usb_musb_init · b8e111a7
      Axel Lin 提交于
      Current code calls omap4430_phy_init() twice in usb_musb_init().
      Calling omap4430_phy_init() once is enough.
      This patch removes the first omap4430_phy_init() call, which using an
      uninitialized pointer as parameter.
      
      This patch elimates below build warning:
      arch/arm/mach-omap2/usb-musb.c: In function 'usb_musb_init':
      arch/arm/mach-omap2/usb-musb.c:141: warning: 'dev' may be used uninitialized in this function
      Signed-off-by: NAxel Lin <axel.lin@gmail.com>
      Bjarne Steinsbo <bsteinsbo@gmail.com>
      Acked-by: NFelipe Balbi <balbi@ti.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      b8e111a7
    • T
      ARM: OMAP: Fix i2c init for twl4030 · bfd46a54
      Tony Lindgren 提交于
      Looks like 2600 kHz rate does not work reliably on 2430,
      so just use the 100 kHz rate.
      
      Otherwise the system often fails to boot properly with:
      
      omap_i2c omap_i2c.2: timeout waiting for bus ready
      omap_i2c omap_i2c.2: timeout waiting for bus ready
      twl: i2c_write failed to transfer all messages
      omap_i2c omap_i2c.2: timeout waiting for bus ready
      twl: i2c_write failed to transfer all messages
      omap_i2c omap_i2c.2: timeout waiting for bus ready
      twl: i2c_write failed to transfer all messages
      twl: clock init err [-110]
      omap_i2c omap_i2c.2: timeout waiting for bus ready
      twl: i2c_write failed to transfer all messages
      TWL4030 Unable to unlock IDCODE registers --110
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      bfd46a54
    • B
      ARM: OMAP4: MMC: fix power and audio issue, decouple USBC1 from MMC1 · 3696d303
      Bryan Buckley 提交于
      Remove OMAP4_USBC1_ICUSB_PWRDNZ_MASK during enable/disable PWRDNZ mode for
      MMC1_PBIAS and associated extended-drain MMC1 I/O cell. This is in accordance
      with the control module programming guide. This fixes a bug where if trying to
      use gpio_98 or gpio_99 and MMC1 at the same time the GPIO signal will be
      affected by a changing SDMMC1_VDDS.
      
      Software must keep MMC1_PBIAS cell and MMC1_IO cell PWRDNZ signals low whenever
      SDMMC1_VDDS ramps up/down or changes for cell protection purposes.
      
      MMC1 is based on SDMMC1_VDDS whereas USBC1 is based on SIM_VDDS therefore
      they can operate independently.
      Signed-off-by: NBryan Buckley <bryan.buckley@ti.com>
      Acked-by: NKishore Kadiyala <kishore.kadiyala@ti.com>
      Tested-by: NBalaji T K <balajitk@ti.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      3696d303
  8. 27 9月, 2011 2 次提交
  9. 26 9月, 2011 4 次提交
  10. 21 9月, 2011 3 次提交
    • R
      ARM: fix vmlinux.lds.S discarding sections · 6760b109
      Russell King 提交于
      We are seeing linker errors caused by sections being discarded, despite
      the linker script trying to keep them.  The result is (eg):
      
      `.exit.text' referenced in section `.alt.smp.init' of drivers/built-in.o: defined in discarded section `.exit.text' of drivers/built-in.o
      `.exit.text' referenced in section `.alt.smp.init' of net/built-in.o: defined in discarded section `.exit.text' of net/built-in.o
      
      This is the relevent part of the linker script (reformatted to make it
      clearer):
      | SECTIONS
      | {
      | /*
      | * unwind exit sections must be discarded before the rest of the
      | * unwind sections get included.
      | */
      | /DISCARD/ : {
      | *(.ARM.exidx.exit.text)
      | *(.ARM.extab.exit.text)
      | }
      | ...
      | .exit.text : {
      | *(.exit.text)
      | *(.memexit.text)
      | }
      | ...
      | /DISCARD/ : {
      | *(.exit.text)
      | *(.memexit.text)
      | *(.exit.data)
      | *(.memexit.data)
      | *(.memexit.rodata)
      | *(.exitcall.exit)
      | *(.discard)
      | *(.discard.*)
      | }
      | }
      
      Now, this is what the linker manual says about discarded output sections:
      
      |    The special output section name `/DISCARD/' may be used to discard
      | input sections.  Any input sections which are assigned to an output
      | section named `/DISCARD/' are not included in the output file.
      
      No questions, no exceptions. It doesn't say "unless they are listed
      before the /DISCARD/ section." Now, this is what asn-generic/vmlinux.lds.S
      says:
      | /*
      |  * Default discarded sections.
      |  *
      |  * Some archs want to discard exit text/data at runtime rather than
      |  * link time due to cross-section references such as alt instructions,
      |  * bug table, eh_frame, etc. DISCARDS must be the last of output
      |  * section definitions so that such archs put those in earlier section
      |  * definitions.
      |  */
      
      And guess what - the list _always_ includes .exit.text etc.
      
      Now, what's actually happening is that the linker is reading the script,
      and it finds the first /DISCARD/ output section at the beginning of the
      script. It continues reading the script, and finds the 'DISCARD' macro
      at the end, which having been postprocessed results in another
      /DISCARD/ output section. As the linker already contains the earlier
      /DISCARD/ output section, it adds it to that existing section, so it
      effectively is placed at the start. This can be seen by using the -M
      option to ld:
      
      | Linker script and memory map
      |
      |                 0xc037c080                jiffies = jiffies_64
      |
      | /DISCARD/
      |  *(.ARM.exidx.exit.text)
      |  *(.ARM.extab.exit.text)
      |  *(.exit.text)
      |  *(.memexit.text)
      |  *(.exit.data)
      |  *(.memexit.data)
      |  *(.memexit.rodata)
      |  *(.exitcall.exit)
      |  *(.discard)
      |  *(.discard.*)
      |
      |                 0xc0008000                . = 0xc0008000
      |
      | .head.text      0xc0008000      0x1d0
      |                 0xc0008000                _text = .
      |  *(.head.text)
      |  .head.text     0xc0008000      0x1d0 arch/arm/kernel/head.o
      |                 0xc0008000                stext
      |
      | .text           0xc0008200   0x2d78d0
      |                 0xc0008200                _stext = .
      |                 0xc0008200                __exception_text_start = .
      |  *(.exception.text)
      |  .exception.text
      | ...
      
      As you can see, all the discarded sections are grouped together - and
      as a result of it being the first output section, they all appear before
      any other section.
      
      The result is that not only is the unwind information discarded (as
      intended), but also the .exit.text, despite us wanting to have the
      .exit.text preserved.
      
      We can't move the unwind information elsewhere, because it'll then be
      included even when we do actually discard the .exit.text (and similar)
      sections.
      
      So, work around this by avoiding the generic DISCARDS macro, and instead
      conditionalize the sections to be discarded ourselves.  This avoids the
      ambiguity in how the linker assigns input sections to output sections,
      making our script less dependent on undocumented linker behaviour.
      Reported-by: NRob Herring <robherring2@gmail.com>
      Tested-by: NMark Brown <broonie@opensource.wolfsonmicro.com>
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      6760b109
    • L
      mach-integrator: fix VGA base regression · b71d8429
      Linus Walleij 提交于
      The changes introduced in commit
      cc22b4c1
      "ARM: set vga memory base at run-time"
      
      Makes the Integrator/AP freeze completely. I appears that
      this is due to the VGA base address being assigned at PCI
      init time, while this base is needed earlier than that.
      Moving the initialization of the base address to the
      .map_io function solves this problem.
      
      Cc: Rob Herring <rob.herring@calxeda.com>
      Cc: Nicolas Pitre <nicolas.pitre@linaro.org>
      Cc: Arnd Bergmann <arnd@arndb.de>
      Signed-off-by: NLinus Walleij <linus.walleij@stericsson.com>
      Acked-by: NRob Herring <rob.herring@calxeda.com>
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      b71d8429
    • S
      arm/dt: Tegra: Update SDHCI nodes to match bindings · a0638eb6
      Stephen Warren 提交于
      The bindings were recently updated to have separate properties for each
      type of GPIO. Update the Device Tree source to match that.
      Signed-off-by: NStephen Warren <swarren@nvidia.com>
      Acked-by: NOlof Johansson <olof@lixom.net>
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      a0638eb6
  11. 17 9月, 2011 2 次提交
  12. 15 9月, 2011 8 次提交
  13. 14 9月, 2011 1 次提交
  14. 11 9月, 2011 2 次提交
  15. 10 9月, 2011 2 次提交
  16. 07 9月, 2011 5 次提交