From: Sameer Pujar <spujar@nvidia.com> To: <tiwai@suse.com>, <broonie@kernel.org>, <lgirdwood@gmail.com>, <robh+dt@kernel.org>, <thierry.reding@gmail.com>, <perex@perex.cz> Cc: <jonathanh@nvidia.com>, <digetx@gmail.com>, <mkumard@nvidia.com>, <alsa-devel@alsa-project.org>, <devicetree@vger.kernel.org>, <linux-tegra@vger.kernel.org>, <linux-kernel@vger.kernel.org>, Sameer Pujar <spujar@nvidia.com> Subject: [PATCH v2 0/3] Fix Tegra194 HDA regression Date: Mon, 20 Dec 2021 23:00:05 +0530 [thread overview] Message-ID: <1640021408-12824-1-git-send-email-spujar@nvidia.com> (raw) HDA probe failure is observed on Tegra194 based platforms and this happens due to reset failure. This series fixes the problem by skipping the failing reset and DT bindings are updated accordingly. Changelog ========= v1 -> v2: --------- * Updated HDA driver patch to skip the failing reset instead of skipping resets in general for BPMP devices as per comment from Dmitry. * Used a better strucure name for SoC data as per comment from Thierry. * Dropped 'Fixes' tag in binding doc patch as per comment from Dmitry. Sameer Pujar (3): ALSA: hda/tegra: Fix Tegra194 HDA reset failure dt-bindings: sound: tegra: Update HDA resets arm64: tegra: Remove non existent Tegra194 reset .../bindings/sound/nvidia,tegra30-hda.yaml | 13 ++- arch/arm64/boot/dts/nvidia/tegra194.dtsi | 5 +- sound/pci/hda/hda_tegra.c | 96 +++++++++++++++++++--- 3 files changed, 97 insertions(+), 17 deletions(-) -- 2.7.4
WARNING: multiple messages have this Message-ID (diff)
From: Sameer Pujar <spujar@nvidia.com> To: <tiwai@suse.com>, <broonie@kernel.org>, <lgirdwood@gmail.com>, <robh+dt@kernel.org>, <thierry.reding@gmail.com>, <perex@perex.cz> Cc: devicetree@vger.kernel.org, alsa-devel@alsa-project.org, Sameer Pujar <spujar@nvidia.com>, linux-kernel@vger.kernel.org, jonathanh@nvidia.com, linux-tegra@vger.kernel.org, digetx@gmail.com, mkumard@nvidia.com Subject: [PATCH v2 0/3] Fix Tegra194 HDA regression Date: Mon, 20 Dec 2021 23:00:05 +0530 [thread overview] Message-ID: <1640021408-12824-1-git-send-email-spujar@nvidia.com> (raw) HDA probe failure is observed on Tegra194 based platforms and this happens due to reset failure. This series fixes the problem by skipping the failing reset and DT bindings are updated accordingly. Changelog ========= v1 -> v2: --------- * Updated HDA driver patch to skip the failing reset instead of skipping resets in general for BPMP devices as per comment from Dmitry. * Used a better strucure name for SoC data as per comment from Thierry. * Dropped 'Fixes' tag in binding doc patch as per comment from Dmitry. Sameer Pujar (3): ALSA: hda/tegra: Fix Tegra194 HDA reset failure dt-bindings: sound: tegra: Update HDA resets arm64: tegra: Remove non existent Tegra194 reset .../bindings/sound/nvidia,tegra30-hda.yaml | 13 ++- arch/arm64/boot/dts/nvidia/tegra194.dtsi | 5 +- sound/pci/hda/hda_tegra.c | 96 +++++++++++++++++++--- 3 files changed, 97 insertions(+), 17 deletions(-) -- 2.7.4
next reply other threads:[~2021-12-20 17:31 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-20 17:30 Sameer Pujar [this message] 2021-12-20 17:30 ` [PATCH v2 0/3] Fix Tegra194 HDA regression Sameer Pujar 2021-12-20 17:30 ` [PATCH v2 1/3] ALSA: hda/tegra: Fix Tegra194 HDA reset failure Sameer Pujar 2021-12-20 17:30 ` Sameer Pujar 2021-12-21 1:21 ` Dmitry Osipenko 2021-12-21 1:21 ` Dmitry Osipenko 2021-12-21 6:18 ` Sameer Pujar 2021-12-21 6:18 ` Sameer Pujar 2021-12-21 15:20 ` Dmitry Osipenko 2021-12-21 15:20 ` Dmitry Osipenko 2021-12-21 16:03 ` Sameer Pujar 2021-12-21 16:03 ` Sameer Pujar 2021-12-20 17:30 ` [PATCH v2 2/3] dt-bindings: sound: tegra: Update HDA resets Sameer Pujar 2021-12-20 17:30 ` Sameer Pujar 2021-12-20 17:30 ` [PATCH v2 3/3] arm64: tegra: Remove non existent Tegra194 reset Sameer Pujar 2021-12-20 17:30 ` Sameer Pujar
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=1640021408-12824-1-git-send-email-spujar@nvidia.com \ --to=spujar@nvidia.com \ --cc=alsa-devel@alsa-project.org \ --cc=broonie@kernel.org \ --cc=devicetree@vger.kernel.org \ --cc=digetx@gmail.com \ --cc=jonathanh@nvidia.com \ --cc=lgirdwood@gmail.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-tegra@vger.kernel.org \ --cc=mkumard@nvidia.com \ --cc=perex@perex.cz \ --cc=robh+dt@kernel.org \ --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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.