Received: by 2002:a05:6a10:2785:0:0:0:0 with SMTP id ia5csp209997pxb; Fri, 8 Jan 2021 02:57:10 -0800 (PST) X-Google-Smtp-Source: ABdhPJwT9kpABZwYTkvwkhSKILv+bUac8enLkSpbqqXGO2MjhjLBgHd19hYJqyUQ2g+36WfdgdyA X-Received: by 2002:a17:906:d152:: with SMTP id br18mr2259840ejb.297.1610103430799; Fri, 08 Jan 2021 02:57:10 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1610103430; cv=none; d=google.com; s=arc-20160816; b=grlxSVfGCyaJmb3GFOLuuMqDwUOoNZuzW1vLvTYDc65dwKtRUMv8Tc621mO0ssZBIK Ic8v5t/68+jfk9vxnIZdx5EwA7j4j1zbRYFjqNGAaRJmQlZric5N2fxFy4k3IGirYztd Zij8wcWHVdqUTlwp5Vm0ncgGQPLSKVJ2Wh7wtP6NlE9yUTFfYa8dCixeQGoZ8bpFGmlS fI7xBLUUkGvfuzhibdm/+4HVErKie9gYHk6bERTRyeYc5HCmgV1XtPDfg5USJJvAo8zD 2j7q1BsBLdc7Bk1+F4bj69j9Sl68iQ4MGDqaEaGozaz371hm0xAYTB20vb8W9HnYNLeU 0Qsw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:dkim-signature:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=44OEuLq8rq8qx902zPtywsnxfjLSd17HpWJCsALsuoE=; b=NhWvZ+aCx7SCQbVdeJGsUi3iuB3XTQdbUvmNq86s9MQEQ4brVpHabX5X0SflCJYstc HsoB5TtXF8T8vKNAbkF94vpE6vs+7oDhiMF3qsVPg+C7toMndSBIoY6kzAjZ93Nll/Yd sB+5wxcxWFx+fCRoEkAHuULtzmjoNBXRgUKqPkMtlQpcz5ZqXhTkb75hmMtWNsoUyFW7 zErag6Cc0li751fhH/Y38tV/FXoJB6LOKmNc8Hy8a9MuMkE7nc+xit56PgZtqKO6EAKP /XLCqg16e3mRcVuTwcaZG3x+wSE1DDlXoE1lwxC+cUAyogk8KCBUlpWrf5PtQuktB6EQ KB5g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@nvidia.com header.s=n1 header.b=PrZgtF4c; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=nvidia.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id gb19si3363487ejc.496.2021.01.08.02.56.47; Fri, 08 Jan 2021 02:57:10 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@nvidia.com header.s=n1 header.b=PrZgtF4c; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=nvidia.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728049AbhAHKzj (ORCPT + 99 others); Fri, 8 Jan 2021 05:55:39 -0500 Received: from hqnvemgate24.nvidia.com ([216.228.121.143]:8111 "EHLO hqnvemgate24.nvidia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727957AbhAHKzi (ORCPT ); Fri, 8 Jan 2021 05:55:38 -0500 Received: from hqmail.nvidia.com (Not Verified[216.228.121.13]) by hqnvemgate24.nvidia.com (using TLS: TLSv1.2, AES256-SHA) id ; Fri, 08 Jan 2021 02:54:58 -0800 Received: from [10.26.72.150] (172.20.145.6) by HQMAIL107.nvidia.com (172.20.187.13) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 8 Jan 2021 10:54:54 +0000 Subject: Re: [PATCH 2/2] ALSA: hda/tegra: fix tegra-hda on tegra30 soc To: Sameer Pujar , Peter Geis CC: Michael Turquette , Stephen Boyd , Peter De Schrijver , "Prashant Gaikwad" , Thierry Reding , Jaroslav Kysela , Takashi Iwai , Mohan Kumar , , , , , Ion Agorria References: <20201225012025.507803-1-pgwipeout@gmail.com> <20201225012025.507803-3-pgwipeout@gmail.com> <0c3665b2-bac6-546a-bdd4-0ab7a90adf7c@nvidia.com> From: Jon Hunter Message-ID: Date: Fri, 8 Jan 2021 10:54:51 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: quoted-printable X-Originating-IP: [172.20.145.6] X-ClientProxiedBy: HQMAIL105.nvidia.com (172.20.187.12) To HQMAIL107.nvidia.com (172.20.187.13) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nvidia.com; s=n1; t=1610103298; bh=44OEuLq8rq8qx902zPtywsnxfjLSd17HpWJCsALsuoE=; h=Subject:To:CC:References:From:Message-ID:Date:User-Agent: MIME-Version:In-Reply-To:Content-Type:Content-Language: Content-Transfer-Encoding:X-Originating-IP:X-ClientProxiedBy; b=PrZgtF4czMmGEaFfElcaTYlFzdTHReGa9hnIzvZ3eZAR7j0wskwsHKRTYbeZMNOdU 6wstL/b2qpFuk5ocXBxVPILLlkDz/9zTyV1FjEQytFxFVe5kUcu8vp4ulQzkZuRpUx 8liMNrli47j4i75tU0A0VsimHVv3ErIRot9hGGr0kw4JKKDRGwmPcU4jVSBLnwCFph CXV3Ntda7tKqbvt0yV0cGlY7CceuxX3Kx8rr+dfmCkS8Euek4Y7t4fglOlZgh9Ys1u 8rszZlujNE7Q6N17eNMKQo9omNXjC7ASaoR7mG+TefJHD+cOVqCxNwlhSLrhoq2MLa 9Ld4KpiW5yC3Q== Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 08/01/2021 08:00, Sameer Pujar wrote: ... >>>> Signed-off-by: Peter Geis >>>> Tested-by: Ion Agorria >>>> --- >>>> =C2=A0=C2=A0 sound/pci/hda/hda_tegra.c | 3 +-- >>>> =C2=A0=C2=A0 1 file changed, 1 insertion(+), 2 deletions(-) >>>> >>>> diff --git a/sound/pci/hda/hda_tegra.c b/sound/pci/hda/hda_tegra.c >>>> index 70164d1428d4..f8d61e677a09 100644 >>>> --- a/sound/pci/hda/hda_tegra.c >>>> +++ b/sound/pci/hda/hda_tegra.c >>>> @@ -388,8 +388,7 @@ static int hda_tegra_first_init(struct azx >>>> *chip, struct platform_device *pdev) >>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 * in powe= rs of 2, next available ratio is 16 which can be >>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 * used as= a limiting factor here. >>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 */ >>>> -=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 if (of_device_is_compatible(np, = "nvidia,tegra194-hda")) >>>> -=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0 chip->bus.core.sdo_limit =3D 16; >>>> +=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 chip->bus.core.sdo_limit =3D 16; >>> Future Tegra chips address this problem and hence cannot be enforced by >>> default. May be we can have like below: >>> >>> if (of_device_is_compatible(np, "nvidia,tegra30-hda")) >>> chip->bus.core.sdo_limit =3D 16; >>> >> It will need to be a bit more complicated than that, since the >> tegra186 and tegra210 device trees have "nvidia,tegra30-hda" as a >> fallback. >> Looking at the generation map, tegra30-hda can be the fallback for the >> broken implementation and tegra210-hda can be the fallback for the >> working implementation. >> Does that work for you? >=20 > As per above explanation, it is fine to apply the workaround for > Tegra210/186 as well. So it simplifies things for all existing chips. FYI ... we now have minimal support for Tegra234 in upstream that should not require this. Given that the Tegra234 device-tree does not include support for HDA yet, I think it is fine to apply this as-is. However, once we do add support for Tegra234 HDA, then we should ensure that this is not applied. So that said ... Reviewed-by: Jon Hunter Cheers Jon --=20 nvpublic