On Mon, Dec 6, 2010 at 9:46 PM, Mark Brown broonie@opensource.wolfsonmicro.com wrote:
On Sun, Dec 05, 2010 at 12:40:01AM +0900, Jassi Brar wrote:
It's necessary evil ATM. There is no access to SPDIF device in machine code and we need to get/set the clock. So the soc-audio is used as a place-holder.
In order to do this you need to tell the clock framework about the ASoC virtual device - once you're doing stuff like that you may as well just fix the S/PDIF driver to let you do what you need.
Assuming I understand you correctly, the problem still remains of having the S/PDIF driver to setup clock hierarchies -- which is the job of the board init code, IMHO. So until we have proper clock subsystem and board init code to handle such scenarios we have to do that in ASoC machine driver in such hackish way.