From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Vinod Koul <vinod.koul@intel.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH 1/5] compress: remove dead code _is_codec_supported()
Date: Fri, 20 Apr 2018 15:20:28 -0700 [thread overview]
Message-ID: <8ce7cfbf-4396-37ff-31df-db44cd7ca4ac@linux.intel.com> (raw)
In-Reply-To: <20180419080832.GH6014@localhost>
On 4/19/18 1:08 AM, Vinod Koul wrote:
> On Thu, Apr 19, 2018 at 12:19:28AM -0700, Pierre-Louis Bossart wrote:
>> On 4/18/18 11:36 PM, Vinod Koul wrote:
>>> static bool _is_codec_type_supported(int fd, struct snd_codec *codec)
>>> {
>>> struct snd_compr_caps caps;
>>> @@ -271,16 +228,6 @@ struct compress *compress_open(unsigned int card, unsigned int device,
>>> config->fragments = caps.max_fragments;
>>> }
>>> -#if 0
>>> - /* FIXME need to turn this On when DSP supports
>>> - * and treat in no support case
>>> - */
>>> - if (_is_codec_supported(compress, config, &caps) == false) {
>>> - oops(compress, errno, "codec not supported\n");
>>> - goto codec_fail;
>>> - }
>>> -#endif
>>
>> Why was this commented out in the first place?
>
> It depends on capabilities being reported properly which wasn't the case so we
> had to turn it off...
>
>> This seems like a valid check to me. If the application is asking for a
>> codec that isn't supported by hardware, should it be allowed to proceed?
>
> It has been dead for quite some time, I don't know if ppl are reporting
> properly. Turning it on might break which is something I would like to
> avoid
It was broken so it's better to remain broken to avoid breaking things?
TGIF.
prev parent reply other threads:[~2018-04-20 22:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-19 6:36 [PATCH 1/5] compress: remove dead code _is_codec_supported() Vinod Koul
2018-04-19 6:36 ` [PATCH 2/5] cplay: remove dead code codec_name_from_id() Vinod Koul
2018-04-19 6:36 ` [PATCH 3/5] cplay: remove dead code check_codec_format_supported() Vinod Koul
2018-04-19 6:36 ` [PATCH 4/5] cplay: fix incorrect print specifier warning Vinod Koul
2018-04-19 6:36 ` [PATCH 5/5] crecord: " Vinod Koul
2018-04-19 7:19 ` [PATCH 1/5] compress: remove dead code _is_codec_supported() Pierre-Louis Bossart
2018-04-19 8:08 ` Vinod Koul
2018-04-20 22:20 ` 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=8ce7cfbf-4396-37ff-31df-db44cd7ca4ac@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=vinod.koul@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