alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Peter Geis <pgwipeout@gmail.com>
Cc: alsa-devel@alsa-project.org,
	Prashant Gaikwad <pgaikwad@nvidia.com>,
	Sameer Pujar <spujar@nvidia.com>, Stephen Boyd <sboyd@kernel.org>,
	linux-kernel@vger.kernel.org,
	Michael Turquette <mturquette@baylibre.com>,
	linux-clk@vger.kernel.org, Takashi Iwai <tiwai@suse.com>,
	Jonathan Hunter <jonathanh@nvidia.com>,
	Thierry Reding <thierry.reding@gmail.com>,
	linux-tegra@vger.kernel.org, Mohan Kumar <mkumard@nvidia.com>,
	Peter De Schrijver <pdeschrijver@nvidia.com>
Subject: Re: [PATCH 0/2] fix tegra-hda on tegra30 devices
Date: Mon, 04 Jan 2021 15:25:23 +0100	[thread overview]
Message-ID: <s5hft3g93u4.wl-tiwai@suse.de> (raw)
In-Reply-To: <20201225012025.507803-1-pgwipeout@gmail.com>

On Fri, 25 Dec 2020 02:20:24 +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 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

Can Nvidia people look at those?


thanks,

Takashi

> 
>  drivers/clk/tegra/clk-tegra30.c | 2 ++
>  sound/pci/hda/hda_tegra.c       | 3 +--
>  2 files changed, 3 insertions(+), 2 deletions(-)
> 
> -- 
> 2.25.1
> 

      parent reply	other threads:[~2021-01-04 14:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-25  1:20 [PATCH 0/2] fix tegra-hda on tegra30 devices Peter Geis
2020-12-25  1:20 ` [PATCH 1/2] clk: tegra30: Add hda clock default rates to clock driver Peter Geis
2021-01-05 10:12   ` Jon Hunter
2020-12-25  1:20 ` [PATCH 2/2] ALSA: hda/tegra: fix tegra-hda on tegra30 soc Peter Geis
2021-01-05  6:30   ` Sameer Pujar
2021-01-06 21:21     ` Peter Geis
2021-01-08  8:00       ` Sameer Pujar
2021-01-08 10:54         ` Jon Hunter
2021-01-08 11:33           ` Jon Hunter
2021-01-08 12:19             ` Peter Geis
2021-01-04 14:25 ` Takashi Iwai [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=s5hft3g93u4.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=jonathanh@nvidia.com \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=mkumard@nvidia.com \
    --cc=mturquette@baylibre.com \
    --cc=pdeschrijver@nvidia.com \
    --cc=pgaikwad@nvidia.com \
    --cc=pgwipeout@gmail.com \
    --cc=sboyd@kernel.org \
    --cc=spujar@nvidia.com \
    --cc=thierry.reding@gmail.com \
    --cc=tiwai@suse.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).