From: Thierry Reding <thierry.reding@gmail.com>
To: Jon Hunter <jonathanh@nvidia.com>
Cc: devicetree@vger.kernel.org, linux-tegra@vger.kernel.org,
Sameer Pujar <spujar@nvidia.com>
Subject: Re: [PATCH] ARM64: tegra: Disable the ACONNECT for Jetson TX2
Date: Mon, 16 Nov 2020 17:28:36 +0100 [thread overview]
Message-ID: <20201116162836.GA2584498@ulmo> (raw)
In-Reply-To: <20201116162026.5324-1-jonathanh@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 1058 bytes --]
On Mon, Nov 16, 2020 at 04:20:26PM +0000, Jon Hunter wrote:
> Commit ff4c371d2bc0 ("arm64: defconfig: Build ADMA and ACONNECT driver")
> enable the Tegra ADMA and ACONNECT drivers and this is causing resume
> from system suspend to fail on Jetson TX2. Resume is failing because the
> ACONNECT driver is being resumed before the BPMP driver, and the ACONNECT
> driver is attempting to power on a power-domain that is provided by the
> BPMP. While a proper fix for the resume sequencing problem is identified,
> disable the ACONNECT for Jetson TX2 temporarily to avoid breaking system
> suspend.
>
> Please note that ACONNECT driver is used by the Audio Processing Engine
> (APE) on Tegra, but because there is no mainline support for APE on
> Jetson TX2 currently, disabling the ACONNECT does not disable any useful
> feature at the moment.
>
> Signed-off-by: Jon Hunter <jonathanh@nvidia.com>
> ---
> arch/arm64/boot/dts/nvidia/tegra186-p2771-0000.dts | 12 ------------
> 1 file changed, 12 deletions(-)
Applied, thanks.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2020-11-16 16:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 16:20 [PATCH] ARM64: tegra: Disable the ACONNECT for Jetson TX2 Jon Hunter
2020-11-16 16:28 ` Thierry Reding [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=20201116162836.GA2584498@ulmo \
--to=thierry.reding@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=linux-tegra@vger.kernel.org \
--cc=spujar@nvidia.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 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.