HDMI Audio screwed up w/ recent kernels
On Tue, Dec 27, 2016 at 12:17 PM, James Cloos wrote: >> "DV" == Daniel Vetter writes: > > DV> amdgpu doesn't yet support hdmi audio. > > Then why does it support the amdgpu.audio command line option, and why > does booting an amdgpu kernel with amdgpu.audio=1 sound the same as > booting a radeon kernel w/ radeon.audio=1? That option is just a carry over from when the amdgpu was copied from radeon. There is some code for older asics left over from when the code was originally ported from radeon. If you want hdmi audio support you need to use the new dc modesetting code we are working on: https://cgit.freedesktop.org/~agd5f/linux/log/?h=amd-staging-4.7 As for radeon, a bisection would help. If both drivers worked before and now both have issues, I'd suggest looking at the hda audio driver. Alex
[Bug 191291] [amdgpu] mouse cursor disappearing on X11 (KDE Plasma)
https://bugzilla.kernel.org/show_bug.cgi?id=191291 Alex Deucher changed: What|Removed |Added CC||alexdeucher at gmail.com --- Comment #1 from Alex Deucher --- Already fixed: http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=a1f49cc179ce6b7b7758ae3ff5cdb138d0ee0f56 -- You are receiving this mail because: You are watching the assignee of the bug.
[Bug 96243] GPU initialization fails when running in VM
https://bugs.freedesktop.org/show_bug.cgi?id=96243 --- Comment #1 from Alex Deucher --- Can you try a newer kernel? -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161231/c54e6e29/attachment-0001.html>
HDMI Audio screwed up w/ recent kernels
> "AD" == Alex Deucher writes: AD> That option is just a carry over from when the amdgpu was copied from AD> radeon. There is some code for older asics left over from when the AD> code was originally ported from radeon. If you want hdmi audio AD> support you need to use the new dc modesetting code we are working on: AD> https://cgit.freedesktop.org/~agd5f/linux/log/?h=amd-staging-4.7 AD> As for radeon, a bisection would help. If both drivers worked before AD> and now both have issues, I'd suggest looking at the hda audio driver. All I know is that radeon audio worked fine in 3.x and stopped working in 4.x Where stopped working means fairly recognizable audio which sounds mixed with white noise. I doubt I can bisect. The screen it uses is in almost constant use In order for the fb to be there from boot, the firmware is all compiled into the kernels via CONFIG_EXTRA_FIRMWARE. Given that, with 4.9, the audio has exactly the same problem with amdgpu as with radeon, I suspect the actual problem is in the firmware. If so, and since I do not have whatever firmware files were installed back when I compiled the 3. kernels, I doubt bisecting the kernel would help. -JimC -- James Cloos OpenPGP: 0x997A9F17ED7DAEA6
[Bug 191571] AMD APU R4 hangs during hibernation - regression
https://bugzilla.kernel.org/show_bug.cgi?id=191571 Przemek changed: What|Removed |Added Regression|No |Yes -- You are receiving this mail because: You are watching the assignee of the bug.
[Bug 191571] AMD APU R4 hangs during hibernation - regression
https://bugzilla.kernel.org/show_bug.cgi?id=191571 Felix Schwarz changed: What|Removed |Added CC||felix.schwarz at oss.schwarz.e ||u --- Comment #4 from Felix Schwarz --- according to the reporter's bisect log (comment #3) the first bad commit is: commit 274ad65c9d02bdcbee9bae045517864c3521d530 Author: Jérome Glisse Date: Fri Mar 18 16:58:39 2016 +0100 drm/radeon: hard reset r600 and newer GPU when hibernating. Some GPU block like UVD and VCE require hard reset to be properly resume if there is no real powerdown of the asic like during various hibernation step. This patch perform such hard reset. Reviewed-by: Christian König Signed-off-by: Jérôme Glisse Cc: Alex Deucher Cc: Christian König Signed-off-by: Alex Deucher -- You are receiving this mail because: You are watching the assignee of the bug.
[Bug 99078] Desktop icons oversaturated with red after December 11 2016 update
https://bugs.freedesktop.org/show_bug.cgi?id=99078 --- Comment #20 from junkmailnotread at yahoo.com --- I had the same problem with Gentoo Linux when upgrading from llvm-3.9.0 to llvm-3.9.1: fbpanel icons exhibited a red shift. Reverting the above mentioned commit against llvm-3.9.1 fixed the problem. -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161231/7c1f6158/attachment.html>
[Bug 99236] System (seems to) completely freezes when interacting with java swing applications.
https://bugs.freedesktop.org/show_bug.cgi?id=99236 Bug ID: 99236 Summary: System (seems to) completely freezes when interacting with java swing applications. Product: DRI Version: DRI git Hardware: x86 (IA32) OS: Linux (All) Status: NEW Severity: major Priority: medium Component: DRM/AMDgpu Assignee: dri-devel at lists.freedesktop.org Reporter: tmp6154 at yandex.ru I'm not completely certain whether it's related to AMD GPU driver or not, but it's rather strange issue that I can get stable reproduce for. I'm running a Gentoo system with AMD Radeon RX 480, with git AMD GPU driver and git version of mesa. When interacting with scrollable JTextAreas in Java Swing application, I get a stably reproducible issue (100%). Since this affects multiple java swing applications (e.g. eclipse), including the program I'm developing at the time, I can attempt to put together a reproducer java app, if that's needed. For first 2-3 seconds, mouse cursor moves jittery, then it stops to move at all and display keeps displaying same frozen state. Nothing appears to work, including Ctrl+Alt+F1, etc. But despite machine looking completely locked up, in fact, it's not. I can ssh into it and issue reboot command. During that time, display doesn't shows any signs of life until the moment when machine reboots (but I can hear KDE shutdown sound). This occurs only under JRE8, both icedtea and oracle variants. Under JRE7 issue doesn't trigger. If memory serves, JRE8 brought improvements to hardware-accelerated GUI rendering. This is especially strange, since Swing GUI framework renders it's own GUI widgets. Considering that even Ctrl+Alt+F1 doesn't work, I suppose problem happens on kernel level, possibly in AMD GPU driver. -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161231/ba711987/attachment.html>
[Bug 99236] System (seems to) completely freeze when interacting with java swing applications.
https://bugs.freedesktop.org/show_bug.cgi?id=99236 Vitaly Ostrosablin changed: What|Removed |Added Summary|System (seems to) |System (seems to) |completely freezes when |completely freeze when |interacting with java swing |interacting with java swing |applications. |applications. -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161231/e1aa11ee/attachment.html>
[Bug 99236] System (seems to) completely freeze when interacting with java swing applications.
https://bugs.freedesktop.org/show_bug.cgi?id=99236 Vitaly Ostrosablin changed: What|Removed |Added Hardware|x86 (IA32) |x86-64 (AMD64) -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161231/6bfe000a/attachment.html>
[PATCH] drm/i915: Fix not finding the VBT when it overlaps with OPREGION_ASLE_EXT
Hi,
On 27-12-16 11:58, Jani Nikula wrote:
> On Sun, 25 Dec 2016, Hans de Goede wrote:
>> If there is no OPREGION_ASLE_EXT then a VBT stored in mailbox #4 may
>> use the ASLE_EXT parts of the opregion. Adjust the vbt_size calculation
>> for a vbt in mailbox #4 for this.
>>
>> This fixes the driver not finding the VBT on a jumper ezpad mini3
>> cherrytrail tablet.
>
> Thanks for the patch. I think you're onto something, but I don't think
> the patch is quite correct. That said, I'm not sure myself yet what
> would be. ;)
>
> Without the change, does intel_bios_is_valid_vbt() return true anyway?
No.
> I.e. do you get "Found valid VBT in ACPI OpRegion (Mailbox #4)\n" in
> log?
No.
> If not, which of the debug messages in intel_bios_is_valid_vbt() do
> you get?
I get "BDB incomplete", which is why I wrote this patch and believe
this patch is the right solution. With this patch everything works,
> In the latter case, I suspect you'll end up with failure in intel_bios.c
> with either "No MIPI config BDB found" or "No MIPI Sequence found,
> parsing complete\n".
I don't remember the exact error, other then getting the
"BDB incomplete" error, and the i915 driver not listing the DSI connector
under /sys/class drm.
What makes you say: "but I don't think the patch is quite correct" why
should the code still keep the OPREGION_ASLE_EXT start as end of the
mailbox #4 vbt if there is the ASLE extenstion is not used ?
Regards,
Hans
>> Cc: stable at vger.kernel.org
>> Signed-off-by: Hans de Goede
>> ---
>> Note even with this fixed the panel still does not work with 4.9,
>> but it does with drm-intel-next-queued :) I believe the missing bit in
>> 4.9 is the "drm/915: Parsing the missed out DTD fields from the VBT"
>> commit, but I've not verified this.
>> ---
>> drivers/gpu/drm/i915/intel_opregion.c | 4 +++-
>> 1 file changed, 3 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/i915/intel_opregion.c
>> b/drivers/gpu/drm/i915/intel_opregion.c
>> index f4429f6..eff35ae 100644
>> --- a/drivers/gpu/drm/i915/intel_opregion.c
>> +++ b/drivers/gpu/drm/i915/intel_opregion.c
>> @@ -982,7 +982,9 @@ int intel_opregion_setup(struct drm_i915_private
>> *dev_priv)
>> opregion->vbt_size = vbt_size;
>> } else {
>> vbt = base + OPREGION_VBT_OFFSET;
>> -vbt_size = OPREGION_ASLE_EXT_OFFSET -
>> OPREGION_VBT_OFFSET;
>> +vbt_size = (mboxes & MBOX_ASLE_EXT) ?
>> +OPREGION_ASLE_EXT_OFFSET : OPREGION_SIZE;
>> +vbt_size -= OPREGION_VBT_OFFSET;
>> if (intel_bios_is_valid_vbt(vbt, vbt_size)) {
>> DRM_DEBUG_KMS("Found valid VBT in ACPI OpRegion
>> (Mailbox #4)\n");
>> opregion->vbt = vbt;
>
[Bug 191291] [amdgpu] mouse cursor disappearing on X11 (KDE Plasma)
https://bugzilla.kernel.org/show_bug.cgi?id=191291 --- Comment #2 from Johannes Hirte --- (In reply to Alex Deucher from comment #1) > Already fixed: > http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/ > ?id=a1f49cc179ce6b7b7758ae3ff5cdb138d0ee0f56 No, as I wrote, this one was applied and I've reverted this too. Additionally I don't see how a1f49cc179ce6b7b7758ae3ff5cdb138d0ee0f56 could be relevant. Carrizo is DCE11 not 6 or 8. -- You are receiving this mail because: You are watching the assignee of the bug.
[Bug 99120] VERDE 7770 - glxdemo, vlc/glx, weston fail with garbled screen. Elsewhere blurry text rendering when focus lost
https://bugs.freedesktop.org/show_bug.cgi?id=99120 --- Comment #12 from Larry <5lokuf+c77xmvwa3y1jk at sharklasers.com> --- According to phoronix (April 20th) the new experimental support for HD 7000 in amdgpu is basically inherited from the radeonsi driver. If true, that explains why they share same critical issues with respect to SI/Verde. CCing Tom St Denis from AMD whose commits amdgpu seem to deal with that generation. I understand that the amdgpu support for HD7700 is experimental (and, lower priority). Please just be aware that the existing drivers you're basing off of have critical issues (I'm posting this on https://bugs.freedesktop.org/show_bug.cgi?id=99120). As AMD's cutoff for amdgpu means that HD7700 should be supported eventually, I hope whatever engineering resources are presently allocated to improving the state of linux support from AMD GPU products will deal with these problems (i.e. utterly unusable GL) while the momentum is strong. Thanks, and Happy new year! -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161231/d8df73e7/attachment-0001.html>
[PATCH 01/10] drm : adds Y-coordinate and Colorimetry Format
PSR2 vsc revision number hb2( as per table 6-11)is updated to 4 or 5 based on Y cordinate and Colorimetry Format as below 04h = 3D stereo + PSR/PSR2 + Y-coordinate. 05h = -3D stereo- + PSR/PSR2 + Y-coordinate + Pixel Encoding/Colorimetry Format indication. A DP Source device is allowed to indicate the pixel encoding/colorimetry format to the DP Sink device with VSC SDP only when the DP Sink device supports it ( i.e.,VSC_SDP_EXTENSION_FOR_COLORIMETRY_SUPPORTED bit in the DPRX_FEATURE_ENUMERATION_LIST register (DPCD Address 02210h, bit 3; is set to 1). v2: (Jani) - Change DP_PSR_Y_COORDINATE to DP_PSR2_SU_Y_COORDINATE_REQUIRED. - Add DP_PSR2_SU_GRANULARITY_REQUIRED. - Change DPRX_FEATURE_ENUMERATION_LIST to DP_DPRX. - Add GTC_CAP and AV_SYNC_CAP, other bits in DPRX_FEATURE_ENUMERATION_LIST. v3: (Jani) - Add support for bits 7:4 and 1 as per DP v1.4 for DPRX_FEATURE_ENUMERATION_LIST. Cc: Rodrigo Vivi Cc: Jim Bride Signed-off-by: Vathsala Nagaraju Signed-off-by: Patil Deepti --- include/drm/drm_dp_helper.h | 13 - 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/include/drm/drm_dp_helper.h b/include/drm/drm_dp_helper.h index 55bbeb0..0468135 100644 --- a/include/drm/drm_dp_helper.h +++ b/include/drm/drm_dp_helper.h @@ -194,7 +194,8 @@ # define DP_PSR_SETUP_TIME_0(6 << 1) # define DP_PSR_SETUP_TIME_MASK (7 << 1) # define DP_PSR_SETUP_TIME_SHIFT1 - +# define DP_PSR2_SU_Y_COORDINATE_REQUIRED (1 << 4) /* eDP 1.4a */ +# define DP_PSR2_SU_GRANULARITY_REQUIRED(1 << 5) /* eDP 1.4b */ /* * 0x80-0x8f describe downstream port capabilities, but there are two layouts * based on whether DP_DETAILED_CAP_INFO_AVAILABLE was set. If it was not, @@ -568,6 +569,16 @@ #define DP_RECEIVER_ALPM_STATUS0x200b /* eDP 1.4 */ # define DP_ALPM_LOCK_TIMEOUT_ERROR(1 << 0) +#define DP_DPRX_FEATURE_ENUMERATION_LIST0x2210 /* DP 1.3 */ +# define DP_GTC_CAP(1 << 0) /* DP 1.3 */ +# define DP_SST_SPLIT_SDP_CAP (1 << 1) /* DP 1.4 */ +# define DP_AV_SYNC_CAP(1 << 2) /* DP 1.3 */ +# define DP_VSC_SDP_EXT_FOR_COLORIMETRY_SUPPORTED (1 << 3) /* DP 1.3 */ +# define DP_VSC_EXT_VESA_SDP_SUPPORTED (1 << 4) /* DP 1.4 */ +# define DP_VSC_EXT_VESA_SDP_CHAINING_SUPPORTED(1 << 5) /* DP 1.4 */ +# define DP_VSC_EXT_CEA_SDP_SUPPORTED (1 << 6) /* DP 1.4 */ +# define DP_VSC_EXT_CEA_SDP_CHAINING_SUPPORTED (1 << 7) /* DP 1.4 */ + /* DP 1.2 Sideband message defines */ /* peer device type - DP 1.2a Table 2-92 */ #define DP_PEER_DEVICE_NONE0x0 -- 1.9.1
