From: Cezary Rojewski <cezary.rojewski@intel.com>
To: broonie@kernel.org, tiwai@suse.com, pierre-louis.bossart@linux.intel.com
Cc: alsa-devel@alsa-project.org, lgirdwood@gmail.com
Subject: Re: [alsa-devel] [PATCH] ASoC: Intel: skl_hda_dsp_common: Fix global-out-of-bounds bug
Date: Wed, 22 Jan 2020 19:27:48 +0100 [thread overview]
Message-ID: <9246ee43-ffec-2b28-3a56-211f08797342@intel.com> (raw)
In-Reply-To: <20200122181254.22801-1-cezary.rojewski@intel.com>
For the last few days we have been playing with "vanilla" 5.5 kernel -
one without ton of /skylake patches - to find out how could hda-dsp be
enabled on skl/ kbl+ with the least amount of changes pulled from our
branch possible.
Turned out the addition of this single patch AND topology binary update
got the job done.
Now, how can we proceed with such solution. Can share the topology
binary/ .conf if needed, so anyone interested can check it out.
Regards,
Czarek
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2020-01-22 18:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-22 18:12 [alsa-devel] [PATCH] ASoC: Intel: skl_hda_dsp_common: Fix global-out-of-bounds bug Cezary Rojewski
2020-01-22 18:27 ` Cezary Rojewski [this message]
2020-01-22 19:52 ` Pierre-Louis Bossart
2020-01-23 15:10 ` Wasko, Michal
2020-01-23 18:22 ` Pierre-Louis Bossart
2020-01-27 13:05 ` Wasko, Michal
2020-01-27 15:30 ` Pierre-Louis Bossart
2020-01-28 19:40 ` Wasko, Michal
2020-01-22 19:55 ` Pierre-Louis Bossart
2020-01-22 21:30 ` Sridharan, Ranjani
2020-01-22 21:32 ` Mark Brown
2020-01-22 21:54 ` Pierre-Louis Bossart
2020-01-22 23:04 ` Sridharan, Ranjani
2020-01-23 8:31 ` Kai Vehmanen
2020-01-23 12:36 ` [alsa-devel] Applied "ASoC: Intel: skl_hda_dsp_common: Fix global-out-of-bounds bug" to the asoc tree Mark Brown
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=9246ee43-ffec-2b28-3a56-211f08797342@intel.com \
--to=cezary.rojewski@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=tiwai@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.