[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20140127205925.GE11841@sirena.org.uk>
Date: Mon, 27 Jan 2014 20:59:25 +0000
From: Mark Brown <broonie@...nel.org>
To: Bo Shen <voice.shen@...el.com>
Cc: nicolas.ferre@...el.com, plagnioj@...osoft.com,
linux-sound@...r.kernel.org, alsa-devel@...a-project.org,
linux-arm-kernel@...ts.infradead.org,
Liam Girdwood <lgirdwood@...il.com>,
Jaroslav Kysela <perex@...ex.cz>, Takashi Iwai <tiwai@...e.de>,
Linus Walleij <linus.walleij@...aro.org>,
Wolfram Sang <wsa@...-dreams.de>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/3] ASoC: atmel_wm8904: make it available to choose clock
On Thu, Jan 16, 2014 at 09:31:23AM +0800, Bo Shen wrote:
> >Shouldn't this code be in the DAI driver? Otherwise this series looks
> >fine to me, though the DT folks might have something to say I guess.
> For audio on Atmel SoC, it depends on three device nodes, one is
> SSC node, one is the codec node and the sound node.
> The sound node will parse by machine driver, and machine driver is
> mainly for hardware connection. As the "clk_from_rk_pin" is decided
> by hardware, so, I put it here.
> If I move the code to dai driver, it will parse the sound node in
> dai driver, I think it will make the code a little bit not explicit.
> What do you think?
I think it should just be a property of the DAI device. It's true that
the card defines the connections but if something is going to be an
option that's there for most if not all systems then putting it in the
device driver means less effort on each integration.
Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)
Powered by blists - more mailing lists