* `meson64-6.1` - rebased patches; 3 were mainlined
- JetHub device was mainlined
- ODROID's hack for pwm1_enable was re-done diffrently in mainline
* `meson64`: switch `current` to `6.0`, `edge` to `6.1-rc8`
- notes in the board file about the RAM issues (tested, confirmed working blob change of #4383 by @pinhaozhang working with u-boot 21.07; `blobless` also works with ATF v2.7 on my known-good-RAM boards)
- tinkerboard-2: add full firmware, for the rtl8822ce PCIe Wifi default card in the tb2 as shipped by ASUS
- tinkerboard-2: uboot: rename `TARGET_TINKER-2_RK3399` to `TARGET_TINKER2_RK3399` to avoid warnings all over
- tinkerboard-2: slower but working Tinkerboard 2S eMMC (HS400+ES to HS200)
- both for u-boot and kernel.
- should not affect 2, only 2S
* `meson64`: `6.0`: g12a and g12b pinmux patches from Radxa
* u-boot: `radxa-zero2`: Radxa's patches for the Zero2 on `v2022.10`
* u-boot: `radxa-zero2`: use `v2022.10` plus Radxa's patches
* `meson64` u-boot v2022.10: change `BOOT_TARGET_DEVICES` to try to boot USB, NVME and SCSI before SD, MMC, PXE, DHCP
* `radxa-zero`: include v2022.10 standard patches (eg: boot from USB first)
* `radxa-zero` & `radxa-zero2`: set `BOOT_FDT_FILE` explicitly; no real changes
* `radxa-zero2`: `6.0`/`edge`: update Radxa Zero 2 DTS patch with Radxa's latest
* `radxa-zero`: `6.0`/`edge`: update USB-C patch with "fix interrupt storm from fusb302"
* `radxa-zero`: use pure mainline v2022.10 u-boot with no patches
* Add Rockpi 4C+
* add newer patches:
- apply patches from RadxaNaoki <noaki@radxa.com>
- ref 5652d6f9c2a4e2c50ac1040c0388859381b0616f: arm64: dts: rockchip: add gmac for ROCK 4C+ (#17)
- apply latest patches from Marcone <marco.nelissen@gmail.com>
- ref e39da181b099a86f5440ed1c08fc699d4a65aed7: arm64: dts: rockchip: Make Rock Pi 4C+ ethernet actually work
- ref 8c519612eeb852268371b3c596eec4622460e5bf: arm64: dts: rockchip: add Rock Pi 4C+ LEDs
- ref 726441afe687ea6059bac37f145ff204b75430f7: arm64: dts: rockchip: enable Rock Pi 4C+ wifi
- ref caad7bef3b5558e2598480c0a0089e2ac3cedcdd: arm64: dts: rockchip: enable Rock Pi 4C+ nvme
- ref 6cdc3215d1691bcd2a407a30e88efa0cec179eb2: arm64: dts: rockchip: enable Rock Pi 4C+ OTG
* default top USB3 port to host mode
* get 2nd HDMI port to work at least. :)
* revert OTG USB3.1 port back to otg mode
* [rockpi4c+] update board def. add usb host overlay.
* remove redundant HDMI clocks and voltages
* enable test builds for Rock PI 4 C+
* [rockpi4c+] add USB host overlay
Co-authored-by: Joe Khoobyar <fourheads@gmail.com>
* sunxi-6.0: initial state: add megous patches to series
* sunxi-6.0: Switch to v6.0.1
* wifi: Limit the version 6.0 for Realtek 88x2cs chipsets
* Adjust kernel configs
* Remove not needed patches
* Adjust broken patches
Co-authored-by: Igor <igor@armbian.com>
* Remove deprecated Odroid XU4 legacy 4.14.y branch
* Clean deprecated kernels from meson64 family
- legacy kernel 4.9 was removed
- current 5.10 was replaced with 5.19
- edge remains on 5.19 until someone bumps it to 6
- patches between 5.11 and 5.18 were removed, 5.10 will be kept for awhile
* Update configs
* RockPI-S board has no video I/O
* udev rule to fix MAC address of iface based on UUID
Deals with WiFi chip lacking any EEPROM to store its unique Ethernet MAC address
Generic mechanism -- could be utilized for other boards having similar issues
* Handy Device Tree overlays for the RockPI S
Use armbian-add-overlay to install these
Reduce CPU voltage for the RK3308 B-S
Option to overclock RK3308 B-S to 1.3Ghz
Increase SDIO clock rate from 1Mhz to 10Mhz
This increases WiFi throughput from 300K bytes/s to 2.4M bytes/s
* corrected comment
* No longer repeat standard opp's in this dts
Require that the standard bs dts already be installed
* User README for adding RockPI-S board variant specific dts overlays
* "enabled" --> "okay"
* added mention of sdnand.dts, fixed typo
* added p2p0 to interfaces whose MAC address should be "fixed"
* RK3308 CPU serial number in nvmem replaces UUID for derivation of fixed MAC addr
Restored use of install utility
* Use RK3308 specific CPU serial number
rather than rootfs UUID
* remove generic fixMACaddress
* Install fixMACaddr file-by-file via install utility
* Drive SDIO bus signals faster
setting RK3308_SOC_CON0_VCCIO3 reduces signal rise/fall times to WiFi SDIO chip
from 30ns to 5ns.
This odd fix forward ported from legacy kernel.
Allows Rock Pi-S WiFi to operate at full speed.
* Set RK3308 I/O voltage domains before SDIO initializes
This patch moves responibility form the io-domain to the pinctrl driver because
the io-domain driver is probed after the SDIO devices are discovered.
This was causing multiple SDIO I/O failures during boot.
A new pinctrl property is added:
io-1v8-domains
is a u32 interpreted as a bit mask where each set bit corresponds to
a 1.8V I/O domain (as opposed to the default of 3.3V for I/O)
The mask is writted to the RK3308_SOC_CON0 GRF register
(once) when the pinctrl driver starts
The default mask is 0x10 where only I/O domain 4 runs at 1.8V
This is necessary for the RockPI-S to run the SDIO clock at high (50Mhz) speed
* align whitespace
* factored rk3308bs overlays out up sdio speedup patch
* factored dts for RK3308 iodomains and pinctrl patches out of speedup patch
* remains of sdio speedup patch merely add iodomains support for rk3308
* factored rockpis dts modification out from rk3308 io voltage domains
replaced rk3308 support from iodomains with
new io-voltage-domains property added to pinctrl
io-voltage-domains specific to rk3308 for now, others SOCs may be added later.
* add sequence numbering to names of rk3308 patches
* corrected tab alignment
* Add ssv6051p wifi driver for rockchip64 current and edge kernel
* also reorders and tidies device tree overlays for rk3318-box
* increase ssv6051 sdio bus to 50MHz in the driver
* Bump sunxi kernels
* sunxi-5.19: Remove pre-applied patch, adapt for series
* sunxi-5.15: Adapt patches to the series, remove previously applied
* Bump it again
Co-authored-by: The-going <48602507+The-going@users.noreply.github.com>
G12/GXL boards with memory of 1GB or lower are unable to boot because the CMA memory pool is set to high. Leaving CMA at the default and providing an overlay for those who need or want the CMA higher, makes more sense than not supporting all possible memory options provided by said SoC(s).
