Received: by 2002:a05:6a10:2785:0:0:0:0 with SMTP id ia5csp2993320pxb; Tue, 12 Jan 2021 03:50:36 -0800 (PST) X-Google-Smtp-Source: ABdhPJwOXhh0Fx13FzpPsMl/X7NZB08iZPyzAhuajzilqDsFlfDDpau6bAY74Iwv8GikWrE2SxeV X-Received: by 2002:a50:9dc9:: with SMTP id l9mr3080807edk.377.1610452236064; Tue, 12 Jan 2021 03:50:36 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1610452236; cv=none; d=google.com; s=arc-20160816; b=0pIR7YE06qYrTMSkYECG8M1Sg1Vvl2KdZnNPoUwQXMHfMtaI9VeEY/8YkSRakPEOLe SdzItqbIE0RJjsqFoxwWOUNYTpxLA0Ko+AzugKXfxLVfePCEiyqh7TcQMZpfQ+so3fOQ NUht9atNs2NCWnHLcWXa08XHhGAOqUflYgjEc7503RJi3OKWdcniXGZ8rb0Skw50iCrZ +9JQgkyYQUeiP8Q8gNdV1XtdkjfcN5y1nOEDbC+ZUqzs2GeVCFUXCRdwLoxjfgr/vs0D eWMPs6rzabxL9xLFDB4YPrxHppfV4MhQeCS6WIdOLnaYCqf4KYGyA7Oc59pNJkFUF7XB MpkQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:user-agent:references:in-reply-to :subject:cc:to:from:message-id:date; bh=iCihDiqqVIKSXI8WTYjQ0LUL7jkZTWQC8Bpr3g0/AMU=; b=j4fQNrPHcArhGrPYL3IufVDYO0w/M3U1AduoLpnC9uteOXRIqWfu67HaW6shrT4F4J OdpCXYroJjt7bGGeVw30VpdAJBgUuphgx4IG531SHvGSkqj4KQlQ6oUgdJsACyOUSW09 NJ3bXvmjRQaffyyhIsBFsR3W9wxAZDktLsfb+12YDfDUqRod9AaX51pPtuPR9qXs/ufg UdsSkyIEFOWCcqEX9/yE7fxS69ohZ47aD7/LH0F8Xqo6rDiKz2WuS9a1HbANFeh5n2Zi Zd9QsL+Ckf3WrQ6Li0jICGd/97zyWnAZZaFyQonhi1cET+oyoBibhUvbNb8js7Q9l8w5 gN8w== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id r16si957452ejz.602.2021.01.12.03.50.12; Tue, 12 Jan 2021 03:50:36 -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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2404821AbhALIXV (ORCPT + 99 others); Tue, 12 Jan 2021 03:23:21 -0500 Received: from mx2.suse.de ([195.135.220.15]:34248 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728262AbhALIXU (ORCPT ); Tue, 12 Jan 2021 03:23:20 -0500 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id 91D36AC8F; Tue, 12 Jan 2021 08:22:38 +0000 (UTC) Date: Tue, 12 Jan 2021 09:22:38 +0100 Message-ID: From: Takashi Iwai To: Peter Geis Cc: Michael Turquette , Stephen Boyd , Peter De Schrijver , Prashant Gaikwad , Thierry Reding , Jonathan Hunter , Jaroslav Kysela , Takashi Iwai , Sameer Pujar , Mohan Kumar , linux-clk@vger.kernel.org, linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org Subject: Re: [PATCH v2 0/2] fix tegra-hda on tegra30 devices In-Reply-To: <20210108135913.2421585-1-pgwipeout@gmail.com> References: <20210108135913.2421585-1-pgwipeout@gmail.com> User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.8 Emacs/25.3 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 08 Jan 2021 14:59:11 +0100, Peter Geis wrote: > > The following patches fix tegra-hda on legacy tegra devices. > Two issues were discovered preventing tegra-hda from functioning: > -The hda clocks on tegra30 were assigned to clk_m and running at too low > of a rate to function. > -The tegra-hda encounters an input/output error when opening a stream. > > Since the only mainline device that used tegra-hda until recently was the > t124, it is unknown exactly when this was broken. Fortunately a recent > patch was submitted that fixed the issue only on t194 devices. We can > apply it to the tegra30-hda device to resolve the issue across the board. > Note that downstream devices used the spdif device instead of hda for hdmi > audio. The spdif device lacks a driver on mainline. > > -Checkpatch seems to have issues finding [1], but git show has no issue. > [1] commit 60019d8c650d ("ALSA: hda/tegra: workaround playback failure on > Tegra194") > > Changelog: > > v2: > -Added ack and reviewed-by from Jon > -Updated fix to apply to tegra30-hda vice universally (Thanks Jon) > -Updated commit to include comments from hardware team (Thanks Sameer) > -Cleaned up commit messages > > Peter Geis (2): > clk: tegra30: Add hda clock default rates to clock driver > ALSA: hda/tegra: fix tegra-hda on tegra30 soc Shall I apply both patches via sound git tree? Or, if you want to take through clk tree, let me know. In that case, feel free to take my ack: Acked-by: Takashi Iwai thanks, Takashi