[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <124d4a5c-e198-d8c0-5fb7-65d008852e32@nvidia.com>
Date: Mon, 4 May 2020 14:05:07 +0530
From: Sameer Pujar <spujar@...dia.com>
To: Takashi Iwai <tiwai@...e.de>
CC: <spujar@...dia.com>, <perex@...ex.cz>, <tiwai@...e.com>,
<thierry.reding@...il.com>, <jonathanh@...dia.com>,
<linux-tegra@...r.kernel.org>, <alsa-devel@...a-project.org>,
<linux-kernel@...r.kernel.org>, <sharadg@...dia.com>,
<mkumard@...dia.com>, <viswanathl@...dia.com>,
<rlokhande@...dia.com>, <dramesh@...dia.com>,
<atalambedu@...dia.com>
Subject: Re: [PATCH 0/3] Tegra194 HW Fixes
On 5/4/2020 1:59 PM, Takashi Iwai wrote:
> External email: Use caution opening links or attachments
>
>
> 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.
Yes the device is in the market. But has not been reported by end users.
During internal resting this has been discovered. I am fine with merging
this to 5.8.
Thanks,
Sameer.
>
>
> thanks,
>
> Takashi
Powered by blists - more mailing lists