From patchwork Fri Dec 25 01:20:24 2020 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Peter Geis X-Patchwork-Id: 1420568 Return-Path: X-Original-To: incoming@patchwork.ozlabs.org Delivered-To: patchwork-incoming@bilbo.ozlabs.org Authentication-Results: ozlabs.org; spf=pass (sender SPF authorized) smtp.mailfrom=vger.kernel.org (client-ip=23.128.96.18; helo=vger.kernel.org; envelope-from=linux-tegra-owner@vger.kernel.org; receiver=) Authentication-Results: ozlabs.org; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: ozlabs.org; dkim=pass (2048-bit key; unprotected) header.d=gmail.com header.i=@gmail.com header.a=rsa-sha256 header.s=20161025 header.b=hAn5MJD5; dkim-atps=neutral Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by ozlabs.org (Postfix) with ESMTP id 4D28LD1zbnz9sTL for ; Fri, 25 Dec 2020 12:21:56 +1100 (AEDT) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729021AbgLYBVi (ORCPT ); Thu, 24 Dec 2020 20:21:38 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:44282 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729020AbgLYBVi (ORCPT ); Thu, 24 Dec 2020 20:21:38 -0500 Received: from mail-qk1-x72d.google.com (mail-qk1-x72d.google.com [IPv6:2607:f8b0:4864:20::72d]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4F381C061573; Thu, 24 Dec 2020 17:20:58 -0800 (PST) Received: by mail-qk1-x72d.google.com with SMTP id n142so3284306qkn.2; Thu, 24 Dec 2020 17:20:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=eR/51XLp7HQCd5RWnkeAFXvnTVVeE+YelrG/OsehfgY=; b=hAn5MJD5rRItKlT/7Zl24e2BKZi0Ls8BZo0yfG0VHqNGbxZIImG5bj/Hw62Gu+mG/u QO7Mr9HJasfbcRh505O+zP9Cp22ZCzWUHrxmqVE9qhvWlELEdxNImMJDFxUDvwziQxI6 NMUBe1UMHiSbY24xZSLCEC0gjY+JPmEyJJkyAQdan47NLcDaq2OjTXlOcu56PrZEf/Qj K3VfpTdZSMv/g56hpCEy1zR7HYWykU6U6oBzC6tznzZ8ClVF/vQitTc9y6DEuUMNcsQ3 ql+bigyXHfDYne4ATahAJRh8V7qWXqutn0+s3hatv64QVfUd+i0A0z5k/VgcvxeTHRD+ YW5w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=eR/51XLp7HQCd5RWnkeAFXvnTVVeE+YelrG/OsehfgY=; b=sFSBicz8fxZ/rKW4Aec1+eMiDc/7B15kRObnjYyYIbRUbPvKsrq3Tc6zEkDlPZ62X4 us720YvtPQcggOybTj4mIWhDxa9ExeqW99Xp1htcpTge/2UMfKMu8hlf5FTRt9Za0RsV V5oqE5HpFy1YbMeXsexyaMQTHXB3hfuN1uO8SCPeDzQnieoAYHqqtVVIiEGRfrtGOwHP QLXkVJdz0NkHiik8rK/4tVi//fsM8z6CtUwb/Hdcr9t2fmTkEEI7+XoUTpKLkHY2pDKG G9Z1Md3Yw1RbkGNXNjEYD2+HYeJ7JAIN2COQQKtVCAH4CVEyXs1q/JECAOVOJtMfYHq/ tHOw== X-Gm-Message-State: AOAM531sV/P6jr9k84mzNUhpRzCM2yO0guwxrN3FCF/d5cAwr7Za6uZD opEPEQRDuRwV5WqtNbTeZTg= X-Google-Smtp-Source: ABdhPJyrNjeysbrlaGCYU+QBL1gUJ/O/dP/8CtbqfoqjVSeWYb5ZgSJ1J5pFIsmM63ClMqGEBprPBg== X-Received: by 2002:a37:5a47:: with SMTP id o68mr21575955qkb.423.1608859257152; Thu, 24 Dec 2020 17:20:57 -0800 (PST) Received: from rockpro64.hsd1.md.comcast.net ([2601:153:900:7730::20]) by smtp.gmail.com with ESMTPSA id x47sm17583505qtb.86.2020.12.24.17.20.55 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 24 Dec 2020 17:20:56 -0800 (PST) From: Peter Geis To: Michael Turquette , Stephen Boyd , Peter De Schrijver , Prashant Gaikwad , Thierry Reding , Jonathan Hunter , Jaroslav Kysela , Takashi Iwai , Sameer Pujar , Mohan Kumar Cc: linux-clk@vger.kernel.org, linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org, Peter Geis Subject: [PATCH 0/2] fix tegra-hda on tegra30 devices Date: Fri, 25 Dec 2020 01:20:24 +0000 Message-Id: <20201225012025.507803-1-pgwipeout@gmail.com> X-Mailer: git-send-email 2.25.1 MIME-Version: 1.0 Precedence: bulk List-ID: X-Mailing-List: linux-tegra@vger.kernel.org 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 previously 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 universally to the tegra-hda device to resolve the issues 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. Peter Geis (2): clk: tegra30: Add hda clock default rates to clock driver ALSA: hda/tegra: fix tegra-hda on tegra30 soc drivers/clk/tegra/clk-tegra30.c | 2 ++ sound/pci/hda/hda_tegra.c | 3 +-- 2 files changed, 3 insertions(+), 2 deletions(-)