From: Takashi Iwai <tiwai@suse.de>
To: <Mario.Limonciello@dell.com>
Cc: <alexdeucher@gmail.com>, <kherbst@redhat.com>,
<nouveau@lists.freedesktop.org>, <rafael.j.wysocki@intel.com>,
<linux-kernel@vger.kernel.org>, <dri-devel@lists.freedesktop.org>,
<linux-acpi@vger.kernel.org>, <alex.hung@canonical.com>,
<bskeggs@redhat.com>, <airlied@redhat.com>
Subject: Re: [Nouveau] [PATCH 1/7] Revert "ACPI / OSI: Add OEM _OSI string to enable dGPU direct output"
Date: Thu, 15 Aug 2019 19:43:59 +0200 [thread overview]
Message-ID: <s5h4l2i9vds.wl-tiwai@suse.de> (raw)
In-Reply-To: <8724585e50004bc8b6f310587555f4a1@AUSX13MPC101.AMER.DELL.COM>
On Thu, 15 Aug 2019 18:19:52 +0200,
<Mario.Limonciello@dell.com> wrote:
>
> > -----Original Message-----
> > From: Takashi Iwai <tiwai@suse.de>
> > Sent: Thursday, August 15, 2019 9:57 AM
> > To: Alex Deucher
> > Cc: Karol Herbst; Limonciello, Mario; nouveau; Rafael J . Wysocki; LKML; dri-devel;
> > Linux ACPI Mailing List; Alex Hung; Ben Skeggs; David Airlie
> > Subject: Re: [Nouveau] [PATCH 1/7] Revert "ACPI / OSI: Add OEM _OSI string to
> > enable dGPU direct output"
> >
> >
> > [EXTERNAL EMAIL]
> >
> > On Thu, 15 Aug 2019 16:37:05 +0200,
> > Alex Deucher wrote:
> > >
> > > On Thu, Aug 15, 2019 at 10:25 AM Karol Herbst <kherbst@redhat.com> wrote:
> > > >
> > > > On Thu, Aug 15, 2019 at 4:20 PM <Mario.Limonciello@dell.com> wrote:
> > > > >
> > > > > > > There are definitely going to be regressions on machines in the field
> > with the
> > > > > > > in tree drivers by reverting this. I think we should have an answer for all
> > of
> > > > > > those
> > > > > > > before this revert is accepted.
> > > > > > >
> > > > > > > Regarding systems with Intel+NVIDIA, we'll have to work with partners
> > to
> > > > > > collect
> > > > > > > some information on the impact of reverting this.
> > > > > > >
> > > > > > > When this is used on a system with Intel+AMD the ASL configures AMD
> > GPU to
> > > > > > use
> > > > > > > "Hybrid Graphics" when on Windows and "Power Express" and
> > "Switchable
> > > > > > Graphics"
> > > > > > > when on Linux.
> > > > > >
> > > > > > and what's exactly the difference between those? And what's the actual
> > > > > > issue here?
> > > > >
> > > > > DP/HDMI is not detected unless plugged in at bootup. It's due to missing
> > HPD
> > > > > events.
> > > > >
> > > >
> > > > afaik Lyude was working on fixing all that, at least for some drivers.
> > > > If there is something wrong, we still should fix the drivers, not
> > > > adding ACPI workarounds.
> > > >
> > > > Alex: do you know if there are remaining issues regarding that with amdgpu?
> > >
> > > There was an issue with hpd events not making it to the audio side
> > > when things were powered down that was fixed with this patch set:
> > > https://patchwork.freedesktop.org/patch/316793/
> > > Those patches depended on a bunch of alsa changes as well which may
> > > have not been available in the distro used for a particular OEM
> > > program.
> >
> > FYI, the corresponding commit for ALSA part is destined for 5.4
> > kernel:
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git/commit/?id=ade
> > 49db337a9d44ac5835cfce1ee873549011b27
> >
> > BTW, Nouveau should suffer from the same problem. The patch to add
> > the audio component support is found at:
> > https://patchwork.freedesktop.org/patch/319131/
> >
> >
>
> It sounds like 5.3rcX won't be a useful check then.
For HDMI/DP audio, right, the main pieces are still missing in 5.3.
But there is no regression in this regard, OTOH.
> So am I correct to understand that everything related to the AMD failures
> described in this thread should be in linux-next at this point?
I'm not sure what you're referring as "AMD failures", so leave this
question to AMD people :)
Takashi
next prev parent reply other threads:[~2019-08-15 17:44 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-14 21:31 [PATCH 0/7] Adding a proper workaround for fixing RTD3 issues with Nouveau Karol Herbst
2019-08-14 21:31 ` [PATCH 1/7] Revert "ACPI / OSI: Add OEM _OSI string to enable dGPU direct output" Karol Herbst
2019-08-14 21:49 ` Alex Hung
2019-08-14 22:47 ` [Nouveau] " Dave Airlie
2019-08-15 13:55 ` Mario.Limonciello
2019-08-15 14:04 ` Karol Herbst
2019-08-15 14:13 ` Alex Deucher
2019-08-15 14:15 ` Karol Herbst
2019-08-15 14:17 ` Alex Deucher
2019-08-15 14:23 ` Mario.Limonciello
2019-08-15 14:35 ` Karol Herbst
2019-08-15 14:41 ` Alex Deucher
2019-08-15 14:19 ` Mario.Limonciello
2019-08-15 14:25 ` Karol Herbst
2019-08-15 14:34 ` Mario.Limonciello
2019-08-15 14:36 ` Karol Herbst
2019-08-15 14:37 ` Alex Deucher
2019-08-15 14:56 ` Takashi Iwai
2019-08-15 16:19 ` Mario.Limonciello
2019-08-15 17:43 ` Takashi Iwai [this message]
2019-08-15 18:34 ` Alex Deucher
2019-08-15 14:59 ` Alex Deucher
2019-08-15 14:11 ` Daniel Vetter
2019-08-19 9:52 ` Rafael J. Wysocki
2019-09-05 15:51 ` Karol Herbst
2019-09-05 16:26 ` Rafael J. Wysocki
2019-09-09 21:07 ` Alex Hung
2019-10-21 2:14 ` Alex Hung
2019-10-21 8:14 ` Rafael J. Wysocki
2019-10-21 8:48 ` Karol Herbst
2019-10-21 8:54 ` Rafael J. Wysocki
2019-09-05 16:35 ` Alex Deucher
2019-08-14 21:31 ` [PATCH 2/7] Revert "ACPI / OSI: Add OEM _OSI string to enable NVidia HDMI audio" Karol Herbst
2020-12-10 17:59 ` Lyude Paul
2019-08-14 21:31 ` [PATCH 3/7] Revert "ACPI / OSI: Add OEM _OSI strings to disable NVidia RTD3" Karol Herbst
2019-08-14 23:34 ` Alex Hung
2019-08-15 4:44 ` Karol Herbst
2019-08-14 21:31 ` [PATCH 4/7] drm/nouveau/pci: enable pcie link changes for pascal Karol Herbst
2019-08-14 21:31 ` [PATCH 5/7] drm/nouveau/pci: add nvkm_pcie_get_speed Karol Herbst
2019-08-14 21:31 ` [PATCH 6/7] drm/nouveau/pci: save the boot pcie link speed and restore it on fini Karol Herbst
2019-08-14 21:31 ` [PATCH 7/7] drm/nouveau: abort runtime suspend if we hit an error Karol Herbst
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=s5h4l2i9vds.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=Mario.Limonciello@dell.com \
--cc=airlied@redhat.com \
--cc=alex.hung@canonical.com \
--cc=alexdeucher@gmail.com \
--cc=bskeggs@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kherbst@redhat.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nouveau@lists.freedesktop.org \
--cc=rafael.j.wysocki@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).