IQureshi Posted September 22, 2018 Share Posted September 22, 2018 I am trying to access the audio codec SSM2603 on ZYBO over i2c interface from linux user-space for some register get and set, what i did so far I enabled in the device-tree PS I2C_0 in system-user.dtsi &i2c0 { ssm2603: ssm2603@1a{ #sound-dai-cells = <0>; compatible = "adi,ssm2603"; reg = <0x1a>; }; i2cdetect -l output i2c-1 i2c Cadence I2C at e0004000 I2C adapter i suppose i2c coec should appear on address 0x1a but nothing i2cdetect -y -r 1 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- if i add the codec drivers in my kernel snd_soc_ssm2602_i2c.ko and snd_soc_ssm2602.ko the i2cdetect -y -r 1 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- UU -- -- -- -- -- which means the i2c device is detected on 0x1a address but its been used by the driver. what i want to do is to make the raw i2c register get /set using i2cget/i2cset but the codec didn't appear without driver, any clue? Link to comment Share on other sites More sharing options...
vicentiu Posted October 5, 2018 Share Posted October 5, 2018 A few questions: What linux kernel sources are you using? Xilinx, Digilent, or other? How are you building the linux image? Petalinux or something else? What i2c driver are you using and what IP are you using for i2c? The i2c from PS or the xiic IP in the PL? Link to comment Share on other sites More sharing options...
Question
IQureshi
I am trying to access the audio codec SSM2603 on ZYBO over i2c interface from linux user-space for some register get and set, what i did so far
I enabled in the device-tree PS I2C_0 in system-user.dtsi
&i2c0 {
ssm2603: ssm2603@1a{
#sound-dai-cells = <0>;
compatible = "adi,ssm2603";
reg = <0x1a>;
};
i2cdetect -l output
i2c-1 i2c Cadence I2C at e0004000 I2C adapter
i suppose i2c coec should appear on address 0x1a but nothing
i2cdetect -y -r 1
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
if i add the codec drivers in my kernel snd_soc_ssm2602_i2c.ko and snd_soc_ssm2602.ko the
i2cdetect -y -r 1
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- UU -- -- -- -- --
which means the i2c device is detected on 0x1a address but its been used by the driver.
what i want to do is to make the raw i2c register get /set using i2cget/i2cset but the codec didn't appear without driver, any clue?
Link to comment
Share on other sites
1 answer to this question
Recommended Posts
Archived
This topic is now archived and is closed to further replies.