I have an out-of-tree kernel module for my device, which is configured through devicetree. The problem is that when the system boots the module does not get loaded by the kernel.
The only option to load it is to manually call modprobe mymodule, then kernel finds it (it is installed under /lib/modules/5.15.71+g95448dd0dc9b/extra/) and loads it correctly.

I am loading a custom linux kernel. I am updating DTB timer to match emulation scaling ratio. In bootup logs, I am able to see the value I am setting.
#sched_clock : running at ‘X’ MHZ.
Is there anyway to update this post bootup to another value ?

In the past (Kernel 4.9, 5.10, 5.15) I’ve “hijacked” pinmux definitions in the kernel device tree to set them into gpio state. Since my latest upgrade to kernel 6.1 this approach is not working anymore. The pins witch are not used by any driver will stay in there inital mode by means of pinmuxing. So I was driven to use led-gpio and gpio-key for getting out- and inputs. That feels somehow uncomfortable. As the led-gpio for an user-space driven OLED display or an custom led board hooked up to spi should not have an led-gpio pin named led / display-reset.

We have multiple GPIO controllers where each pin effectively only serves one purpose. For example, if the device-tree entry is the following:

I’m using LS1028a-rdb board which in its device tree defines the following aliases:

I’m trying to bring up rtc-rv3028 clock on my board through device tree overlays. My board is LS1028a-rdb. I need to alias my clock as rtc2
The board device tree has the following aliases: