Linux Kernel 3.4.91 instantiating audio codec without device tree
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
At the moment I am dealing with an ARM based device shipped with sources for Kernel 3.4.91. The name of the platform is mdm9615.
The particular problem is how to instantiate an audio codec, TLV320AIC3104. It is connected to the I2C bus for configuration and to the I2S for digital audio streaming. What should be done in order to use this device? In the Kernel documentation I have seen three different ways of instantiating I2C. Since 3.4.91 doesn't support the device tree, it seems like I need to change board source files and to add i2c_register_board_info instances. However, since the codec is also part of the audio path, it should also be somehow declared to the sound subsystem. What is the proper way of making this work?
linux-kernel audio device-tree
asked Oct 8 '17 at 16:04
Nexy_sm
134
add a comment |Â
up vote
0
down vote
favorite
At the moment I am dealing with an ARM based device shipped with sources for Kernel 3.4.91. The name of the platform is mdm9615.
The particular problem is how to instantiate an audio codec, TLV320AIC3104. It is connected to the I2C bus for configuration and to the I2S for digital audio streaming. What should be done in order to use this device? In the Kernel documentation I have seen three different ways of instantiating I2C. Since 3.4.91 doesn't support the device tree, it seems like I need to change board source files and to add i2c_register_board_info instances. However, since the codec is also part of the audio path, it should also be somehow declared to the sound subsystem. What is the proper way of making this work?
linux-kernel audio device-tree
asked Oct 8 '17 at 16:04
Nexy_sm
134
There is a lot of information that you left out here like what board support package used, what micro processor, and if you compiled the kernel, but if you have a GPIO driver you might be able to export and use the GPIO pin from user space. Check out this kernel doc
– jc__
Oct 9 '17 at 13:51
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
At the moment I am dealing with an ARM based device shipped with sources for Kernel 3.4.91. The name of the platform is mdm9615.
The particular problem is how to instantiate an audio codec, TLV320AIC3104. It is connected to the I2C bus for configuration and to the I2S for digital audio streaming. What should be done in order to use this device? In the Kernel documentation I have seen three different ways of instantiating I2C. Since 3.4.91 doesn't support the device tree, it seems like I need to change board source files and to add i2c_register_board_info instances. However, since the codec is also part of the audio path, it should also be somehow declared to the sound subsystem. What is the proper way of making this work?
linux-kernel audio device-tree
asked Oct 8 '17 at 16:04
Nexy_sm
134
At the moment I am dealing with an ARM based device shipped with sources for Kernel 3.4.91. The name of the platform is mdm9615.
The particular problem is how to instantiate an audio codec, TLV320AIC3104. It is connected to the I2C bus for configuration and to the I2S for digital audio streaming. What should be done in order to use this device? In the Kernel documentation I have seen three different ways of instantiating I2C. Since 3.4.91 doesn't support the device tree, it seems like I need to change board source files and to add i2c_register_board_info instances. However, since the codec is also part of the audio path, it should also be somehow declared to the sound subsystem. What is the proper way of making this work?
linux-kernel audio device-tree
linux-kernel audio device-tree
asked Oct 8 '17 at 16:04
Nexy_sm
134
asked Oct 8 '17 at 16:04
Nexy_sm
134
edited Oct 16 '17 at 9:43
asked Oct 8 '17 at 16:04
Nexy_sm
134
asked Oct 8 '17 at 16:04
Nexy_sm
134
asked Oct 8 '17 at 16:04
Nexy_sm
134
134
There is a lot of information that you left out here like what board support package used, what micro processor, and if you compiled the kernel, but if you have a GPIO driver you might be able to export and use the GPIO pin from user space. Check out this kernel doc
– jc__
Oct 9 '17 at 13:51
add a comment |Â
There is a lot of information that you left out here like what board support package used, what micro processor, and if you compiled the kernel, but if you have a GPIO driver you might be able to export and use the GPIO pin from user space. Check out this kernel doc
– jc__
Oct 9 '17 at 13:51
There is a lot of information that you left out here like what board support package used, what micro processor, and if you compiled the kernel, but if you have a GPIO driver you might be able to export and use the GPIO pin from user space. Check out this kernel doc
– jc__
Oct 9 '17 at 13:51
There is a lot of information that you left out here like what board support package used, what micro processor, and if you compiled the kernel, but if you have a GPIO driver you might be able to export and use the GPIO pin from user space. Check out this kernel doc
– jc__
Oct 9 '17 at 13:51
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f396863%2flinux-kernel-3-4-91-instantiating-audio-codec-without-device-tree%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
There is a lot of information that you left out here like what board support package used, what micro processor, and if you compiled the kernel, but if you have a GPIO driver you might be able to export and use the GPIO pin from user space. Check out this kernel doc
– jc__
Oct 9 '17 at 13:51