On Mon, Sep 28, 2015 at 09:49:35PM +0300, Jyri Sarha wrote:
> On 09/19/15 21:42, Mark Brown wrote:
> >What's the use case again? Can we address this by converting the
> >relevant drivers to the clock API (or improving their clock API
> >support)?
> Sorry, I forgot to reply this earlier. The reas
On 09/19/15 21:42, Mark Brown wrote:
On Fri, Sep 11, 2015 at 04:18:02PM +0300, Jyri Sarha wrote:
The updated binding provides a way to set clock-ID and direction
parameters for DAI drivers set_sysclk() call back.
I proposed something similar about a year ago, but Mark rejected that
at the ti
On Fri, Sep 11, 2015 at 04:18:02PM +0300, Jyri Sarha wrote:
> The updated binding provides a way to set clock-ID and direction
> parameters for DAI drivers set_sysclk() call back.
> I proposed something similar about a year ago, but Mark rejected that
> at the time. This RFC is to start that disc
The updated binding provides a way to set clock-ID and direction
parameters for DAI drivers set_sysclk() call back.
Signed-off-by: Jyri Sarha
---
I proposed something similar about a year ago, but Mark rejected that
at the time. This RFC is to start that discussion again. This time
before I do an
