1. 05 3月, 2013 2 次提交
    • N
      ARM: dts: remove generated .dtb files on clean · 9e25fe6b
      Nishanth Menon 提交于
      commit 5f300acd
      (ARM: 7152/1: distclean: Remove generated .dtb files)
      ensured that dtbs were cleaned up when they were in
      arch/arm/boot.
      However, with the following commit:
      commit 499cd829
      (ARM: dt: change .dtb build rules to build in dts directory)
      
      make clean now leaves dtbs in arch/arm/boot/dts/
      untouched. Include dts directory so that clean-files rule
      from arch/arm/boot/dts/Makefile is invoked when make
      clean is done.
      
      Cc: Dirk Behme <dirk.behme@de.bosch.com>
      CC: Grant Likely <grant.likely@secretlab.ca>
      Signed-off-by: NNishanth Menon <nm@ti.com>
      Signed-off-by: NOlof Johansson <olof@lixom.net>
      9e25fe6b
    • S
      ARM: bcm2835: fix I2C module clock rate · 2837a1d4
      Stephen Warren 提交于
      BCM2835-ARM-Peripherals.pdf states that the I2C module's input clock is
      nominally 150MHz, and that value is currently reflected in bcm2835.dtsi.
      However, practical measurements show that the rate is actually 250MHz,
      and this agrees with various downstream kernels.
      
      Switch the I2C clock's frequency to 250MHz so that the generated bus
      clock rate is accurate.
      Signed-off-by: NStephen Warren <swarren@wwwdotorg.org>
      Signed-off-by: NOlof Johansson <olof@lixom.net>
      2837a1d4
  2. 02 3月, 2013 1 次提交
    • R
      ARM: Fix broken commit 0cc41e4a corrupting kernel messages · ded3ef0f
      Russell King 提交于
      Commit 0cc41e4a (arch: remove direct definitions of KERN_<LEVEL>
      uses) is broken - not enough thought was put into changing:
      
      	.asciz	"string"
      
      to
      
      	.asciz	"string1" "string2"
      
      The problem is that each string gets _separately_ NUL terminated, so
      the result is a string containing:
      
      	"string1\0string2\0"
      
      rather than:
      
      	"string1string2\0"
      
      With our new printk levels, this ends up as - eg, KERN_DEBUG "string":
      
      	0x01 0x00 0x07 0x00 "string" 0x00
      
      which produces lots of \x01 in the kernel log.
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      ded3ef0f
  3. 01 3月, 2013 37 次提交