On Wed, Dec 13, 2017 at 10:47:32AM +, Mark Brown wrote:
> The things the driver is doing automatically to mute the DACs and ADCs
> should be moved to user control if they're not suitable for doing
> automatically.
>
The mutes can work normally without the PLL stuff. I have removed the PLL
On Wed, Dec 13, 2017 at 10:47:32AM +, Mark Brown wrote:
> The things the driver is doing automatically to mute the DACs and ADCs
> should be moved to user control if they're not suitable for doing
> automatically.
>
The mutes can work normally without the PLL stuff. I have removed the PLL
On Tue, Dec 12, 2017 at 04:51:35PM -0600, Steven Eckhoff wrote:
> Also I am not sure what you mean with the mute controls. Could you
> elaborate more on this?
The things the driver is doing automatically to mute the DACs and ADCs
should be moved to user control if they're not suitable for doing
On Tue, Dec 12, 2017 at 04:51:35PM -0600, Steven Eckhoff wrote:
> Also I am not sure what you mean with the mute controls. Could you
> elaborate more on this?
The things the driver is doing automatically to mute the DACs and ADCs
should be moved to user control if they're not suitable for doing
On Tue, Dec 12, 2017 at 04:51:35PM -0600, Steven Eckhoff wrote:
> > > > +static int tscs42xx_mute_stream(struct snd_soc_dai *dai, int mute, int
> > > > stream)
> > > > +{
> > > > + struct snd_soc_codec *codec = dai->codec;
> > > > + int ret;
> > > > +
> > > > + if (mute)
> > >
On Tue, Dec 12, 2017 at 04:51:35PM -0600, Steven Eckhoff wrote:
> > > > +static int tscs42xx_mute_stream(struct snd_soc_dai *dai, int mute, int
> > > > stream)
> > > > +{
> > > > + struct snd_soc_codec *codec = dai->codec;
> > > > + int ret;
> > > > +
> > > > + if (mute)
> > >
On Tue, Dec 12, 2017 at 03:31:16PM -0600, Steven Eckhoff wrote:
> On Tue, Dec 12, 2017 at 04:32:54PM +, Mark Brown wrote:
> > On Mon, Dec 11, 2017 at 01:54:25PM -0600, Steven Eckhoff wrote:
> > > Currently there is no support for the TSCS42xx audio CODEC.
> > >
> > > Add support for it.
> > >
On Tue, Dec 12, 2017 at 03:31:16PM -0600, Steven Eckhoff wrote:
> On Tue, Dec 12, 2017 at 04:32:54PM +, Mark Brown wrote:
> > On Mon, Dec 11, 2017 at 01:54:25PM -0600, Steven Eckhoff wrote:
> > > Currently there is no support for the TSCS42xx audio CODEC.
> > >
> > > Add support for it.
> > >
On Tue, Dec 12, 2017 at 04:32:54PM +, Mark Brown wrote:
> On Mon, Dec 11, 2017 at 01:54:25PM -0600, Steven Eckhoff wrote:
> > Currently there is no support for the TSCS42xx audio CODEC.
> >
> > Add support for it.
> >
> > v5 attempts to address all issues raised in the previous reviews.
> >
On Tue, Dec 12, 2017 at 04:32:54PM +, Mark Brown wrote:
> On Mon, Dec 11, 2017 at 01:54:25PM -0600, Steven Eckhoff wrote:
> > Currently there is no support for the TSCS42xx audio CODEC.
> >
> > Add support for it.
> >
> > v5 attempts to address all issues raised in the previous reviews.
> >
On Tue, Dec 12, 2017 at 02:10:09PM +0100, Takashi Iwai wrote:
> On Tue, 12 Dec 2017 14:04:01 +0100,
> Charles Keepax wrote:
> >
> > On Mon, Dec 11, 2017 at 01:54:25PM -0600, Steven Eckhoff wrote:
> > > Currently there is no support for the TSCS42xx audio CODEC.
> > >
> > > Add support for it.
>
On Tue, Dec 12, 2017 at 02:10:09PM +0100, Takashi Iwai wrote:
> On Tue, 12 Dec 2017 14:04:01 +0100,
> Charles Keepax wrote:
> >
> > On Mon, Dec 11, 2017 at 01:54:25PM -0600, Steven Eckhoff wrote:
> > > Currently there is no support for the TSCS42xx audio CODEC.
> > >
> > > Add support for it.
>
On Tue, Dec 12, 2017 at 01:04:01PM +, Charles Keepax wrote:
> On Mon, Dec 11, 2017 at 01:54:25PM -0600, Steven Eckhoff wrote:
> > Currently there is no support for the TSCS42xx audio CODEC.
> >
> > Add support for it.
> >
> > v5 attempts to address all issues raised in the previous reviews.
On Tue, Dec 12, 2017 at 01:04:01PM +, Charles Keepax wrote:
> On Mon, Dec 11, 2017 at 01:54:25PM -0600, Steven Eckhoff wrote:
> > Currently there is no support for the TSCS42xx audio CODEC.
> >
> > Add support for it.
> >
> > v5 attempts to address all issues raised in the previous reviews.
On Mon, Dec 11, 2017 at 01:54:25PM -0600, Steven Eckhoff wrote:
> Currently there is no support for the TSCS42xx audio CODEC.
>
> Add support for it.
>
> v5 attempts to address all issues raised in the previous reviews.
>
> Thank you to everyone who has invested their time reviewing these
>
On Mon, Dec 11, 2017 at 01:54:25PM -0600, Steven Eckhoff wrote:
> Currently there is no support for the TSCS42xx audio CODEC.
>
> Add support for it.
>
> v5 attempts to address all issues raised in the previous reviews.
>
> Thank you to everyone who has invested their time reviewing these
>
On Tue, 12 Dec 2017 14:04:01 +0100,
Charles Keepax wrote:
>
> On Mon, Dec 11, 2017 at 01:54:25PM -0600, Steven Eckhoff wrote:
> > Currently there is no support for the TSCS42xx audio CODEC.
> >
> > Add support for it.
> >
> > v5 attempts to address all issues raised in the previous reviews.
> >
On Tue, 12 Dec 2017 14:04:01 +0100,
Charles Keepax wrote:
>
> On Mon, Dec 11, 2017 at 01:54:25PM -0600, Steven Eckhoff wrote:
> > Currently there is no support for the TSCS42xx audio CODEC.
> >
> > Add support for it.
> >
> > v5 attempts to address all issues raised in the previous reviews.
> >
On Mon, Dec 11, 2017 at 01:54:25PM -0600, Steven Eckhoff wrote:
> Currently there is no support for the TSCS42xx audio CODEC.
>
> Add support for it.
>
> v5 attempts to address all issues raised in the previous reviews.
>
> Thank you to everyone who has invested their time reviewing these
>
On Mon, Dec 11, 2017 at 01:54:25PM -0600, Steven Eckhoff wrote:
> Currently there is no support for the TSCS42xx audio CODEC.
>
> Add support for it.
>
> v5 attempts to address all issues raised in the previous reviews.
>
> Thank you to everyone who has invested their time reviewing these
>
20 matches
Mail list logo
