mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kai-Heng Feng <kaihengf@nvidia.com>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: Luke Jones <luke@ljones.dev>,
	Mario Limonciello <superm1@kernel.org>,
	Bjorn Helgaas <bhelgaas@google.com>,
	"open list:PCI SUBSYSTEM" <linux-pci@vger.kernel.org>,
	open list <linux-kernel@vger.kernel.org>,
	dri-devel@lists.freedesktop.org,
	Mario Limonciello <mario.limonciello@amd.com>,
	Alex Deucher <alexander.deucher@amd.com>
Subject: Re: [PATCH] PCI/VGA: Don't assume only VGA device found is the boot VGA device
Date: Wed, 23 Oct 2024 09:27:11 +0800	[thread overview]
Message-ID: <fd7cae9a-5ee1-4e18-915d-4115f0a6a156@nvidia.com> (raw)
In-Reply-To: <CADnq5_OjfJzcOqa=NbWVw5ENvi+nmvNAZX0u_0hOvk3EVoh0bw@mail.gmail.com>



On 2024/10/22 9:04 PM, Alex Deucher wrote:
> External email: Use caution opening links or attachments
> 
> 
> On Tue, Oct 22, 2024 at 2:31 AM Kai-Heng Feng <kaihengf@nvidia.com> wrote:
>>
>> Hi Luke,
>>
>> On 2024/10/15 4:04 PM, Luke Jones wrote:
>>> On Mon, 14 Oct 2024, at 5:25 PM, Mario Limonciello wrote:
>>>> From: Mario Limonciello <mario.limonciello@amd.com>
>>>>
>>>> The ASUS GA605W has a NVIDIA PCI VGA device and an AMD PCI display device.
>>>>
>>>> ```
>>>> 65:00.0 VGA compatible controller: NVIDIA Corporation AD106M [GeForce
>>>> RTX 4070 Max-Q / Mobile] (rev a1)
>>>> 66:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI]
>>>> Strix [Radeon 880M / 890M] (rev c1)
>>>> ```
>>>>
>>>> The fallback logic in vga_is_boot_device() flags the NVIDIA dGPU as the
>>>> boot VGA device, but really the eDP is connected to the AMD PCI display
>>>> device.
>>>>
>>>> Drop this case to avoid marking the NVIDIA dGPU as the boot VGA device.
>>>>
>>>> Suggested-by: Alex Deucher <alexander.deucher@amd.com>
>>>> Reported-by: Luke D. Jones <luke@ljones.dev>
>>>> Closes: https://gitlab.freedesktop.org/drm/amd/-/issues/3673
>>>> Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
>>>> ---
>>>>    drivers/pci/vgaarb.c | 7 -------
>>>>    1 file changed, 7 deletions(-)
>>>>
>>>> diff --git a/drivers/pci/vgaarb.c b/drivers/pci/vgaarb.c
>>>> index 78748e8d2dba..05ac2b672d4b 100644
>>>> --- a/drivers/pci/vgaarb.c
>>>> +++ b/drivers/pci/vgaarb.c
>>>> @@ -675,13 +675,6 @@ static bool vga_is_boot_device(struct vga_device *vgadev)
>>>>               return true;
>>>>       }
>>>>
>>>> -    /*
>>>> -     * Vgadev has neither IO nor MEM enabled.  If we haven't found any
>>>> -     * other VGA devices, it is the best candidate so far.
>>>> -     */
>>>> -    if (!boot_vga)
>>>> -            return true;
>>>> -
>>>>       return false;
>>>>    }
>>>>
>>>> --
>>>> 2.43.0
>>>
>>> Hi Mario,
>>>
>>> I can verify that this does leave the `boot_vga` attribute set as 0 for the NVIDIA device.
>>
>> Does the following diff work for you?
>> This variant should be less risky for most systems.
>>
>> diff --git a/drivers/pci/vgaarb.c b/drivers/pci/vgaarb.c
>> index 78748e8d2dba..3fb734cb9c1b 100644
>> --- a/drivers/pci/vgaarb.c
>> +++ b/drivers/pci/vgaarb.c
>> @@ -675,6 +675,9 @@ static bool vga_is_boot_device(struct vga_device *vgadev)
>>                   return true;
>>           }
>>
>> +       if (vga_arb_integrated_gpu(&pdev->dev))
>> +               return true;
>> +
> 
> The problem is that the integrated graphics does not support VGA.

Right, so the check has to be used much earlier.

I wonder does the integrated GFX have _DOD/_DOS while the discrete one doesn't? 
If that's the case, vga_arb_integrated_gpu() can be used to differentiate which 
one is the boot GFX.

Kai-Heng

> 
> Alex
> 
>>           /*
>>            * Vgadev has neither IO nor MEM enabled.  If we haven't found any
>>            * other VGA devices, it is the best candidate so far.
>>
>>
>> Kai-Heng
>>
>>>
>>> Tested-by: Luke D. Jones <luke@ljones.dev>
>>


  reply	other threads:[~2024-10-23  1:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-14 15:25 Mario Limonciello
2024-10-14 15:45 ` Alex Deucher
2024-10-14 16:12   ` Mario Limonciello
2024-10-15  8:04 ` Luke Jones
2024-10-22  1:35   ` Kai-Heng Feng
2024-10-22 13:04     ` Alex Deucher
2024-10-23  1:27       ` Kai-Heng Feng [this message]
2024-10-23  8:27         ` Luke Jones
2024-10-23 15:27         ` Alex Deucher
2024-10-25  7:51           ` Kai-Heng Feng
2024-10-25 12:55             ` Alex Deucher
2024-10-31  0:58               ` Kai-Heng Feng
2024-10-31 10:51                 ` Luke Jones

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=fd7cae9a-5ee1-4e18-915d-4115f0a6a156@nvidia.com \
    --to=kaihengf@nvidia.com \
    --cc=alexander.deucher@amd.com \
    --cc=alexdeucher@gmail.com \
    --cc=bhelgaas@google.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=luke@ljones.dev \
    --cc=mario.limonciello@amd.com \
    --cc=superm1@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®