On Thu, Apr 11, 2024 at 06:33:17AM +0300, Dmitry Baryshkov wrote: > On Thu, 11 Apr 2024 at 06:19, Bjorn Andersson <andersson@xxxxxxxxxx> wrote: > > > > On Wed, Apr 10, 2024 at 01:12:15AM +0300, Dmitry Baryshkov wrote: > > > On Tue, 9 Apr 2024 at 23:02, Konrad Dybcio <konrad.dybcio@xxxxxxxxxx> wrote: > > > > On 4/9/24 20:27, Dmitry Baryshkov wrote: > > > > > Enable CONFIG_INTERCONNECT_QCOM_SM6115 as module to enable the > > > > > interconnect driver for the SoC used on Qualcomm Robotics RB2 board. > > > > > > > > > > Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@xxxxxxxxxx> > > > > > --- > > > > > > > > =y for console? > > > > > > I think with pinctrl being set to m it won't reach the console anyway. > > > And earlycon should work w/o ICC driver if I'm not mistaken. > > > > > > Several other Qualcomm platforms also have interconnects built as > > > modules in defconfig. I really suppose that we should move all such > > > drivers to =m and force using initrd. But this sounds like a topic for > > > plumbers. > > > > > > > That currently does not work very well, because if you probe defer the > > UART into the future e.g. systemd will open /dev/console before it > > exist - with no interest in reopening that later. > > > > So, if you care about UART, that is suboptimal. > > > > Resolve this, and I'd be happy to see them all go =m. > > BTW, so even if /dev/console doesn't handle switching behind the scenes, > Systemd at initramfs opens /dev/console, maybe fails, loads icc and > other modules. Then it does pivot_root and executes systemd on the > rootfs. At this point the /dev/console exists and the systemd should > continue without any issues. > On which console does it ask for your passphrase for your encrypted rootfs? Closer to home, I do most of my testing in a ramdisk, not having working /dev/console is a problem for m. Regards, Bjorn