Jump to content

amusz

Members
  • Posts

    2
  • Joined

  • Last visited

  1. I’m trying to define a simple sound card where I just have a TDM output on TDMA. Now I have defined my device tree as: sound { compatible = "amlogic,axg-sound-card"; model = "BPI-CM4IO"; audio-aux-devs = <&tdmout_a>; audio-widgets = "Speaker", "Speaker1 Left", "Speaker", "Speaker1 Right"; audio-routing = "TDMOUT_A IN 0", "FRDDR_A OUT 0", "TDM_A Playback", "TDMOUT_A OUT", "Speaker1 Left", "SPK1 OUT_A", "Speaker1 Right", "SPK1 OUT_B"; clocks = <&clkc CLKID_HIFI_PLL>, <&clkc CLKID_MPLL0>, <&clkc CLKID_MPLL1>; assigned-clocks = <&clkc CLKID_HIFI_PLL>, <&clkc CLKID_MPLL0>, <&clkc CLKID_MPLL1>; assigned-clock-parents = <0>, <0>, <0>; assigned-clock-rates = <589824000>, <270950400>, <393216000>; dai-link-0 { sound-dai = <&frddr_a>; }; dai-link-1 { sound-dai = <&tdmif_a>; dai-format = "dsp_a"; dai-slot-num= <2>; dai-tdm-slot-width = <32>; dai-tdm-slot-tx-mask-0 = <1 1>; codec { sound-dai = <&dummy_codec1>; }; }; }; however, aplay -l gives: **** List of PLAYBACK Hardware Devices **** card 0: BPICM4IO [BPI-CM4IO], device 0: fe.dai-link-0 (*) Subdevices: 1/1 Subdevice #0: subdevice #0 Why am I not seeing the sound dai link 1 ? And how then is the user supposed to select in which TDM slot to play if so. Is this expected ? As I understand it If I have several codecs I would define a different "dai-tdm-slot-tx-mask-xxx " for each dai link with a different codec. The dummy codec I’m using is based on pcm5102 as it does not require i2c for testing and probes with minimum effort. Any comments are aprecciated
  2. I'm looking for an alternative way (like raspberry pysh...) to quick compile dtb, kernel modules and kernel Image to test some custom sound cards with a banana pi cm4 as base board. In principle, I'm following the simplest path for me that it would be, compile and install specific kernel image, dtb and modules and of course an initrd image for uBoot and kernel. But I'm a bit confused about all the files in the boot partition below: xxxx@bananapicm4io:/boot$ ls armbianEnv.txt Image boot.bmp initrd.img-6.12.0 boot.cmd initrd.img-6.12.13-current-meson64 boot.scr System.map-6.12.13-current-meson64 config-6.12.0 uInitrd config-6.12.13-current-meson64 uInitrd-6.12.0 dtb uInitrd-6.12.13-current-meson64 dtb-6.12.13-current-meson64 vmlinuz-6.12.13-current-meson64 ignore 6.12.0 files because those are the ones I'm trying to compile in a host machine (also aarch64) and then install and copy into the boot partition of the bananapi. So far I'm building and installing: Image initrd.img-6.12.0 uInitrd and the dtbs of the bananapi (already verified those work with the default image 6.12.13) Kernel source is linux mainline So far does not seem to work as I get from uboot: Applying kernel provided DT fixup script (meson-fixup.scr) ## Executing script at 32000000 ## Loading init Ramdisk from Legacy Image at 13000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 271326524 Bytes = 258.8 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 04080000 Booting using the fdt blob at 0x4080000 Working FDT set to 4080000 ERROR: Failed to allocate 0x102c1d3c bytes below 0x40000000. ramdisk - allocation error booti - boot Linux kernel 'Image' format from memory any suggestions are apreccited.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines