the WM8962 driver can not be probe

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

the WM8962 driver can not be probe

1,047 Views
captain_huang
Contributor I

In our i.mx6 board ,we connect the audio device WM8962 to I2C2,while the sabre_SDP board connect the device to I2C1.

we also modify the kernel file "board-mx6q_sabresd.c" like below:

static struct i2c_board_info mxc_i2c0_board_info[] __initdata = {

#if 0

  {

  I2C_BOARD_INFO("wm8962", 0x1a),

  .platform_data = (void *)&wm8962_config_data,

  },

#endif

......

};

static struct i2c_board_info mxc_i2c1_board_info[] __initdata = {

#if 1

  {

  I2C_BOARD_INFO("wm8962", 0x1a),

  .platform_data = (void *)&wm8962_config_data,

  },

#endif

};

but we found that the WM8962 driver cannot be probed, and no wm8962 audio device found in the alsa list. if I connect it to the I2C1, it probed successful.

so i don't know what 's the problem, please help me to fix it ,thanks!

Labels (1)
0 Kudos
5 Replies

763 Views
igorpadykov
NXP Employee
NXP Employee

Hi chao

in first place I would suggest to test with i.MX 6Series Platform SDK

if WM8962 can be discovered on I2C2.

As for Linux, there are comments file "board-mx6q_sabresd.c" :

/* On mx6x sabresd board i2c2 iomux with hdmi ddc,

* the pins default work at i2c2 function,

when hdcp enable, the pins should work at ddc function */

So please try to disable hdmi, i.MX_6Dual6Quad_Linux_Reference_Manual.pdf

L3.0.35_4.1.0_LINUX_DOCS

shows how to do that. Also Sabre SD board schematic

SPF-27392 rev.C3.pdf p.3 suggests:

Depopulate R153 and R154 (schematic page 22)

This removes HDMI comms channel from I2C2.

Best regards

chip

-----------------------------------------------------------------------------------------------------------------------

Note: If this post answers your question, please click the Correct Answer button. Thank you!

-----------------------------------------------------------------------------------------------------------------------

763 Views
captain_huang
Contributor I

hi chip,

when i test this ,i have not  connected  the HDMI Display ,

so i don't think the HDMI occurs the problem , i just think it's somewhere in the software occurs this problem.

Best regards

0 Kudos

763 Views
igorpadykov
NXP Employee
NXP Employee

Hi chao

it does not matter, connected you hdmi or

not. Software configured pins for hdmi.

Best regards

chip

0 Kudos

763 Views
captain_huang
Contributor I

hi chip,

but i also connect the touch screen and OV5640 sensor to the I2C2, these devices work normally.

Best regards

0 Kudos

763 Views
igorpadykov
NXP Employee
NXP Employee

Hi chao

you may wish to debug it with

AN4553 Using Open Source Debugging Tools for Linux on i.MX Processors

and oscilloscope.

Best regards

chip

0 Kudos