Received: by 2002:a25:1985:0:0:0:0:0 with SMTP id 127csp3371590ybz; Mon, 4 May 2020 01:31:52 -0700 (PDT) X-Google-Smtp-Source: APiQypLVKfNXOcsn4mpm9QFP7tMWLBtc+0hFLGIDFWGGZACjAjvljih66BFHmVCIJgwC7hAYG1M6 X-Received: by 2002:a50:c3c2:: with SMTP id i2mr13894985edf.227.1588581112309; Mon, 04 May 2020 01:31:52 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1588581112; cv=none; d=google.com; s=arc-20160816; b=rftiswekoV7LB/G5BPzXWG5hRQuilgfAALL/y8LEGp8vK4AbFimhKFC/uiS214M9Vc RNWdKTHYxCCsLOB4PlTAJTANOM4E2SN2l/gI1KKJXFwD4EJfJ26G/lXzqzwE31MAaJGh ryvHzwFwcGnpPrVCo01tX01ehGccFdDJBqSqt6qdSv434h+pmOSdKD1W3QglwlLLYIag cf8eGoeF1+uETsUm4Rh2LtOgIAoQfF6M3RU7AHXBnOXfWnYEI3UBH0Px1YRYquzEurCe YUsmwwAaIGUc8xqO9/D562odtG+VRsw9PwW5JUrS0D9FG35GY6luwogBgMk8VbyzInnX 5KDw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :in-reply-to:subject:cc:to:from:message-id:date; bh=mFTcrQzIii094arGikC1x3H/1guaUf1JE/e+Xg+Jotw=; b=j2wyyjTPBghWVjhCWBv9AYdRwqC5zw3FeHiyo7txDU5I2WQMQy7SNyK8BNLtvFZhK+ uJdQoCBhZFiOFIXXxi7v8H8CjOnTrIqVauAbAgDNDPTNznErrQXofPVJddVmtz7BSXK3 naQHbrgTRrLuF2VzOEzM88RMbP+tlX+Yv230Q9AqzYd/jyZxkMaw+bK2EobPcpW8YaZM tSL3QY9Sxf9PcIF6c8s6X5gfK4ZinRawQNnldhrMwDP4UBSPnBj0e6z/oEJXpZiFIJbF 7n4kIcNtGjQ/2c5NDXZUQ+qLW7XHhcKxHIzEkX8LkrciobF6ASEgXVtCvJ+FOqZEdIN/ Gv+g== 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 c12si6168281edv.443.2020.05.04.01.31.29; Mon, 04 May 2020 01:31:52 -0700 (PDT) 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 S1728378AbgEDI3S (ORCPT + 99 others); Mon, 4 May 2020 04:29:18 -0400 Received: from mx2.suse.de ([195.135.220.15]:44066 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725941AbgEDI3Q (ORCPT ); Mon, 4 May 2020 04:29:16 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id 0F551ACF1; Mon, 4 May 2020 08:29:16 +0000 (UTC) Date: Mon, 04 May 2020 10:29:14 +0200 Message-ID: From: Takashi Iwai To: Sameer Pujar Cc: , , , , , , , , , , , , Subject: Re: [PATCH 0/3] Tegra194 HW Fixes In-Reply-To: <1588580176-2801-1-git-send-email-spujar@nvidia.com> References: <1588580176-2801-1-git-send-email-spujar@nvidia.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 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 04 May 2020 10:16:13 +0200, Sameer Pujar wrote: > > This series proposes SW workarounds for Tegra194 HDA HW bugs. > Following are the two issues seen: > 1. GCAP register does not reflect true capability. > The actual number of SDO lines is "4", where as it reflects "2". > 2. With 4 SDO line configuration playback fails for, > 44.1K/48K, 2-channel, 16-bps audio stream. > > After fixing [1], issue [2] is uncovered. > As per recommendation by Tegra HW team the workarounds are pushed. > > Testing done > ============ > * Verify GCAP register after registering HDA sound card > * Verify audio playback for 44.1K/48K, 2-channel, 16-bps. > > Sameer Pujar (3): > ALSA: hda/tegra: correct number of SDO lines for Tegra194 > ALSA: hda: add member to store ratio for stripe control > ALSA: hda/tegra: workaround playback failure on Tegra194 Through a quick glance, all changes look good. Is the device already in market, i.e. it had hit users? If yes, I'm going to merge for 5.7, otherwise for 5.8. thanks, Takashi