From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.0 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_ADSP_ALL, DKIM_SIGNED,DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_PASS,URIBL_BLOCKED,USER_AGENT_NEOMUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 17575C43387 for ; Fri, 18 Jan 2019 15:06:50 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id C9D662086D for ; Fri, 18 Jan 2019 15:06:49 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="q4xR9H9D"; dkim=fail reason="signature verification failed" (2048-bit key) header.d=plaes.org header.i=@plaes.org header.b="kV5juQnN" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org C9D662086D Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=plaes.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender: Content-Transfer-Encoding:Content-Type:Cc:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=KxVnkjbbeRk/RKXqNY8ZIbqSDpytbzwPfaEzsK1By5Y=; b=q4xR9H9DE303OI uajzeBb0sOhKfE+QhCkZ/DBc96okKqjGE9i7SrvF8Xja8FfqwYcCl/2eqUxv2KCp6d7M4V8IqPUJT umYQlQqrq7HDKQtXYC5+Dyv3mMhYc0vxKoSWVIr+vsSbR9ELv0JtN3/HQHm9rStL2ppryIHLCnz39 /RSglBcsdthgdCWT15P3cJRBgkw5zlgnD6Yn9Ilbe2fAuXyWWkaNKa76UnnVFkFNlgj5l0RviUPf5 rMNWWAxHB10j7p6vm23FHqXT62ZdTnC/EG5Q9CEDUyluAL0YHh6puC6KFQsnAzktjwR9Mk+nb5wAJ wCIzOW1GJItz6Cpx5v7Q==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.90_1 #2 (Red Hat Linux)) id 1gkVjJ-0001dG-38; Fri, 18 Jan 2019 15:06:45 +0000 Received: from plaes.org ([188.166.43.21]) by bombadil.infradead.org with esmtps (Exim 4.90_1 #2 (Red Hat Linux)) id 1gkVe2-0006sH-I0 for linux-arm-kernel@lists.infradead.org; Fri, 18 Jan 2019 15:01:25 +0000 Received: from plaes.org (localhost [127.0.0.1]) by plaes.org (Postfix) with ESMTPSA id DE3CF40377; Fri, 18 Jan 2019 14:51:27 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=plaes.org; s=mail; t=1547823087; bh=RqnCgZM+q0oVG4KhvJNi0zRpg3bH0DGsbu3kddUIzWE=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=kV5juQnNa1ZZqoSqwhqL+g8+JBwKsumFFWhZFT6ZFEkomWWzTjypGVAzBwBzLj7U9 wZLjw4lYwf7SWNZeadkFBmtIzOoeQEYxIi3K5+8L4V4+cWjJfD+dh9GqLRVLmf6wzf ZQfe+jbYRItzpqTHybMIlmOBr4hx9Ut43JpC1lnqSriIWIFyWNL2694xdA7tsB030T VC/RkwaDdQg1/ROm8HiVd+jkcnOEs6Gb/UxCXPzbRUIbwK142qwh2JBrYMqDH/1Ayf EBsDQ4Wch3zqTlx5kBHfFR9Af8rM3do8KLzt3Hp/6j+NCsiMmZPHhbdLx0uZ42FmkG PSBcCUZEpVkSg== Date: Fri, 18 Jan 2019 14:51:26 +0000 From: Priit Laes To: Maxime Ripard Subject: Re: [linux-sunxi] Re: HDMI/DVI spurious failure Message-ID: <20190118145126.mpjz5t5hjqqpgzys@plaes.org> References: <20190114132934.rywqqtjarbf6fgcr@plaes.org> <20190115094951.e7jnjpibj5tcp5pz@flea> <20190116075854.o2kme5nxq5kckwem@plaes.org> <20190116192442.qz4xi2ky6axgiyvg@flea> <20190116203516.s7pisy4miaclo63u@plaes.org> <20190117113340.ydszal5c3nlrqr47@flea> <20190118101053.gkxpfymsjzw3ptxf@plaes.org> <20190118140418.m5mliyvddfdfju3v@flea> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20190118140418.m5mliyvddfdfju3v@flea> User-Agent: NeoMutt/20170113 (1.7.2) X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20190118_070119_079470_7D927538 X-CRM114-Status: GOOD ( 28.37 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: linux-arm-kernel@lists.infradead.org, linux-sunxi@googlegroups.com, Chen-Yu Tsai , Jonathan Liu , dri-devel@lists.freedesktop.org Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Fri, Jan 18, 2019 at 03:04:18PM +0100, Maxime Ripard wrote: > On Fri, Jan 18, 2019 at 10:10:53AM +0000, Priit Laes wrote: > > > > > > > It doesn't look related to the clock rate itself, since it doesn't > > > > > > > change between the two cases. However, in one case the DDC clock is > > > > > > > enabled and in the other it's disabled. > > > > > > > > > > > > > > Was it taken at the same time? Maybe you can try with that patch? > > > > > > > http://code.bulix.org/z7jmkm-555344?raw > > > > > > > > > > > > Thanks, after doing ~50+ boots I haven't seen a single failure. > > > > > > > > > > > > Previously I had following failure cases which are now both fixed: > > > > > > > > > > > > a) Linux without u-boot HDMI, where one in every 6-7 boots failed. > > > > > > b) u--boot with hdmi enabled switching to simplefb and then switching > > > > > > to kms, where previously all boots ended up with garbled screen. > > > > > > > > > > So it's not really a fix, but it really looks like the clock is not > > > > > enabled when it should. > > > > > > > > > > Can you describe your test scenario a bit more? What are you doing > > > > > exactly, just booting? When do you start using the display? When did > > > > > you capture the debugfs output that you pasted? > > > > > > > > Display is already connected via HDMI to the board. I don't really > > > > remove it, I just boot the device and let it start Xorg. > > > > Meanwhile I just ssh into the device and capture debugfs output. > > > > See my 3 testing scenarios below. > > > > > > > > Kernel also includes one extra patch to fall back to DDC, in case HPD > > > > fails. Mostly the same I already submitted last November [1]. > > > > > > Do you have the same issue without that patch? > > > > Can't really test this display without this patch and I do not have other > > HDMI/DVI screens. And this issue does not happen with other HDMI displays > > that I have here. > > Can't you just force the monitor to be reported as present? It's not > great and we don't want to merge it, but that would allow you to test > that setup without too many interferences. Baseline is clean u-boot / linux. U-boot does not detect/enable display. 1) Booting Linux with drm.debug=0xe * Linux does not detect/enable display 2) Booting with drm.debug=0xe video=HDMI-A-1:640x480@60e * Linux detects display, but display is garbled, and proper edid data is detected: [snip] pll-video1 0 0 0 327000000 0 0 50000 pll-video1-2x 0 0 0 654000000 0 0 50000 hdmi-tmds 0 0 0 25153846 0 0 50000 hdmi-ddc 0 0 0 89835 0 0 50000 [/snip] 3) Booting with drm.debug=0xe video=HDMI-A-1:640x480@60e And also one extra patch for Linux where HDMI DDC clock marked as critical Linux detects and initializes display properly: [snip] pll-video1 1 1 0 327000000 0 0 50000 pll-video1-2x 1 1 0 654000000 0 0 50000 hdmi-tmds 1 1 0 25153846 0 0 50000 hdmi-ddc 1 1 0 89835 0 0 50000 [/snip] > Maxime > > -- > Maxime Ripard, Bootlin > Embedded Linux and Kernel engineering > https://bootlin.com > > -- > You received this message because you are subscribed to the Google Groups "linux-sunxi" group. > To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscribe@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel