From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.9 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id A644DC48BE5 for ; Tue, 15 Jun 2021 15:48:01 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 9165B615A0 for ; Tue, 15 Jun 2021 15:48:01 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231694AbhFOPuF (ORCPT ); Tue, 15 Jun 2021 11:50:05 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58090 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231366AbhFOPuE (ORCPT ); Tue, 15 Jun 2021 11:50:04 -0400 Received: from mail-wm1-x32b.google.com (mail-wm1-x32b.google.com [IPv6:2a00:1450:4864:20::32b]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id EF255C06175F for ; Tue, 15 Jun 2021 08:47:59 -0700 (PDT) Received: by mail-wm1-x32b.google.com with SMTP id t11-20020a1cc30b0000b02901cec841b6a0so1136446wmf.0 for ; Tue, 15 Jun 2021 08:47:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=GBinx4Fgo45gvNb6Q+VwiPy/5uxor4+wH/XjaU7vEwU=; b=fKBLKEpGGji1pJ8Chsxfvqljab6qo00YqyYLcs9KAIRVzcPyZyRS/9kYae9BQhnPkS ZnpNaP5a2XEdbNdJeZViHbkyiIYIIILUexJwCWeSWF8fDuQSgpoe7MuUHFy0z4UazS32 sDdFgLVdGm9mG/b/9FD+ArxbRhqK74pHM2kr8= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=GBinx4Fgo45gvNb6Q+VwiPy/5uxor4+wH/XjaU7vEwU=; b=My8WjSa9QSih/FSZb/P0QSVFw4ICgSEYueAowmUtygyMtgRtZ57ixwFb6m4+Sek/SS XbnTUAmr19nRosQ3GJApViEoKASYzzUC8/n/Zt31w0ARcPBLKNPyvX5V+4XvgJSgQklL 0Mxjmtl/obBupw7O7nXRbVleHinbvr2I4Tr5QAitMv0uNVE8dfIc24I3HE77vyJrI5f7 jJXBhK8IlCCVQhW2BsO/JsGeKVxjNXEniit5zY7abN0iWjAdB1ujYryQ//FsdimJQoVh 7DFm6cnim19xeuEwz9G2dSn5mrZqvW1n2B+akEFDDgAc833xWD8lsAU0ZFuIoQ+zh2tA KQSQ== X-Gm-Message-State: AOAM533dmEe7L9LDorYTlbjiRG7q8Ns7jj1h2icalm/OgZfOduP2j5zn 0rrsmfBZi40ILivVimJW7Wg1mkXMvJtsZMXNDAjlJw== X-Google-Smtp-Source: ABdhPJwUoEVW6kMYZC606PnYCEczrljMALiN96zNLd0kS0EL2UX5TDso3su7xUx2lhZdDpzedPnxBwH3c8Nmho87MO0= X-Received: by 2002:a7b:c5d2:: with SMTP id n18mr6083880wmk.97.1623772078396; Tue, 15 Jun 2021 08:47:58 -0700 (PDT) MIME-Version: 1.0 References: <20210526154704.114957-1-judyhsiao@chromium.org> In-Reply-To: From: Cheng-yi Chiang Date: Tue, 15 Jun 2021 23:47:30 +0800 Message-ID: Subject: Re: [PATCH] ASoC: max98357a: set channels_max to 4 To: Tzung-Bi Shih Cc: Judy Hsiao , Mark Brown , Taniya Das , Rohit kumar , Banajit Goswami , Patrick Lai , Andy Gross , Bjorn Andersson , Liam Girdwood , Rob Herring , Jaroslav Kysela , Takashi Iwai , Srini Kandagatla , Stephan Gerhold , Douglas Anderson , Dylan Reid , Tzung-Bi Shih , Stephen Boyd , "moderated list:ARM/Mediatek SoC support" , linux-arm-msm , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , ALSA development Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-arm-msm@vger.kernel.org Hi Tzung-Bi, On a platform, the four max98357a amps will be controlled by only one codec device, as GPIO for SD_MODE is shared by all amps and is the only thing to be controlled. In this sense, I think we can treat max98357a DAI as if it supports four channels. I understand that this solution is not scalable, because one can control as many amps as they want. Theoretically, the number of supported channels by this codec device is unlimited. I found that rt1015.c has similar usage. Do you have a better suggestion to support this kind of use case ? Thanks! On Tue, Jun 1, 2021 at 2:20 PM Tzung-Bi Shih wrote: > > On Wed, May 26, 2021 at 11:47 PM Judy Hsiao wrote: > > Sets channels_max to 4 to support QUAD channel. > > Could you point out probably the up-to-date MAX98357A datasheet for > 4-channel support? > > On a related note, from the public datasheet I could find[1], "Table > 5" only shows 2 channel's configuration. > > [1]: https://pdf1.alldatasheet.com/datasheet-pdf/view/623796/MAXIM/MAX98357A.html From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id ABB5FC49361 for ; Tue, 15 Jun 2021 15:49:00 +0000 (UTC) Received: from alsa0.perex.cz (alsa0.perex.cz [77.48.224.243]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id B07876162B for ; Tue, 15 Jun 2021 15:48:59 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org B07876162B Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=chromium.org Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=alsa-devel-bounces@alsa-project.org Received: from alsa1.perex.cz (alsa1.perex.cz [207.180.221.201]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by alsa0.perex.cz (Postfix) with ESMTPS id B81511676; Tue, 15 Jun 2021 17:48:07 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa0.perex.cz B81511676 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alsa-project.org; s=default; t=1623772137; bh=GBinx4Fgo45gvNb6Q+VwiPy/5uxor4+wH/XjaU7vEwU=; h=References:In-Reply-To:From:Date:Subject:To:Cc:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From; b=Il/TQ295a18UErblunAMf+9cbhmx0D00J53o0FPHjdRVaaUb2rkTB0CNAL/LKCuun dkjPKpq4jQvtPLJ2DPCJuGY/zz1jDqdfSUiGcTUKRXMTu43wjAnsNCzQ8enI2+M/gZ wmVpuY4LCgrq6QIOlKaSBRaGwpnzatImch3gCi8I= Received: from alsa1.perex.cz (localhost.localdomain [127.0.0.1]) by alsa1.perex.cz (Postfix) with ESMTP id 54C2DF8016D; Tue, 15 Jun 2021 17:48:07 +0200 (CEST) Received: by alsa1.perex.cz (Postfix, from userid 50401) id DC0A4F80113; Tue, 15 Jun 2021 17:48:05 +0200 (CEST) Received: from mail-wm1-x32b.google.com (mail-wm1-x32b.google.com [IPv6:2a00:1450:4864:20::32b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by alsa1.perex.cz (Postfix) with ESMTPS id 911E4F80113 for ; Tue, 15 Jun 2021 17:47:59 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa1.perex.cz 911E4F80113 Authentication-Results: alsa1.perex.cz; dkim=pass (1024-bit key) header.d=chromium.org header.i=@chromium.org header.b="fKBLKEpG" Received: by mail-wm1-x32b.google.com with SMTP id l9so14424801wms.1 for ; Tue, 15 Jun 2021 08:47:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=GBinx4Fgo45gvNb6Q+VwiPy/5uxor4+wH/XjaU7vEwU=; b=fKBLKEpGGji1pJ8Chsxfvqljab6qo00YqyYLcs9KAIRVzcPyZyRS/9kYae9BQhnPkS ZnpNaP5a2XEdbNdJeZViHbkyiIYIIILUexJwCWeSWF8fDuQSgpoe7MuUHFy0z4UazS32 sDdFgLVdGm9mG/b/9FD+ArxbRhqK74pHM2kr8= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=GBinx4Fgo45gvNb6Q+VwiPy/5uxor4+wH/XjaU7vEwU=; b=dP8JDwVAruf8XU0G+o3lxno6VhnaShPxrwXJkg75K5IzMhEuQqtCd9zPe1LqTALi2N Bq1TD6SCJbWWmkpV3z9L4xAk0AACcHg1Utas70p1m1OhsjsSDQ+PALEWCFE5Dj3aVLo0 Zrxnbkn6qClEhsagi/hJ0ETR0KVjDsjGL2mFPxMxEBu19c0z4lNbjpn7a4deLepKZQWY bqSBjp6N5Y0C8ZbPTPsCwwYLLTye/TngaXTVGAXkvKeFzh+lOPnkyBfLWjzwUL01egK/ piHvU4AWtsuok2hjGSi8FuSdQeRIBKb1DRvQBxTVVErnB3AWmicPsxXHCjyIkldLd8pb mL9w== X-Gm-Message-State: AOAM530wpIoYkg8Ha4OAAm7f+3YWXLKdnlv2cZyVRtx1zRpUiuTCrDOl R/EMPqrO9NB546TsOBVrpWUQiRjVAhvCweTz5Btisw== X-Google-Smtp-Source: ABdhPJwUoEVW6kMYZC606PnYCEczrljMALiN96zNLd0kS0EL2UX5TDso3su7xUx2lhZdDpzedPnxBwH3c8Nmho87MO0= X-Received: by 2002:a7b:c5d2:: with SMTP id n18mr6083880wmk.97.1623772078396; Tue, 15 Jun 2021 08:47:58 -0700 (PDT) MIME-Version: 1.0 References: <20210526154704.114957-1-judyhsiao@chromium.org> In-Reply-To: From: Cheng-yi Chiang Date: Tue, 15 Jun 2021 23:47:30 +0800 Message-ID: Subject: Re: [PATCH] ASoC: max98357a: set channels_max to 4 To: Tzung-Bi Shih Content-Type: text/plain; charset="UTF-8" Cc: Taniya Das , ALSA development , Banajit Goswami , Takashi Iwai , Rohit kumar , Patrick Lai , Andy Gross , Dylan Reid , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , Tzung-Bi Shih , Stephan Gerhold , linux-arm-msm , Stephen Boyd , Rob Herring , Bjorn Andersson , "moderated list:ARM/Mediatek SoC support" , Douglas Anderson , Liam Girdwood , Mark Brown , Judy Hsiao X-BeenThere: alsa-devel@alsa-project.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "Alsa-devel mailing list for ALSA developers - http://www.alsa-project.org" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: alsa-devel-bounces@alsa-project.org Sender: "Alsa-devel" Hi Tzung-Bi, On a platform, the four max98357a amps will be controlled by only one codec device, as GPIO for SD_MODE is shared by all amps and is the only thing to be controlled. In this sense, I think we can treat max98357a DAI as if it supports four channels. I understand that this solution is not scalable, because one can control as many amps as they want. Theoretically, the number of supported channels by this codec device is unlimited. I found that rt1015.c has similar usage. Do you have a better suggestion to support this kind of use case ? Thanks! On Tue, Jun 1, 2021 at 2:20 PM Tzung-Bi Shih wrote: > > On Wed, May 26, 2021 at 11:47 PM Judy Hsiao wrote: > > Sets channels_max to 4 to support QUAD channel. > > Could you point out probably the up-to-date MAX98357A datasheet for > 4-channel support? > > On a related note, from the public datasheet I could find[1], "Table > 5" only shows 2 channel's configuration. > > [1]: https://pdf1.alldatasheet.com/datasheet-pdf/view/623796/MAXIM/MAX98357A.html From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.9 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id D7D7CC48BDF for ; Tue, 15 Jun 2021 19:58:00 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 9E5AF613B3 for ; Tue, 15 Jun 2021 19:58:00 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 9E5AF613B3 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=chromium.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:Cc:To:Subject:Message-ID:Date:From: In-Reply-To:References:MIME-Version:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=KMMl1iHdgsDHlYlTDf/fsd07XWwgeshv01WdadNpCe0=; b=l9SwyfDqJ2Dq5G RqR7ZNYiPQQxBw/aq+1I5f6DQmdTg9EI6SaT+9GtjD18tKaxVG5n8Ugd7IHHSzLhsVsNCRrpO1DR4 UUUj8QhSGMnBfUhgYznoQQ15tMr1hQBP2jLxOOXBk24Rt+C6D9KjI4CcgPtMKxmZrkTToWR9Nl08a vynMqn1JE6O5jE3SeUe4TGWp2vbDLbO+nzMe6YZpq4jadVdGqZlfFTQgNLwoNjSOBfSrD+c/j3PA/ K3atklWDbRGXWLvqG/IWlO/rZJpqzCTJ/mGXuXDBKAJcxPXNBoaXW56UVNQRWIsWXH7ZL3sQmNSfV R42ZG+Q6k1IvdAyGGVMg==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1ltF9r-002byv-Jn; Tue, 15 Jun 2021 19:55:36 +0000 Received: from mail-wm1-x336.google.com ([2a00:1450:4864:20::336]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1ltBIL-0015Xa-GE for linux-arm-kernel@lists.infradead.org; Tue, 15 Jun 2021 15:48:07 +0000 Received: by mail-wm1-x336.google.com with SMTP id u5-20020a7bc0450000b02901480e40338bso1790786wmc.1 for ; Tue, 15 Jun 2021 08:47:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=GBinx4Fgo45gvNb6Q+VwiPy/5uxor4+wH/XjaU7vEwU=; b=fKBLKEpGGji1pJ8Chsxfvqljab6qo00YqyYLcs9KAIRVzcPyZyRS/9kYae9BQhnPkS ZnpNaP5a2XEdbNdJeZViHbkyiIYIIILUexJwCWeSWF8fDuQSgpoe7MuUHFy0z4UazS32 sDdFgLVdGm9mG/b/9FD+ArxbRhqK74pHM2kr8= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=GBinx4Fgo45gvNb6Q+VwiPy/5uxor4+wH/XjaU7vEwU=; b=P1Cm7/iVNY28Ogag8QIdHtw4ojOeFQeKCsZNvhPUAxXE+1yYMM5N0AdRSqnbCYJvAd fdMNNqyYkr8cgDOM/K2k4k3aW1sLSOwbbjO6ACZGipD9HcGsYOsurN6fWkJCUQsvJ+Bx PnNxsbZVkmmFVGOgcX7rvTULdgVdSPTr0rIbu4RHBNdj18s+OtGDCI9g6G9K87dx6+m4 3sm0dEelw43DKOuqF8M5lxZ4usAeB2oKHYpXtdJsxTJ0OAuPC2PI8lFwbHrXCUwWp80L pbKp+MRF4oCfHeZJ0IvD6GlrrlG0BpBOHDqL05UPGdoIMFR4AdoXbeaaf1w9lGONMaPg wsiQ== X-Gm-Message-State: AOAM532k1v9Kp0LaLKFulbxN6yHnLWq9XxJZdoCpiUoW/ZDMknVN49X+ SewpEMAatlchjbiXX00O5KgychA9FY/Ja/MLldI/NQ== X-Google-Smtp-Source: ABdhPJwUoEVW6kMYZC606PnYCEczrljMALiN96zNLd0kS0EL2UX5TDso3su7xUx2lhZdDpzedPnxBwH3c8Nmho87MO0= X-Received: by 2002:a7b:c5d2:: with SMTP id n18mr6083880wmk.97.1623772078396; Tue, 15 Jun 2021 08:47:58 -0700 (PDT) MIME-Version: 1.0 References: <20210526154704.114957-1-judyhsiao@chromium.org> In-Reply-To: From: Cheng-yi Chiang Date: Tue, 15 Jun 2021 23:47:30 +0800 Message-ID: Subject: Re: [PATCH] ASoC: max98357a: set channels_max to 4 To: Tzung-Bi Shih Cc: Judy Hsiao , Mark Brown , Taniya Das , Rohit kumar , Banajit Goswami , Patrick Lai , Andy Gross , Bjorn Andersson , Liam Girdwood , Rob Herring , Jaroslav Kysela , Takashi Iwai , Srini Kandagatla , Stephan Gerhold , Douglas Anderson , Dylan Reid , Tzung-Bi Shih , Stephen Boyd , "moderated list:ARM/Mediatek SoC support" , linux-arm-msm , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , ALSA development X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20210615_084805_597605_BF21ACE5 X-CRM114-Status: GOOD ( 13.90 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org Hi Tzung-Bi, On a platform, the four max98357a amps will be controlled by only one codec device, as GPIO for SD_MODE is shared by all amps and is the only thing to be controlled. In this sense, I think we can treat max98357a DAI as if it supports four channels. I understand that this solution is not scalable, because one can control as many amps as they want. Theoretically, the number of supported channels by this codec device is unlimited. I found that rt1015.c has similar usage. Do you have a better suggestion to support this kind of use case ? Thanks! On Tue, Jun 1, 2021 at 2:20 PM Tzung-Bi Shih wrote: > > On Wed, May 26, 2021 at 11:47 PM Judy Hsiao wrote: > > Sets channels_max to 4 to support QUAD channel. > > Could you point out probably the up-to-date MAX98357A datasheet for > 4-channel support? > > On a related note, from the public datasheet I could find[1], "Table > 5" only shows 2 channel's configuration. > > [1]: https://pdf1.alldatasheet.com/datasheet-pdf/view/623796/MAXIM/MAX98357A.html _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel