Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp5341499yba; Mon, 13 May 2019 09:14:06 -0700 (PDT) X-Google-Smtp-Source: APXvYqxkBrbZFDqdF6RnMSV21eK8cHspJmQX+U2fUPQaFqtX8T8FwP1AiK9n3kBBL8Kh6cBbnBGI X-Received: by 2002:a63:6bc3:: with SMTP id g186mr20184054pgc.21.1557764045837; Mon, 13 May 2019 09:14:05 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1557764045; cv=none; d=google.com; s=arc-20160816; b=hjqD0Xcm5/1uWr5Or/4olewp1kmJ2cCIAWAp0MQpBaVyhpTpnBpFaTkl3KS8PT/LmQ +ct4JJidZ9EZ+0RG5JYi9xTjyxy/Hs+ACclEVUduC4l1weuN4OD3wCCZP3/3JcS1peuK tTaP0w6EZ9dc+MPkCq/q5rryI07Hd2k7zCo1yAnrDL533VhedsCy5io85ojhR//u66oO yFrN+Zpmzk9BjdnOphgF2TIK5tEUuZma0pD6xqWxabnpdTz8wx5NIJRS4DyuNBZ1KRYg ik0JNAngSWY4Uk+T124ExP8sq6gNZ1pBy/5e41EtKpUtb3Nl0v3gRszRATDJVDqh7kFN rlZw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=YWa7P5s7QAVHiN7XmsTZcnCJ6BOVV+SUgpJWDR/clMw=; b=gCKm/aZsMDrgjMODQ7wlXZfljGVISfV83upuRpVcPvP3qOSGG5CxZM7/fQChL0eZne uvCM5+vXJwXzrEJ+qzhQ38meWPxh4cR9wct2sIU9box4AU/La/tA5uJL3OU/wyLD1mot jlcYkMsYA9H0Mt0yXyt8Zb7S7qEW+lztKU9XOytjr1k0qitjsdtgK2omgGfVzA1zY2r0 n6eZnsziH5y74XZZr6WI3U+xKZkg8k57gHw08a05mS2uOs4UiI7z1QMbZwDKRXxbCgtG 1v/Jj00PtcX3A2JWgdK9L0JEuVDw1vq+CroSSPZuX7h7jqhHnO2mvwCHivWPK9TaLtRe lJ4A== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f17si20191494pfq.237.2019.05.13.09.13.49; Mon, 13 May 2019 09:14:05 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730754AbfEMOlk (ORCPT + 99 others); Mon, 13 May 2019 10:41:40 -0400 Received: from mga14.intel.com ([192.55.52.115]:38791 "EHLO mga14.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730733AbfEMOlg (ORCPT ); Mon, 13 May 2019 10:41:36 -0400 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by fmsmga103.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 13 May 2019 07:41:35 -0700 X-ExtLoop1: 1 Received: from younghwa-mobl.amr.corp.intel.com (HELO [10.254.176.76]) ([10.254.176.76]) by fmsmga005.fm.intel.com with ESMTP; 13 May 2019 07:41:34 -0700 Subject: Re: [alsa-devel] [PATCH] ASoC: max98090: remove 24-bit format support To: Yu-Hsuan Hsu , linux-kernel@vger.kernel.org Cc: alsa-devel@alsa-project.org, Takashi Iwai , Jon Hunter , dgreid@chromium.org, cychiang@chromium.org References: <20190510102559.76137-1-yuhsuan@chromium.org> From: Pierre-Louis Bossart Message-ID: Date: Mon, 13 May 2019 08:31:33 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: <20190510102559.76137-1-yuhsuan@chromium.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 5/10/19 5:25 AM, Yu-Hsuan Hsu wrote: > Remove 24-bit format support because it doesn't work now. We can revert > this change after it really supports. > (https://patchwork.kernel.org/patch/10783561/) > > Signed-off-by: Yu-Hsuan Hsu As discussed in the previous thread, the data sheet explicitly mentions 24 bit support for the input in RJ mode. It'd be odd to remove support for 24 bits without clarifying in which modes it's not supported. Also you'd need to clarify which platform you tested on, there are known issues with Maxim devices when using e.g. a 19.2 MHz clock and trailing bits (25-bit slots with 24-bit data). > --- > sound/soc/codecs/max98090.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/sound/soc/codecs/max98090.c b/sound/soc/codecs/max98090.c > index 7619ea31ab50..b25b7efa9118 100644 > --- a/sound/soc/codecs/max98090.c > +++ b/sound/soc/codecs/max98090.c > @@ -2313,7 +2313,7 @@ int max98090_mic_detect(struct snd_soc_component *component, > EXPORT_SYMBOL_GPL(max98090_mic_detect); > > #define MAX98090_RATES SNDRV_PCM_RATE_8000_96000 > -#define MAX98090_FORMATS (SNDRV_PCM_FMTBIT_S16_LE | SNDRV_PCM_FMTBIT_S24_LE) > +#define MAX98090_FORMATS SNDRV_PCM_FMTBIT_S16_LE > > static const struct snd_soc_dai_ops max98090_dai_ops = { > .set_sysclk = max98090_dai_set_sysclk, >