On Mon, Apr 01, 2019 at 10:11:44PM +1100, Michael Ellerman wrote:
> Anyway I think what you've done in next, make the code depend on
> COMMON_CLOCK, is the best option. If anyone cares about that driver on
> powerpc platforms that don't support COMMON_CLOCK they should speak up.
It's probably fin
Mark Brown writes:
> On Wed, Mar 27, 2019 at 03:29:55PM +1100, Michael Ellerman wrote:
>> Mark Brown writes:
>
>> > Hrm, seems PowerPC is still not using the common clock API - is there
>> > any plan for that? There are some ASoC PowerPC uses so it's going to be
>> > a bit of an issue as we expa
On Wed, Mar 27, 2019 at 03:29:55PM +1100, Michael Ellerman wrote:
> Mark Brown writes:
> > Hrm, seems PowerPC is still not using the common clock API - is there
> > any plan for that? There are some ASoC PowerPC uses so it's going to be
> > a bit of an issue as we expand our use of the clock API
Mark Brown writes:
> On Tue, Mar 26, 2019 at 01:33:49PM +1100, Stephen Rothwell wrote:
>
>> After merging the sound-asoc tree, today's linux-next build (powerpc
>> allyesconfig) failed like this:
>
>> sound/soc/codecs/tlv320aic32x4-clk.c: In function 'clk_aic32x4_pll_prepare':
>> include/linux/ker
