Move kernel patch folder to archive/rockchip-rk3588-${KERNEL_MAJOR_MINOR} which is the default.
Also rename kernel config to linux-rockchip-rk3588-${KERNEL_MAJOR_MINOR}
Since the `edge` kernel branch often uses RC kernels, introduce a more stable `current` branch.
This branch should not be RC kernels and it also should move to an LTS kernel once released.
Patches are from the Linux Rockchip Mailing List, submitted by Alexey
Charkov. [1]
Notable improvements from changelog:
- Moved the TSADC enablement to per-board .dts/.dtsi files
- Dropped extra "inefficient" OPPs (same voltage - lower frequencies)
- Dropped second passive cooling trips altogether to keep things simple
- Added a cooling map for passive GPU cooling (in a separate patch)
- Added regulator coupling for EVB1 and QuartzPro64
Also enable automatic fan control on Rock 5B.
[1] https://lore.kernel.org/linux-rockchip/20240506-rk-dts-additions-v4-0-271023ddfd40@gmail.com/
"general-add-overlay-compilation-support.patch" became obsolete in
Linux 6.9 (see AR-2352 [1]). Fix this problem:
- Rename *.dts sources in overlay directory to *.dtso
- Change "target +=" line to "dts-y +=" in overlay Makefile
- Remove "always +=" line in overlay Makefile
- Add .scr compilation support in kernel scripts/Makefile.lib
- Patch kernel scripts/Makefile.dtbinst to avoid flattening overlay
directory
For the last two points, see
general-add-overlay-compilation-support.patch
Credits for this fix go to @paolosabatino
[1] https://armbian.atlassian.net/browse/AR-2352
- Bump mainline kernel from 6.10-rc1 to 6.10-rc2
- Remove patches which are now mainlined
- Re-number "fix-initial-PERST-GPIO-value" patch as per number
ordering seen in 0000.patching_config.yaml
- Rewrite kernel config
- `common_defaults_for_mainline` already sets KERNELPATCHDIR='archive/s5p6818-4.14' thus this symlink is not necessary
- 1 step closer to a clean `patch/kernel` dir, when we could finally get rid of `archive/`
The PR build workflow does not need to be started every time a single
reviwer is added, since requesting a review does not change the build.
If the 'Build' label was already added earlier, the build workflow will
have been started already.
On every PR, a workflow is started to check if artifacts should be
built. This happens not only once, but many times, e.g. for every
selected reviewer. Since the workflow has `cancel-in-progress`
enabled, workflows are started and immediately cancelled by the
next one, resulting in many notifications.
Move the `cancel-in-progress` concurrency policy to the second job
which starts only after a check is done if the 'Build' label is even
active on the PR. This should greatly reduce "Workflow cancelled"
notifications via GitHub and email (if enabled by the user).
Also make wording more clear.
