From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: "Łukasz Majczak" <lma@semihalf.com>
Cc: alsa-devel@alsa-project.org, Jie Yang <yang.jie@linux.intel.com>,
Radoslaw Biernacki <rad@semihalf.com>,
Ross Zwisler <zwisler@google.com>,
linux-kernel@vger.kernel.org,
Liam Girdwood <liam.r.girdwood@linux.intel.com>,
Bob Brandt <brndt@google.com>, Marcin Wojtas <mw@semihalf.com>,
Alex Levin <levinale@chromium.org>
Subject: Re: [PATCH v3] ASoC: Intel: kbl_rt5663_rt5514_max98927: Split be_hw_params_fixup function
Date: Thu, 21 May 2020 12:17:49 -0500 [thread overview]
Message-ID: <475fb5c0-9b26-a8f6-c102-25c7775bc2ca@linux.intel.com> (raw)
In-Reply-To: <CAFJ_xbr8TN3ynfELJ3NQnkuRg0VRbkjB7=Cyb8yu2L==JGXJiw@mail.gmail.com>
On 5/21/20 12:08 PM, Łukasz Majczak wrote:
>>
>> don't add a new dailink, this is not right.
>>
> Can you advise a better solution how to assign different fixup
> functions to mic and to speakers? I was looking at "dmic01" dailink in
> skl_nau88l25_max98357a.c as an example.
I am not sure I follow. the DMICs are handled on a shared SSP, so how
would one set a different fixup? The word length have to be the same.
next prev parent reply other threads:[~2020-05-21 17:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-21 16:25 [PATCH v3] ASoC: Intel: kbl_rt5663_rt5514_max98927: Split be_hw_params_fixup function Lukasz Majczak
2020-05-21 16:32 ` Pierre-Louis Bossart
2020-05-21 17:08 ` Łukasz Majczak
2020-05-21 17:17 ` Pierre-Louis Bossart [this message]
2020-05-21 17:30 ` Łukasz Majczak
2020-05-21 18:10 ` Pierre-Louis Bossart
2020-06-29 11:11 ` Łukasz Majczak
2020-06-29 16:51 ` N, Harshapriya
2020-06-29 18:19 ` Łukasz Majczak
2020-06-29 22:30 ` N, Harshapriya
2020-07-01 16:37 ` N, Harshapriya
2020-07-01 16:48 ` Pierre-Louis Bossart
2020-07-01 17:00 ` N, Harshapriya
2020-07-01 17:08 ` Pierre-Louis Bossart
2020-07-02 10:09 ` Łukasz Majczak
2020-07-03 12:16 ` [PATCH v4] ASoC: Intel: kbl_rt5663_rt5514_max98927: Fix kabylake_ssp_fixup function Lukasz Majczak
2020-07-06 15:41 ` Pierre-Louis Bossart
2020-07-07 8:34 ` [PATCH v5] " Lukasz Majczak
2020-07-07 15:47 ` Pierre-Louis Bossart
2020-07-16 15:00 ` N, Harshapriya
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=475fb5c0-9b26-a8f6-c102-25c7775bc2ca@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=brndt@google.com \
--cc=levinale@chromium.org \
--cc=liam.r.girdwood@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lma@semihalf.com \
--cc=mw@semihalf.com \
--cc=rad@semihalf.com \
--cc=yang.jie@linux.intel.com \
--cc=zwisler@google.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