Hover

Now the mainline u-boot has decent pcie and pcie phy driver for rk3399. The only deficiency is the clock of pcie phy not included. The first attached patch add this clock so that u-boot proper can load linux kernel residing in an ext4 partition of nvme ssd.pcie_phy_clk.patch The second patch enables loading the environment from a file in an ext4 partition of nvme ssd.env_nvme.patch More conveniently the u-boot proper(u-boot.itb) could be an ordinary file residing in an ext4 partition of nvme ssd. The idbloader(tpl/spl in spi/emmc/sdcard) could load it if pcie nvme support is enabled in spl. That's the third attachment.spl_nvme.patch The usb and usb phy is working so the usbkbd can be used to choose a boot option without a serial port debug console. The last attachment set the default env to enable usbkbd and vidconsole.env_vidconsole_usbkbd.patch And for your convenience my u-boot config for nanopc-t4 also attached here.u-boot.config

I want to use the mainline u-boot spl to load the u-boot proper(u-boot.itb) from nvme, so that the only part off the nvme is the tpl/spl in the emmc/sd/spi flash. But now the mainline u-boot has no pcie driver and no nvme support in spl. I have found the radxa guys using their u-boot in spi flash to boot kernel from nvme. But their pcie driver(https://github.com/radxa/u-boot/commit/096f2c16bbfa24c93a4c87e31334d5b5064dfd0a) has a limitation: It can not be used in u-boot spl, or it would not function properly in u-boot proper and fail the boot. After some frustrating tryings and compare with the linux driver, I found that the port initialization process was short cutted and causing the reinitialization malfunctioned. After this correction the pcie driver can be used in spl: it can be reinitialized correctly in u-boot proper. Bring nvme support into spl is just a mimic from the spl_mmc and spl_usb driver. Another patch for fixing spl_ext as I want the u-boot.itb and kernel in a ext4 partition on nvme but the existing spl_ext can not load the u-boot.itb properly. With these patches I can boot nanopc-t4 with u-boot.itb and linux kernel in nvme boot partition and only the u-boot tpl/spl in emmc. Btw, now the vidconsole of the mainline u-boot is working on rk3399, but usb phys are still missing. pcie.patch rk3399_boot_nvme.patch spl_ext_fix.patch spl_nvme.patch

These mixer settings gave a crippled playback on my nanopc t4. The following gave a normal one. amixer set 'HPO L' on amixerset 'HPO R' on amixerset 'HPOVOL L' off amixer set 'HPOVOL R' off amixer set 'HPO MIX HPVOL' off amixer set 'OUT MIXL DAC L1' off amixer set 'OUT MIXR DAC R1' off amixer set 'Stereo DAC MIXL DAC L1' on amixer set 'Stereo DAC MIXR DAC R1' on amixer set 'HPO MIX DAC1' on amixer set 'DD MIXL DAC L1' on amixer set 'DD MIXR DAC R1' on

Thank you @iamdrq for the mclk patch of rt5651. I used the patch from armbian build and heard the very first sound in the earphone since I got my nanopc-t4.

@piter75Thanks for the head up. I know on t4 it's attached to i2s0 and the mixer settings discussed in the other threads. Maybe I should test the codec on friendlyarm's android image to make sure the hardware is working as I had never heard any playback since I got the t4.

Even confusing the bluetooth came to work unexpectedly after I adjusted i2c1 parameters in dtb in order to get sound from rt5651 and reboot. While cannot get sound playback from codec still. There seems a ghost in my nanopc t4.

@piter75 Just asked for confirmation. As I am confused.

@piter75Thanks. Is the CONFIG_SND_SOC_ROCKCHIP_RT5651only select the codec and i2s, without additional source files like rockchip_5640.c?

@piter75 I am trying to get rt5651 sound on nanopc t4 kernel 5.4. But only static noise in headphone now. If you have rt5651 sound on m4, would you please publish you kernel config and patch(if any)? And the bluetooth is broken on 5.4, while it worked on 5.2. Does your bluetooth work well on 5.4?

It seems on mainline kernel 5.3 & 5.4 the serdev bcm4356 driver is broken, while it worked on kernel 5.2. Anyone on nanopc t4 or m4 found the same problem? Anything sent to the module via __hci_cmd_sync resulted in timeout. There was a refactor of the underlying 8250_dw uart driver after kernel 5.2, but I can not tell anything break the communication from the git diff.

Glad to know the mainline u-boot progress. Give it another try. Now the tpl-spl loads u-boot.itb. It seems aclk-vop and hclk-vop rate setting are missing. But with these rate settings added only got a fake vidconsole, only registered the stdio driver without any signal sent to hdmi. There is something missing to enable the hdmi correctly although it's probed successfully. Another mystery: the kernel would hang in very early stage after board was soft reset, but boot well after hard reset or poweron.

@MerbludThanks. But still no progress with rt5651. Maybe the module in mainline to be blamed. I know nothing about kernel sound driver, it seems beyond my touch. Btw, although panfrost works with glmark2-es2 well, it bends knees to a simple draw, causing a segfault in rockchip_dri.so which called memset(). So it's still prealpha. And no success to get vidconsole on mainline uboot, even worse the tpl-spl won't load u-boot.itb on sd. I have to resort to an old spl without tpl. Anyone got vidconsole in uboot?

@MerbludWould you please publish you sound patch here? I am trying to get rt5651 sound of nanopc t4 on mainline kernel 5.4rc, but only static noise in headphone so far. Btw bluetooth is broken on 5.3 or 5.4rc, while it's working on 5.2. Any idea? With panfrost and hantro vpu marching on well, rk3399 seems becoming a good choice to run mainline kernel.