sgjava

@martinayotte I'm doing it this way https://github.com/sgjava/patchbian since the build creates the patch for you and a test image at the same time.

@martinayotteI understand the patch part, but usually you make the change somewhere like build/cache/sources/linux-odroidxu4/odroid-5.4.y/arch/arm/boot/dts/exynos5420-pinctrl.dtsi (for XU3/XU4) and a patch is generated in output/patch. This is the step I'm missing. Almost there, thanks for your help do far.

@martinayotteOK, I figured out the syntax for each pinctrl using phandle to identify. So next question is how do I make this part of build process, so it gets applied automatically in img? Duo: /dts-v1/; /plugin/; / { compatible = "allwinner,sun8i-h3-pinctrl"; fragment@0 { target = <0x0b>; __overlay__ { gpio-line-names = "", "", "", "", "GPIOA4 DTX", "GPIOA5 DRX", "", "", "", "", "", "GPIOA11 SCL", "GPIOA12 SDA", "GPIOA13 CS", "GPIOA14 CLK", "GPIOA15 MO", "GPIOA16 MI", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", ""

How does it know which pinctrl to place the line names?

Yes, I'm wondering is that another fragment section in one file or another file?

No worries, I still need to find a way to cover both pin controllers? It appears compatible strings are different.

Ah wrong location. You need to put dtbo in /boot/dtb/overlay, not /boot/dts/overlay as you suggested above.

@martinayotte OK, tried this and no luck on duo: ls /boot/dts/overlay/ sun8i-h3-gpio-line-names.dtbo cat /boot/armbianEnv.txt verbosity=1 bootlogo=false console=serial disp_mode=1920x1080p60 overlay_prefix=sun8i-h3 overlays=usbhost2 usbhost3 rootdev=UUID=d1e6e420-cd58-46c8-aa52-0f8cd59dabb7 rootfstype=ext4 overlays=gpio-line-names usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u cat sun8i-h3-gpio-line-names.dts /dts-v1/; /plugin/; / { compatible = "allwinner,sun8i-h3"; fragment@1 { target = <&pio>; __overlay__ { gpio-line-names = "", "", "", "", "GPIOA4 DTX", "GPIOA5

@martinayotte do you have an example for /boot/armbianEnv.txt gpio-line-names? This is generated board specific, correct? How would I do it that way for Duo? I'll try my grep-fu and google-fu in the meantime. I assume you are talking about loading the overlay from armbianEnv.txt i.e. https://docs.armbian.com/User-Guide_Allwinner_overlays

@martinayotteI finally got my VM cranking and build pulled down. Looking around based on what you said wouldn't something duo specific be better off in something like ./patch/kernel/sunxi-dev/board-h2plus-nanopi-duo-add-device.patch? I still need to look at Makefile, but this should only impact Duo.

OK, let me try that. Working on a new build VM today.

@martinayotte yes, and in that case XU3 had same lines, but my question was how do I do this for Duo using overlay, but make it part of normal build process?

@martinayotte so I'm trying to make this part of the build like https://github.com/armbian/build/pull/2449 so it's part of the image. How would that work?

@martinayotte I need to know how to do overlay. I already know how to do gpio-line-names already, thanks.

@martinayotteis this documented somewhere? I'll give that a try.