From: Jeeja KP <jeeja.kp@intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: tiwai@suse.de, patches.audio@intel.com,
alsa-devel@alsa-project.org, liam.r.girdwood@intel.com
Subject: Re: [PATCH v4 2/9] ASoC: Intel: Skylake: Add set_tristate DAI ops to enable SSP MCLK
Date: Tue, 10 Jan 2017 15:01:13 +0530 [thread overview]
Message-ID: <20170110093112.GA15578@kpjeeja-desk> (raw)
In-Reply-To: <20170106183233.n6vbqzyczkclnbtc@sirena.org.uk>
On Fri, Jan 06, 2017 at 06:32:33PM +0000, Mark Brown wrote:
> On Mon, Jan 02, 2017 at 12:44:29PM +0530, jeeja.kp@intel.com wrote:
> > From: Jeeja KP <jeeja.kp@intel.com>
> >
> > Some machine requires MCLK to be enabled before SSP start up, so add
> > set_tristate() DAI ops to enable/disable SSP MCLK. This ops will be
> > called from machine which requires early MCLK and removes the usage of
> > enabling early MLCK in platform DAI prepare by default which is not
> > machine specific.
>
> This isn't an *obvious* use of the tristate operation...
>
> > + /*
> > + * To enable ssp clk explicitly before gateway copier is configured,
> > + * need to use dma control IPC.
> > + * Disable will be done when DSP gateway copier modules are deleted.
> > + */
> > + if (!tristate)
> > + return skl_dsp_set_dma_control(ctx, mconfig);
>
> So we never clear this? And to be frank I'd have no idea looking at
> this that it's doing anything to do with clocks though that's a bit of a
> separate thing. It feels like DAPM might be a more natural place to do
> this, have a clock widget supplying the AIF widget for the interface.
> That'd be a bit more idiomatic.
The clk will be cleared, when DSP pipeline is deleted, that is when audio device
is closed.
My bad, yes this is not the correct usage of tristate operation, we need to model
it as a clock supply widget, will rework on this patch.
--
next prev parent reply other threads:[~2017-01-10 9:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-02 7:14 [PATCH v4 0/9] ASoC: Intel: Skylake: Driver updates jeeja.kp
2017-01-02 7:14 ` [PATCH v4 1/9] ALSA: hda: check stream decoupled register state jeeja.kp
2017-01-02 7:14 ` [PATCH v4 2/9] ASoC: Intel: Skylake: Add set_tristate DAI ops to enable SSP MCLK jeeja.kp
2017-01-06 18:32 ` Mark Brown
2017-01-10 9:31 ` Jeeja KP [this message]
2017-01-02 7:14 ` [PATCH v4 3/9] ASoC: Intel: Skylake: Remove unused SSP BE prepare DAI ops jeeja.kp
2017-01-02 7:14 ` [PATCH v4 4/9] ASoC: Intel: Skylake: Add supply widget as non DSP widget jeeja.kp
2017-01-02 7:14 ` [PATCH v4 5/9] ASoC: Intel: Skylake: Add supply widget in skl_nau_max machine jeeja.kp
2017-01-02 7:14 ` [PATCH v4 6/9] ASoC: Intel: Skylake: Add supply widget in bxt_da_max machine jeeja.kp
2017-01-06 18:34 ` Mark Brown
2017-01-02 7:14 ` [PATCH v4 7/9] ASoC: Intel: Skylake: Don't reset pass-through pipe in BE prepare jeeja.kp
2017-01-02 7:14 ` [PATCH v4 8/9] ASoC: Intel: Skylake: set the resume point to LPIB jeeja.kp
2017-01-02 7:14 ` [PATCH v4 9/9] ASoC: hdac_hdmi: Enable pin and converter in prepare jeeja.kp
2017-01-19 18:03 ` Applied "ASoC: hdac_hdmi: Enable pin and converter in prepare" to the asoc tree Mark Brown
2017-01-02 10:01 ` [PATCH v4 0/9] ASoC: Intel: Skylake: Driver updates Vinod Koul
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170110093112.GA15578@kpjeeja-desk \
--to=jeeja.kp@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=liam.r.girdwood@intel.com \
--cc=patches.audio@intel.com \
--cc=tiwai@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).