[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <85499f52ebd29581bf58b9cafbae6864.squirrel@www.codeaurora.org>
Date: Thu, 13 Nov 2014 03:02:04 -0000
From: gsantosh@...eaurora.org
To: alsa-devel-bounces@...a-project.org
Cc: "Mark Rutland" <mark.rutland@....com>,
"Rob Herring" <robh@...nel.org>,
"ALSA Development Mailing List" <alsa-devel@...a-project.org>,
"Kuninori Morimoto" <kuninori.morimoto.gx@...esas.com>,
"Stephen Warren" <swarren@...dotorg.org>,
"Linux-sh list" <linux-sh@...r.kernel.org>,
"Magnus" <magnus.damm@...il.com>, linux-kernel@...r.kernel.org,
grant.likely@...aro.org, devicetree@...r.kernel.org,
"Mark Brown" <broonie@...nel.org>,
"Geert Uytterhoeven" <geert@...ux-m68k.org>,
"Olof Johansson" <olof@...om.net>,
"Kuninori Morimoto" <kuninori.morimoto.gx@...il.com>
Subject: Question on Compressed offload session
Hi All,
The Question is for the compressed offload session.
For a generic codec driver during the startup function it will set some of
the hw_constraints rule similarly like this.
snd_pcm_hw_constraint_list(substream->runtime, 0,
SNDRV_PCM_HW_PARAM_RATE,
&constraints_12_24);
pcm_lib.c will try to add the rule to the runtime structure by accessing
the pointers which will be initialized during opening of the session,
as The Constraints added by the codec driver will be updated in the
struct snd_pcm_hw_constraints of runtime structure which will be part of
substream handle.
But for the compressed offload I do not see the initialization done for HW
constraints, as done in pcm session
2092int snd_pcm_open_substream(struct snd_pcm *pcm, int stream,
2093 struct file *file,
2094 struct snd_pcm_substream **rsubstream)
most of the existing drivers which has the hw_constraint_list code will
not be applicable for compress offload session, how to solve this?
Regards,
Santosh M G.
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora
Forum,a Linux Foundation Collaborative Project
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists