1. 07 10月, 2017 1 次提交
    • L
      ARM: dts: bcm283x: Fix console path on RPi3 · f08f58a2
      Loic Poulain 提交于
      Contrary to other RPi devices, RPi3 uses uart0 to communicate with
      the BCM43438 bluetooth controller. uart1 is then used for the console.
      Today, the console configuration is inherited from the bcm283x dtsi
      (bootargs) which is not the correct one for the RPi3. This leads to
      routing issue and confuses the Bluetooth controller with unexpected
      data.
      
      This patch introduces chosen/stdout path to configure console to uart0
      on bcm283x family and overwrite it to uart1 in the RPi3 dts.
      
      Create serial0/1 aliases referring to uart0 and uart1 paths.
      Remove unneeded earlyprintk.
      
      Fixes: 4188ea2a ("ARM: bcm283x: Define UART pinmuxing on board level")
      Signed-off-by: NLoic Poulain <loic.poulain@gmail.com>
      Tested-by: NStefan Wahren <stefan.wahren@i2se.com>
      Signed-off-by: NEric Anholt <eric@anholt.net>
      Reviewed-by: NEric Anholt <eric@anholt.net>
      f08f58a2
  2. 13 6月, 2017 1 次提交
  3. 16 5月, 2017 2 次提交
  4. 28 3月, 2017 3 次提交
  5. 18 3月, 2017 1 次提交
  6. 17 3月, 2017 1 次提交
  7. 07 3月, 2017 1 次提交
  8. 19 1月, 2017 1 次提交
  9. 12 11月, 2016 1 次提交
  10. 01 11月, 2016 1 次提交
  11. 18 10月, 2016 1 次提交
  12. 09 9月, 2016 1 次提交
    • I
      ARM: dts: Remove use of skeleton.dtsi from bcm283x.dtsi · 6b7b554d
      Ian Campbell 提交于
      This file is included from DTS files under arch/arm64 too (via
      broadcom/bcm2837-rpi-3-b.dts and broadcom/bcm2837.dtsi). There is a desire
      not to have skeleton.dtsi for ARM64. See commit 3ebee5a2 ("arm64: dts:
      kill skeleton.dtsi") for rationale for its removal.
      
      As well as the addition of #*-cells also requires adding the device_type to
      the rpi memory node explicitly.
      
      Note that this change results in the removal of an empty /aliases node from
      bcm2835-rpi-a.dtb and bcm2835-rpi-a-plus.dtb. I have no hardware to check
      if this is a problem or not.
      
      It also results in some reordering of the nodes in the DTBs (the /aliases
      and /memory nodes come later). This isn't supposed to matter but, again,
      I've no hardware to check if it is true in this particular case.
      Signed-off-by: NIan Campbell <ijc@hellion.org.uk>
      Acked-by: NMark Rutland <mark.rutland@arm.com>
      Tested-by: NStefan Wahren <stefan.wahren@i2se.com>
      Cc: Catalin Marinas <catalin.marinas@arm.com>
      Cc: Will Deacon <will.deacon@arm.com>
      Cc: Mark Rutland <mark.rutland@arm.com>
      Cc: Rob Herring <robh+dt@kernel.org>
      Cc: Frank Rowand <frowand.list@gmail.com>
      Cc: Eric Anholt <eric@anholt.net>
      Cc: Stephen Warren <swarren@wwwdotorg.org>
      Cc: Lee Jones <lee@kernel.org>
      Cc: Gerd Hoffmann <kraxel@redhat.com>
      Cc: devicetree@vger.kernel.org
      Cc: linux-kernel@vger.kernel.org
      Cc: linux-arm-kernel@lists.infradead.org
      Cc: linux-rpi-kernel@lists.infradead.org
      Cc: arm@kernel.org
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      6b7b554d
  13. 25 8月, 2016 1 次提交
  14. 01 6月, 2016 1 次提交
    • L
      ARM: bcm2835: dt: Add the ethernet to the device trees · 6a937927
      Lubomir Rintel 提交于
      The hub and the ethernet in its port 1 are hardwired on the board.
      
      Compared to the adapters that can be plugged into the USB ports, this
      one has no serial EEPROM to store its MAC. Nevertheless, the Raspberry Pi
      has the MAC address for this adapter in its ROM, accessible from its
      firmware.
      
      U-Boot can read out the address and set the local-mac-address property of the
      node with "ethernet" alias. Let's add the node so that U-Boot can do its
      business.
      
      Model B rev2 and Model B+ entries were verified by me, the hierarchy and
      pid/vid pair for the Version 2 was provided by Peter Chen. Original
      Model B is a blind shot, though very likely correct.
      Signed-off-by: NLubomir Rintel <lkundrak@v3.sk>
      Acked-by: NStephen Warren <swarren@wwwdotorg.org>
      Signed-off-by: NEric Anholt <eric@anholt.net>
      6a937927
  15. 20 4月, 2016 1 次提交
  16. 19 4月, 2016 1 次提交
  17. 18 2月, 2016 1 次提交
  18. 03 2月, 2016 4 次提交
  19. 01 1月, 2016 2 次提交
  20. 23 10月, 2015 2 次提交
    • E
      ARM: bcm2835: Add the DDC I2C controller to the device tree. · 121432c7
      Eric Anholt 提交于
      We need to use it for getting video modes over HDMI.
      Signed-off-by: NEric Anholt <eric@anholt.net>
      Acked-by: NStephen Warren <swarren@wwwdotorg.org>
      121432c7
    • E
      ARM: bcm2835: Switch to using the new clock driver support. · 94cb7f76
      Eric Anholt 提交于
      This will give us the ability to set the pixel and HDMI state machine
      clocks for the VC4 KMS driver, change the CPU frequency, and
      potentially gate clocks in the future (once we also write a power
      domain driver).  It also gives the uart an explicit clock reference,
      so that we don't need to change the physical addresses of the old
      fixed clk_bcm2835.c clocks for Raspberry Pi 2 port.
      
      Two clocks get their frequencies updated as a result of this.  One is
      uart's apb_pclk, which was previously accidentally grabbing the fixed
      uart0_pclk due to the apb_pclk not having clk_register_clkdev()
      called.  The uart doesn't seem to do anything with apb_pclk other than
      make sure it's on, so that appears safe (also, as far as I can see,
      the apb clock is actually the same as the VPU clock).  The other is
      EMMC, which according to the docs was supposed to be in the 50-100Mhz
      range, but it turns out the firmware needed to change to running it at
      the 250Mhz core clock speed to avoid a bug in clock domain crossing.
      
      Additionally, anything using BCM2835_CLOCK_VPU will now have a correct
      clock rate if the user configures the boot-time core clock speed using
      config.txt.
      Signed-off-by: NEric Anholt <eric@anholt.net>
      Acked-by: NStephen Warren <swarren@wwwdotorg.org>
      94cb7f76
  21. 15 10月, 2015 1 次提交
  22. 14 5月, 2015 4 次提交
  23. 26 9月, 2014 1 次提交
  24. 25 2月, 2014 1 次提交
    • S
      ARM: bcm2835: fix clock DT node names · b7c6c176
      Stephen Warren 提交于
      DT nodes should be named according to the type of object that they
      represent rather than the identity. DT nodes that contain a reg
      property should include a unit address in their name. Fix these issues.
      
      Add clock-output-names properties to the nodes so that the clocks get
      named something meaningful. This works around the fact that the fixed
      clock driver names clocks after the short node name, i.e. not including
      the unit address.
      Signed-off-by: NStephen Warren <swarren@wwwdotorg.org>
      b7c6c176
  25. 21 2月, 2014 1 次提交
    • S
      ARM: bcm2835: node name unit address cleanup · 25b2f1bd
      Stephen Warren 提交于
      DT nodes that contain a reg property should include a unit address in
      their name. Add the missing unit addresses.
      
      The unit address in a node name must match the value in the reg property.
      Fix the cases where they don't match.
      
      Don't fix the /clocks/* node names yet; that causes problems the clock
      driver to attempt to register multiple clocks with the same name, which
      fails.
      Signed-off-by: NStephen Warren <swarren@wwwdotorg.org>
      25b2f1bd
  26. 12 2月, 2014 4 次提交