This change adds a board configuration for the NanoPi NEO Core2 LTS device ("nanopineocore2").
This board configuration provides support for the Core2's SY8106A I2C-based voltage regulator.
This regulator provides higher CPU voltage operation, allowing higher CPU clock rates to be
utilized.
* [Early WIP] Update sunxi-next to kernel 4.17
* Switch Allwinner 32 and 64bit to U-boot 2018.05
* Adjust patched for 4.17.y / sunxi-next
- adjust both configurations
- removing FAT support from u-boot (breaks if you try to save)
Tested those boards:
Cubietruck: wlan fails http://ix.io/1fYS USB OK, HDMI yes
Bananapi R40: http://ix.io/1fZm USB OK, HDMI yes
Lime A64: USB no, HDMI no, wireless buggy, eMMC yes
Orangepi prime H5: OK http://ix.io/1fZJ DVFS no
Orangepi2e: DVFS OK, HDMI OK, net OK, wifi OK, eMMC ok, http://ix.io/1fZT
* Kernel config update, enabling HDMI on CT+
* Trying to fix A64 HDMI but failed. Fixed M64 ethernet instead
* Update orangepioneplus.wip
* Update orangepioneplus.wip
* Fix H6 build process
* Add regulator bits for Orangepizero+, thanks to @5kft
* add H5 support for optional 1.3v regulator and 1.3GHz operation
This patch adds two optional overlays that can be used to:
1) enable the 1.1v/1.3v regulator on boards that provide the necessary compatible H/W support
2) modify the default CPU clock operating table to add new 1.2GHz and 1.3GHz clocks
Note that the generated regulator overlay will only support boards whose 1.1v/1.3v regulator
is controlled by GPIO PL6.
* updates for the NanoPi NEO Plus2
This change introduces a patch that provides two changes for the NanoPi NEO Plus2:
* Configure the "cpu0" to use the "vdd_cpux" regulator; this enables the ability to use higher CPU clocks
* Correct the configurations of the on-board power and status LEDs
* Adjust nightly building and few boards config cleanup
* implemented improved support for the FriendlyArm NanoPi Fire3
* introduced new WIP board configuration "nanopifire3"
* added and enabled the FA SPU1705 regulator
* enabled CPU-based thermal support
* implemented DT-based DVFS table (400MHz-1.4GHz)
* fixed and updated the thermal table and cooling maps
* added support for the onboard LED
* minor patch cleanup
the I2S clock is apparently problematic right now, or the dts definition is off. Either way it is causing problems at the moment. This simply doesn't add the device tree entries for the cards.
* Initial commit, cleanup of Rockchip default
* clean up patches:
- 100_DTS_Tinker_opp_LED was splitted into 3 patches
- 100_DTS_opp for opp (adjusted to RKs 3 point description of opp Voltage)
- 110_DTS_8723bs for the wifi driver
-rename of 270-dts-tinker-bluetooth.patch -> 111_DTS_disable_AP6212_bluetooth.patch to keep wifi-chip stuff together
- 120_DTS_led1_heartbeat
- 190_dts_tinker_s_emmc was reworked and splitted
- gpiomem node was removed and has its own patch (260_DTS_gpiomem_node)
- i2c1 node was removed and has its own patch 270_DTS_activate_i2c1
- spi2 part was removed (defined in rk3288.dtsi), default CS will now be CS0 not 1 (no reason to change this)
- vdd_log regulator is removed (the counterpart is missing anyway, and actually disabled in ASUS and Rockchips branch) --> own patch in case it gets activated
- 120_workaround_tinker_board_reboot -> 130_workaround_tinker_board_reboot to get some free numbers... ;)
* Renamed 190_DTS_tinker_s_emmc and splitted into DTS-Part and driver part (191_driver_mmc_adjustment)
* Boots, Still no hdmi console
* Rockchip Kernel config updates
Thanks to @Ntemis for the config options, they fixed the framebuffer
Still have runtime GPU errors related to power model
- merging C2 and Meson family on the source level, C2 is still making own kernels, but sources, patches and configs are the same
- merged boot scripts for meson family. support for non existing legacy kernel was dropped from boot scripts, added UUID support, armbianEnv.txt
- Meson default remain on 4.14.y, NEXT moved to 4.17.y and DEV remains on master
- remove deprecated patches, remove wrong permissions in patches
- tested on C2, K2 and Le Potate. USB troubles are still present and common, while K2 and Lepotato might have boot/reboot troubles on 4.16+
- boards configuration cleanup
- moving K2 to the supported list. It's the same level of support as Le Potato
