From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Rander Wang <rander.wang@linux.intel.com>, broonie@kernel.org
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH] ASoC:hdac_hda: use correct format to setup hda codec
Date: Mon, 25 Feb 2019 12:04:13 -0600 [thread overview]
Message-ID: <a7d6f54c-5466-ec63-4dec-cb403eed7b86@linux.intel.com> (raw)
In-Reply-To: <20190225074845.73950-1-rander.wang@linux.intel.com>
On 2/25/19 1:48 AM, Rander Wang wrote:
> The current implementation of the hdac_hda codec results in zero-valued
> samples on capture and noise with headset playback when SOF is used on
> platforms with an on-board HDaudio codec. This is root-caused to SOF
> using be_hw_params_fixup, and the prepare() call using invalid runtime
> fields to determine the format.
>
> This patch moves the format handling to the hw_params() callback, as
> done already for hdac_hdmi, to make sure the fixed-up information is
> taken into account but keeps the codec initialization in prepare() as
> the stream_tag is only available at that time. Moving everything in the
> prepare() callback is possible but the code is less elegant so this
> two-step solution was chosen.
>
> The solution was tested with the SST driver with no regressions, and all
> the issues with SOF playback and capture are solved.
>
> Signed-off-by: Rander Wang <rander.wang@linux.intel.com>
I suggested to Rander to send this patch upstream last week, but since
there are two additional fixes suggested over the week-end on the SOF
github we probably want to discard this patch.
We will resubmit a series once all the current ASoC+HDaudio issues are
sorted out (both with the Skylake and SOF drivers). It's easier for
reviewers and people backporting stuff.
prev parent reply other threads:[~2019-02-25 18:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-25 7:48 [PATCH] ASoC:hdac_hda: use correct format to setup hda codec Rander Wang
2019-02-25 18:04 ` Pierre-Louis Bossart [this message]
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=a7d6f54c-5466-ec63-4dec-cb403eed7b86@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=rander.wang@linux.intel.com \
/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).