mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mario Limonciello <mario.limonciello@amd.com>
To: Alex Deucher <alexdeucher@gmail.com>, Sebastian Reichel <sre@kernel.org>
Cc: amd-gfx@lists.freedesktop.org,
	Alex Deucher <alexander.deucher@amd.com>,
	Jun.ma2@amd.com, linux-kernel@vger.kernel.org,
	linux-pm@vger.kernel.org
Subject: Re: [PATCH 0/3] Fix Navi3x boot and hotplug problems
Date: Thu, 28 Sep 2023 15:01:16 -0500	[thread overview]
Message-ID: <8cae7afb-3e6d-42cd-925f-4ee3af920178@amd.com> (raw)
In-Reply-To: <CADnq5_NHQhUZ9DzNtOy67Hx1g2_ZeBfKPC6O22YY_bzSJsMiUw@mail.gmail.com>

On 9/28/2023 13:00, Alex Deucher wrote:
> On Thu, Sep 28, 2023 at 12:41 PM Mario Limonciello
> <mario.limonciello@amd.com> wrote:
>>
>> On some OEM systems multiple navi3x dGPUS are triggering RAS errors
>> and BACO errors.
>>
>> These errors come from elements of the OEM system that weren't part of
>> original test environment.  This series addresses those problems.
>>
>> NOTE: Although this series touches two subsystems, I would prefer to
>> take this all through DRM because there is a workaround in linux-next
>> that I would like to be reverted at the same time as picking up the first
>> two patches.
> 
> FWIW, the workaround is not in linux-next yet.  At the time I thought
> it was already fixed by the fixes in ucsi and power supply when we
> first encountered this.

I looked yesterday and I did see it there, but I think it was 
specifically because it had merged the amd-staging-drm-next tree.
It's not there today..

If Sebastian is OK, I'd still rather keep it all together so that people 
testing amd-staging-drm-next get the fixes.

> 
> Alex
> 
>>
>> Mario Limonciello (3):
>>    drm/amd: Fix detection of _PR3 on the PCIe root port
>>    power: supply: Don't count 'unknown' scope power supplies
>>    Revert "drm/amd/pm: workaround for the wrong ac power detection on smu
>>      13.0.0"
>>
>>   drivers/gpu/drm/amd/amdgpu/amdgpu_device.c           | 2 +-
>>   drivers/gpu/drm/amd/pm/swsmu/smu13/smu_v13_0.c       | 3 ++-
>>   drivers/gpu/drm/amd/pm/swsmu/smu13/smu_v13_0_0_ppt.c | 1 +
>>   drivers/power/supply/power_supply_core.c             | 2 +-
>>   4 files changed, 5 insertions(+), 3 deletions(-)
>>
>> --
>> 2.34.1
>>


      reply	other threads:[~2023-09-28 20:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-26 22:59 Mario Limonciello
2023-09-26 22:59 ` [PATCH 1/3] drm/amd: Fix detection of _PR3 on the PCIe root port Mario Limonciello
2023-09-28 16:58   ` Deucher, Alexander
2023-09-26 22:59 ` [PATCH 2/3] power: supply: Don't count 'unknown' scope power supplies Mario Limonciello
2023-09-30 20:18   ` Sebastian Reichel
2023-10-02  0:00     ` Mario Limonciello
2023-10-04 23:10       ` Sebastian Reichel
2023-10-05 19:51         ` Mario Limonciello
2023-09-26 22:59 ` [PATCH 3/3] Revert "drm/amd/pm: workaround for the wrong ac power detection on smu 13.0.0" Mario Limonciello
2023-09-28 18:00 ` [PATCH 0/3] Fix Navi3x boot and hotplug problems Alex Deucher
2023-09-28 20:01   ` Mario Limonciello [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=8cae7afb-3e6d-42cd-925f-4ee3af920178@amd.com \
    --to=mario.limonciello@amd.com \
    --cc=Jun.ma2@amd.com \
    --cc=alexander.deucher@amd.com \
    --cc=alexdeucher@gmail.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=sre@kernel.org \
    /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

all inboxes | Powered by JetHome®