dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: stable <stable@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	shawn.c.lee@intel.com, Jani Nikula <jani.nikula@intel.com>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Gustavo Padovan <gustavo@padovan.org>,
	cooper.chiou@intel.com, Lee@phenom.ffwll.local,
	dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH AUTOSEL 4.9 08/17] drm/edid: Add 6 bpc quirk for BOE panel.
Date: Thu, 22 Nov 2018 10:53:07 -0500	[thread overview]
Message-ID: <20181122155307.GA6667@sasha-vm> (raw)
In-Reply-To: <CAKMK7uG=Z_GkNR3J2hdYbEfa9nr6UcMx-HanJ6j85jv1beJsVw@mail.gmail.com>

On Wed, Nov 21, 2018 at 10:33:18AM +0100, Daniel Vetter wrote:
>On Wed, Nov 21, 2018 at 10:31 AM Daniel Vetter <daniel@ffwll.ch> wrote:
>>
>> On Tue, Nov 13, 2018 at 12:52:14AM -0500, Sasha Levin wrote:
>> > From: "Lee, Shawn C" <shawn.c.lee@intel.com>
>> >
>> > [ Upstream commit 922dceff8dc1fb4dafc9af78139ba65671408103 ]
>> >
>> > BOE panel (ID: 0x0771) that reports "DFP 1.x compliant TMDS".
>> > But it's 6bpc panel only instead of 8 bpc.
>> >
>> > Add panel ID to edid quirk list and set 6 bpc as default to
>> > work around this issue.
>> >
>> > Cc: Jani Nikula <jani.nikula@intel.com>
>> > Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
>> > Cc: Gustavo Padovan <gustavo@padovan.org>
>> > Cc: Cooper Chiou <cooper.chiou@intel.com>
>> > Signed-off-by: Lee, Shawn C <shawn.c.lee@intel.com>>
>> > Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
>> > Link: https://patchwork.freedesktop.org/patch/msgid/1540792173-7288-1-git-send-email-shawn.c.lee@intel.com
>> > Signed-off-by: Sasha Levin <sashal@kernel.org>
>>
>> Given that I'm not a fan of AUTOSEL at all: This one here is correctly
>> cherry-picked for stable, ack.
>
>An idea that just crossed my mind: Could we integrate this into 0day
>and suggest cc: stable before the patch even gets merged? Or is the
>heuristics not good enough for that kind of automation?

Yes! I've actually tried it before but it seemed that the response rate
was quite low (even for commits that are obviously stable material) so I
turned it off to avoid spamming too much.

If you'd like to be the guinea pig for this, I could enable it for
drivers/gpu/drm/i915/ which I currently completely ignore. If at any
point you want it back off that's easy to do.

If this works well we can extend it to more subsystems where maintainers
might find it useful.

      reply	other threads:[~2018-11-22 15:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20181113055223.79060-1-sashal@kernel.org>
2018-11-13  5:52 ` [PATCH AUTOSEL 4.9 08/17] drm/edid: Add 6 bpc quirk for BOE panel Sasha Levin
2018-11-21  9:31   ` Daniel Vetter
2018-11-21  9:33     ` Daniel Vetter
2018-11-22 15:53       ` Sasha Levin [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=20181122155307.GA6667@sasha-vm \
    --to=sashal@kernel.org \
    --cc=Lee@phenom.ffwll.local \
    --cc=cooper.chiou@intel.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gustavo@padovan.org \
    --cc=jani.nikula@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=shawn.c.lee@intel.com \
    --cc=stable@vger.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;
as well as URLs for NNTP newsgroup(s).