1. 22 Jul, 2020 1 commit
  2. 07 Jul, 2020 1 commit
    • Jagan Teki's avatar
      arm64: dts: rockchip: Add Radxa Rock Pi N10 initial support · b1fccd3c
      Jagan Teki authored and Kever Yang's avatar Kever Yang committed
      
      
      Rock Pi N10 is a Rockchip RK3399Pro based SBC, which has
      - VMARC RK3399Pro SOM (as per SMARC standard) from Vamrs.
      - Compatible carrier board from Radxa.
      
      VAMRC RK3399Pro SOM need to mount on top of radxa dalang
      carrier board for making Rock Pi N10 SBC.
      
      So, add initial support for Rock Pi N10 by including rk3399,
      rk3399pro vamrc-som and raxda dalang carrier board dtsi files.
      
      rk3399pro-rock-pi-n10.dts was synced from linux-next v5.7-rc1.
      
      Tested
      - ROCK PI N10 Model B
      - ROCK PI N10 Model C
      - Boot from SD
      Signed-off-by: Jagan Teki's avatarJagan Teki <jagan@amarulasolutions.com>
      Reviewed-by: Kever Yang's avatarKever Yang <kever.yang@rock-chips.com>
      b1fccd3c
  3. 30 Jan, 2020 2 commits
    • Jagan Teki's avatar
      rockchip: Add Single boot image (with binman, pad_cat) · 79030a48
      Jagan Teki authored and Kever Yang's avatar Kever Yang committed
      
      
      All rockchip platforms support TPL or SPL-based bootloader
      in mainline with U-Boot proper as final stage. For each
      stage we need to burn the image on to flash with respective
      offsets.
      
      This patch creates a single boot image component using
      - binman, for arm32 rockchip platforms
      - pad_cat, for arm64 rockchip platforms.
      
      This would help users to get rid of burning different
      boot stage images.
      
      The new image called 'u-boot-rockchip.bin'
      which can burn into flash like:
      
      ₹ sudo dd if=u-boot-rockchip.bin of=/dev/sda seek=64
      
      This would support all rockchip platforms, except rk3128
      since it doesn't support for SPL yet.
      
      Cc: Matwey V. Kornilov <matwey.kornilov@gmail.com>
      Cc: Wadim Egorov <w.egorov@phytec.de>
      Signed-off-by: Jagan Teki's avatarJagan Teki <jagan@amarulasolutions.com>
      Reviewed-by: Kever Yang's avatarKever Yang <kever.yang@rock-chips.com>
      79030a48
    • Jagan Teki's avatar
      arm: dts: rk3036: Add rk3036-u-boot.dtsi · f48299a8
      Jagan Teki authored and Kever Yang's avatar Kever Yang committed
      
      
      Add U-Boot specific dtsi file for rk3036 SoC. This
      would help to add U-Boot specific dts nodes, properties
      which are common across rk3036.
      
      Right now, the file is empty, will add required changes
      in future patches.
      Signed-off-by: Jagan Teki's avatarJagan Teki <jagan@amarulasolutions.com>
      Reviewed-by: Kever Yang's avatarKever Yang <kever.yang@rock-chips.com>
      f48299a8
  4. 08 May, 2019 1 commit
    • Jagan Teki's avatar
      arm64: rockchip: dts: rk3399: Use rk3399-u-boot.dtsi · 90430fa8
      Jagan Teki authored and Kever Yang's avatar Kever Yang committed
      Now we have
      - board specific -u-boot.dtsi files for board specific u-boot
        dts changes.
      - soc specific rk3399-u-boot.dtsi for soc specific u-boot
        dts changes.
      
      So, include the rk3399-u-boot-dtsi on respective board -u-boot.dtsi
      and drop the properties which are globally available in rk3399-u-boot.dtsi
      
      Right now rk3399-u-boot.dtsi has sdmmc, spi1 u-boot,dm-pre-reloc
      property and more properties and nodes can be move further based
      on the requirements.
      
      This would fix, the -u-boot.dtsi inclusion for evb, firefly, puma
      boards that was accidentally merged on below commit.
      "rockchip: dts: rk3399: Create initial rk3399-u-boot.dtsi"
      (sha1: e05b4a4f
      
      )
      Signed-off-by: Jagan Teki's avatarJagan Teki <jagan@amarulasolutions.com>
      Reviewed-by: Kever Yang's avatarKever Yang <kever.yang@rock-chips.com>
      90430fa8
  5. 30 Apr, 2019 2 commits
  6. 17 Apr, 2019 1 commit