All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 198885] amdgpu.dc=1 on CIK (R4 Mullins APU) brightness impossible to change. by Fn or "echo".
Date: Fri, 23 Feb 2018 16:12:02 +0000	[thread overview]
Message-ID: <bug-198885-2300-DqgpD9DcaG@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-198885-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=198885

--- Comment #5 from Przemek (soprwa@gmail.com) ---
(In reply to Harry Wentland from comment #4)
> Thanks for reporting this. It's currently not hooked up for ASICs older than
> Carrizo. We'll take a look. 
> 
> You're right that it clashes with the kernel's 'no regressions' policy
> should we change pre-VEGA ASIC support with DC to enabled by default.

Hi Harry,

I am glad to hear that the reason is already known, and we are not searching it
blindly.

There is still time till 4.17 merge window ends, so if you would like me to try
out some patches, please do not hesitate.

Thanks,
Przemek.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2018-02-23 16:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-22 13:13 [Bug 198885] New: amdgpu.dc=1 on CIK (R4 Mullins APU) brightness impossible to change. by Fn or "echo" bugzilla-daemon
2018-02-22 15:26 ` [Bug 198885] " bugzilla-daemon
2018-02-22 16:36 ` bugzilla-daemon
2018-02-22 17:01 ` bugzilla-daemon
2018-02-23 14:24 ` bugzilla-daemon
2018-02-23 16:12 ` bugzilla-daemon [this message]
2018-03-27 15:44 ` bugzilla-daemon
2018-03-28  0:20 ` bugzilla-daemon

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=bug-198885-2300-DqgpD9DcaG@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.