Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752064AbbFSBcx (ORCPT ); Thu, 18 Jun 2015 21:32:53 -0400 Received: from regular2.263xmail.com ([211.157.152.4]:45202 "EHLO regular2.263xmail.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751818AbbFSBcs (ORCPT ); Thu, 18 Jun 2015 21:32:48 -0400 X-263anti-spam: KSV:0; X-MAIL-GRAY: 0 X-MAIL-DELIVERY: 1 X-KSVirus-check: 0 X-ABS-CHECKED: 4 X-ADDR-CHECKED: 0 X-RL-SENDER: ykk@rock-chips.com X-FST-TO: linux-kernel@vger.kernel.org X-SENDER-IP: 191.101.57.22 X-LOGIN-NAME: ykk@rock-chips.com X-UNIQUE-TAG: <8face1090113026e15b36f11446d843b> X-ATTACHMENT-NUM: 0 X-DNS-TYPE: 0 Subject: Re: [PATCH] drm: bridge/dw_hdmi: Filter modes > 165MHz for DVI To: Doug Anderson , Russell King - ARM Linux References: <1434582847-713-1-git-send-email-dianders@chromium.org> <20150617233040.GE7557@n2100.arm.linux.org.uk> <20150618085335.GF7557@n2100.arm.linux.org.uk> <20150618155545.GQ7557@n2100.arm.linux.org.uk> Cc: Philipp Zabel , Thierry Reding , Heiko Stuebner , David Airlie , Andy Yan , Fabio Estevam , "dri-devel@lists.freedesktop.org" , "linux-kernel@vger.kernel.org" From: Yakir Yang Message-ID: <55837105.2060409@rock-chips.com> Date: Fri, 19 Jun 2015 09:31:49 +0800 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.0.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3062 Lines: 74 Doug & Russell, 在 2015/6/19 0:10, Doug Anderson 写道: > Russell, > > On Thu, Jun 18, 2015 at 8:55 AM, Russell King - ARM Linux > wrote: >>> Perhaps you can try >> Something like that needs to be done, but let's get rid of the mdvi >> thing in struct hdmi_vmode - it doesn't belong there, it isn't part >> of the currently set video mode, but becomes a property of the >> connected sink. >> >> I'd also prefer it to be called "is_dvi_sink", especially as its >> function is changing from "is it a CEA mode" to "is the attached >> device a DVI sink". >> >> Even better would be to call it "is_hdmi_sink" to maintain positive >> logic with single-negation where required, rather than double- >> negation in places. > Yakir: sounds like you now have some feedback on your patch now. > Perhaps you can spin it with Russell's feedback? > > When you send it next, please make sure you include Russell in the > "To" line. Based at looking at who committed things to dw_hdmi in the > past, I've been sending my patches "To": > Philipp Zabel > Russell King > Thierry Reding > > ...so perhaps that would be good for you to do, too? Okay, thanks for your remind. >>> I am nowhere near an HDMI expert. If you have a better suggestion >>> then I'm more than happy for you to post it and drop my patch. In my >>> non-expert opinion, it would seem awfully strange for an AV receiver >>> to modify the EDID though unless it was actively interpreting the >>> signal and generating a whole new signal on the other end. In any >>> case, perhaps you can find such a device and that will give insight to >>> how we should deal with it. Until such a device is found, it seems >>> fruitless to speculate. >> Neither am I, but I have had the ability to do some testing with AV >> receivers in the path of a HDMI device, and I've seen how they behave. >> (I made copious notes on this, which I intend to publish when I have >> a round tuit.) Unfortunately, I have no DVI devices to test with, >> and DVI devices are a dying breed - most monitors today come with >> HDMI sockets instead. > Ah, OK. Have you seen any that specifically confuse the DVI vs. HDMI bits? > > I still have copious DVI devices around, personally. I could have > sworn that supporting "older hardware" was actually pretty important > in Linux. ...and I can still buy plenty of DVI devices out there. > > >> That's a shame... I'm not inclined to Ack it as-is - and I'd also like >> to see Yakir's patch reworked as I mentioned above. > Perhaps when Yakir spins his series he can include a patch like mine > in it. It doesn't make sense for me to re-spin it until his is > resolved. I will rebase on russell series and re-send my patch today. - Yakir > -Doug > > > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/