From: Bjorn Helgaas <helgaas@kernel.org>
To: Guchun Chen <guchun.chen@amd.com>
Cc: amd-gfx@lists.freedesktop.org, alexander.deucher@amd.com,
hawking.zhang@amd.com, lijo.lazar@amd.com, evan.quan@amd.com,
Stefan Roese <sr@denx.de>,
linux-pci@vger.kernel.org
Subject: Re: [PATCH 1/3] drm/amd/pm/smu11: BACO is supported when it's in BACO state
Date: Tue, 27 Dec 2022 12:23:39 -0600 [thread overview]
Message-ID: <20221227182339.GA452254@bhelgaas> (raw)
In-Reply-To: <20221123014307.263178-1-guchun.chen@amd.com>
[+cc Stefan, linux-pci]
On Wed, Nov 23, 2022 at 09:43:07AM +0800, Guchun Chen wrote:
> Return true early if ASIC is in BACO state already, no need
> to talk to SMU. It can fix the issue that driver was not
> calling BACO exit at all in runtime pm resume, and a timing
> issue leading to a PCI AER error happened eventually.
This sounds suspiciously racy.
> Fixes: 8795e182b02d ("PCI/portdrv: Don't disable AER reporting in get_port_device_capability()")
To clarify, this patch avoids a driver problem, not a problem with
8795e182b02d.
See question below.
> Suggested-by: Lijo Lazar <lijo.lazar@amd.com>
> Signed-off-by: Guchun Chen <guchun.chen@amd.com>
> ---
> drivers/gpu/drm/amd/pm/swsmu/smu11/smu_v11_0.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/gpu/drm/amd/pm/swsmu/smu11/smu_v11_0.c b/drivers/gpu/drm/amd/pm/swsmu/smu11/smu_v11_0.c
> index 70b560737687..ad5f6a15a1d7 100644
> --- a/drivers/gpu/drm/amd/pm/swsmu/smu11/smu_v11_0.c
> +++ b/drivers/gpu/drm/amd/pm/swsmu/smu11/smu_v11_0.c
> @@ -1588,6 +1588,10 @@ bool smu_v11_0_baco_is_support(struct smu_context *smu)
> if (amdgpu_sriov_vf(smu->adev) || !smu_baco->platform_support)
> return false;
>
> + /* return true if ASIC is in BACO state already */
> + if (smu_v11_0_baco_get_state(smu) == SMU_BACO_STATE_ENTER)
> + return true;
smu_v13_0_baco_is_support() is essentially identical to
smu_v11_0_baco_is_support(). Does it need a similar change?
> /* Arcturus does not support this bit mask */
> if (smu_cmn_feature_is_supported(smu, SMU_FEATURE_BACO_BIT) &&
> !smu_cmn_feature_is_enabled(smu, SMU_FEATURE_BACO_BIT))
> --
> 2.25.1
>
next parent reply other threads:[~2022-12-27 18:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221123014307.263178-1-guchun.chen@amd.com>
2022-12-27 18:23 ` Bjorn Helgaas [this message]
2022-12-28 2:02 ` [PATCH 1/3] drm/amd/pm/smu11: BACO is supported when it's in BACO state Chen, Guchun
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=20221227182339.GA452254@bhelgaas \
--to=helgaas@kernel.org \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=evan.quan@amd.com \
--cc=guchun.chen@amd.com \
--cc=hawking.zhang@amd.com \
--cc=lijo.lazar@amd.com \
--cc=linux-pci@vger.kernel.org \
--cc=sr@denx.de \
/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