[Invalid] - HifiBerry digi with orange pi H3 PC PLUS

[Nabeel]

Hi All,

 

Can anyone help in setting up HifiBerry Digi + with Opi PC Plus with i2s0.The HIfi Berry is based on wm8804 codec and it acts as a master while i2s on Opi acts as a slave

I havent any examples of using i2s in slave mode on H3 boards so just need some help.

Kernel is 5.10.19 built with Armbian Build system.

This is the driver I am using

https://github.com/raspberrypi/linux/blob/rpi-5.10.y/sound/soc/bcm/rpi-wm8804-soundcard.c        on my PC PLUS

 

This is my dts:

/dts-v1/;
/plugin/;

/ {
  compatible = "allwinner,sun8i-h3";

  fragment@0 {
          target = <&i2c0>;
          __overlay__ {
                status = "okay";
                wm8804: wm8804@3b {
                #sound-dai-cells = <0>;
                compatible = "wlf,wm8804";
                reg = <0x3b>;
                status = "okay";
                };
          };
  };
  fragment@1 {
    target = <&i2s0>;
    __overlay__ {
      status = "okay";
      pinctrl-0 = <&i2s0_pins>;
      sound-dai = <&wm8804>;
      pinctrl-names = "default";
      
    };
  };

  fragment@2 {
    target-path = "/";
    __overlay__ {
      sound_i2s {
        compatible = "hifiberry,hifiberry-digi";
        i2s-controller = <&i2s0>;
        hifiberry,format = "i2s";
        hifiberry,bitclock-master = <&sndcodec>;
    hifiberry,frame-master = <&sndcodec>;      
        #hifiberry,mclk-fs = <256>;
        #hifiberry,frame-inversion;
        status = "okay";

        hifiberry,cpu {
        sound-dai = <&i2s0>;
        dai-tdm-slot-num = <0x2>;
        dai-tdm-slot-width = <0x20>;
                         
        };

        sndcodec: hifiberry,codec {
          sound-dai = <&wm8804>;
          system-clock-frequency = <11289600>;
          
        };

 

Many Thanks for your help.

[Werner]

Your issue report is not a valid bug report per the Armbian bug reporting instructions (https://www.armbian.com/bugs).  With limited resources the Armbian project is only able to spend time on issues where all the requested information has been provided and for only the boards/images/software that are supported.  Your report is invalid for one or more of the following reasons (non-exhaustive list):

 

• it is for an unsupported board or image (CSC/EOS/WIP/edge)
• it is for software that is not supported (such as userspace modules installed on top of the core operating system)
• it has been logged in the wrong forum (for example requests for help that are not actual bug reports)
• it lacks requested data (armbianmonitor output)
• it could have been easily solved by a quick search and/or reading documentation

 

Please review what you have submitted and the bug logging instructions (https://www.armbian.com/bugs) and either add the required information or open a new topic in the correct forum (such as Common issues / peer to peer technical support or General chit chat)