mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Baluta <daniel.baluta@oss.nxp.com>
To: pierre-louis.bossart@linux.intel.com, lgirdwood@gmail.com,
	broonie@kernel.org
Cc: daniel.baluta@nxp.com, kai.vehmanen@linux.intel.com,
	ranjani.sridharan@linux.intel.com,
	sound-open-firmware@alsa-project.org,
	alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
	cezary.rojewski@intel.com, paul.olaru@nxp.com
Subject: [PATCH v2 0/2] SOF: Add compress support implementation
Date: Tue, 18 Jan 2022 23:27:30 +0200	[thread overview]
Message-ID: <20220118212732.281657-1-daniel.baluta@oss.nxp.com> (raw)

From: Daniel Baluta <daniel.baluta@nxp.com>

This patch series adds compress operations support. This is tested with
SOF (codec_adapter component enabled) and i.MX8/8X/8M boards.

Changes since v1:
(https://lore.kernel.org/lkml/20220113161341.371345-1-daniel.baluta@oss.nxp.com/T/)

- Addressed review from Cezary and Pierre
- fixed layout of declaration blocks to be more consistent
- avoid using rtd and runtime simultaneously inside a function (always
  used rtd and crtd)
- check return code for create_page_table
- completely remove sof_compr_stream and use snd_compr_tstmap instead to
  keep compress stream related info.·
- add get_caps and get_codec_caps implementations (in patch 2) 

Daniel Baluta (1):
  ASoC: SOF: compr: Add compress ops implementation

Paul Olaru (1):
  ASoC: SOF: compress: Implement get_caps and get_codec_caps

 sound/soc/sof/compress.c | 347 ++++++++++++++++++++++++++++++++++++++-
 1 file changed, 345 insertions(+), 2 deletions(-)

-- 
2.27.0


             reply	other threads:[~2022-01-18 21:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-18 21:27 Daniel Baluta [this message]
2022-01-18 21:27 ` [PATCH v2 1/2] ASoC: SOF: compr: Add compress ops implementation Daniel Baluta
2022-01-18 21:27 ` [PATCH v2 2/2] ASoC: SOF: compress: Implement get_caps and get_codec_caps Daniel Baluta
2022-01-19  1:00   ` Pierre-Louis Bossart
2022-01-19 15:43     ` Daniel Baluta
2022-01-19 16:56       ` Pierre-Louis Bossart

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=20220118212732.281657-1-daniel.baluta@oss.nxp.com \
    --to=daniel.baluta@oss.nxp.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=cezary.rojewski@intel.com \
    --cc=daniel.baluta@nxp.com \
    --cc=kai.vehmanen@linux.intel.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paul.olaru@nxp.com \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=ranjani.sridharan@linux.intel.com \
    --cc=sound-open-firmware@alsa-project.org \
    /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

all inboxes | Powered by JetHome®