* rock-3a - fix formatting of gpio-line-names
properly format gpio-line-names, following the example from Trevor Woerner for his contribution to the radxa-zero-3 dt.
Also fix a wrong pin number
* fix applying
The extcon-usbc-virtual-pd driver requests the detection GPIO with the flag GPIOD_OUT_LOW, which leads to a failure in gpiod_to_irq and consequently causes the driver loading to fail.
This issue can be fixed by changing GPIOD_OUT_LOW to either GPIOD_IN or GPIOD_ASIS.
This patch opts to change GPIOD_OUT_LOW to GPIOD_ASIS, as this is a less invasive approach. For devices intending to use this driver, it's also necessary to set the pinctrl property of the detection GPIO to input mode in the dts file.
Update Tools in Scripts / Update ${{ matrix.tool.REPO_NAME }} version (map[PROJECT_NAME:koalaman/shellcheck REPO_NAME:shellcheck USER_NAME:koalaman VAR_FILE:lib/functions/general/shellcheck.sh VERSION_VAR:SHELLCHECK_VERSION]) (push) Has been cancelled
Update Tools in Scripts / Update ${{ matrix.tool.REPO_NAME }} version (map[PROJECT_NAME:koalaman/shellcheck REPO_NAME:shellcheck USER_NAME:koalaman VAR_FILE:lib/tools/shellcheck.sh VERSION_VAR:SHELLCHECK_VERSION]) (push) Has been cancelled
Update Tools in Scripts / Update ${{ matrix.tool.REPO_NAME }} version (map[PROJECT_NAME:mvdan/sh REPO_NAME:sh USER_NAME:mvdan VAR_FILE:lib/tools/shellfmt.sh VERSION_VAR:SHELLFMT_VERSION]) (push) Has been cancelled
Update Tools in Scripts / Update ${{ matrix.tool.REPO_NAME }} version (map[PROJECT_NAME:oras-project/oras REPO_NAME:oras USER_NAME:oras-project VAR_FILE:lib/functions/general/oci-oras.sh VERSION_VAR:ORAS_VERSION]) (push) Has been cancelled
Update Tools in Scripts / Update ${{ matrix.tool.REPO_NAME }} version (map[PROJECT_NAME:sharkdp/bat REPO_NAME:bat USER_NAME:sharkdp VAR_FILE:lib/functions/general/bat-cat.sh VERSION_VAR:BATCAT_VERSION]) (push) Has been cancelled
This reverts commit a3dac432fc.
USB patch for 6.12.y needs rework - its a bit more work as code has been moved around kernel tree. TBD after 25.2 release.
* Add MXQ target. Copy HDMI fix from odroid-c1.
* meson8, MXQ: add boot from usb support, configurable dtb
* MXQ: remove boot logo
Built-in U-BOOT is used, so the logo will not be displayed anyway.
* meson: kernel update: legacy -> 6.6, current -> 6.12
* Change Odroid C1 and Onecloud to community supported as build now passes
---------
Co-authored-by: Igor Pecovnik <igor@armbian.com>
Overlay for testing purposes:
There is a strange interaction between that ethernet adapter and the rtc
(it runs better -but still not well- with the ethernet adapter enabled).
Contains rewritten dts, based on decompiled dtb from original Klipad50
(as similiar as possible to original).
Kernel defconfig taken from MKSPI (replaced "mkspi" with "mksklipad50")
While syncing with upstream Linux helios64 dts for 6.9 I missed
the diff for the helios64 status led label (upstream was
helios64:green:status instead of Armbian helios64::status) and
thus broke armbian helios64-heartbeat-led.service.
This commit restores the Armbian label helios64::status to let
helios64-heartbeat-led.service starts.
Fixes: cbaf67f00 ("Sync helios64 to its updated 6.9 dts")
Signed-off-by: Alban Browaeys <alban.browaeys@gmail.com>
Since v5.11, Linux upstream commit 8b5c2b45b8f0 disabled the internal pull-down
for the strobe line explicitly instead of leaving it in its default
state (the opposite of Rockchip Kernel which force enable this intrnal
pulldown by default) thus causing I/O errors in HS400 mode for various
eMMC modules (the ones that did not have an external pulldown on the
strobe line likely).
Discussed upstream and the choice has been made to keep this
behavior as it has been there for too long and reverting might break
other boards http://lists.infradead.org/pipermail/linux-rockchip/2024-April/046416.html
HS400 for helios64 was disabled in commit 5f2e23e90
"Disabled hs400 on Helios64 (hopefully only temporarily) (#3126)"
but for 5.10.63 (ie before the above commit disabled internal pulldown).
Back then I had bisected the emmc I/O issue to a double init of the emmc
regulator introduced while adding deferred support to the regulator driver
core, ie commit 06653ebc0ad2 "regulator: core: resolve supply for boot-on/always-on regulators"
in 5.10.60. But due to the new default for the strobe line internal pulldown
introduced in 5.11, when this double voltage regulator init issue was fixed likely by
8a866d527ac0 "regulator: core: Resolve supply name earlier to prevent double-init"
in Linux 6.1.
