Received: by 2002:ac0:e350:0:0:0:0:0 with SMTP id g16csp241628imn; Thu, 4 Aug 2022 04:15:53 -0700 (PDT) X-Google-Smtp-Source: AA6agR5yeOB/dOo1Ts/yor4wEExGNc2MEQC91H8V7Uk6d5bXuAJQMuFIYvceunUNtiv+gRUVhQA4 X-Received: by 2002:a05:6a00:1343:b0:52e:8174:fc37 with SMTP id k3-20020a056a00134300b0052e8174fc37mr1303575pfu.32.1659611753636; Thu, 04 Aug 2022 04:15:53 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1659611753; cv=none; d=google.com; s=arc-20160816; b=Kx1JDLLO+pB+v4q2KoQ4Q16ytKqM2W0CAGBTudWWbQNLLC5bMI9xjYTSDFnUbVHomG 1ICfNKOJgTFPDsz2PnbZAbGtsDwgx9Y9ndsDxfwOM4AxoDltnLp7XiGEOgrUpxyGp3on a2B2eoeOVg5H545yp1jO4w4/9LCLYmIJpUTpzXrL9/1JUDw5FJ/jPtjEA57BOUM/OnX3 AVvtczCWjxHAp9KtgV0nllZzFaMhDRLFHPBTuqx6Yr5nDXsksfuZSKvhdh3GQJyxxzFZ T+IjYhQTSHWEQ5GVnkUzhgf/joVGc3/9KxjXXZUzVgQdbjw/Vke0vISoLKbIYvNMmZ33 C/OQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-transfer-encoding :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=aLndu7eWl0iNQ51C+ugoQlTMY0CsVI+VuYT41z9kpBI=; b=x/c7JI1t+kWf7a6ZMT3QL4Y2L03lWCkrpYZAxoxHduGHd73kpG2uUWDCS7r73lsPq6 Ue9L6VMFsdeqDzVHUpcX5JK+Hp6e0+TXQkGTuBK75RZ1x1S1P8pBI+oBTAzSZBMdjSpT MHCanj+ivjTlqHXfHQ8rDA3fcNmzKCmdhDftt3/dIG3VJkDMXoQ1Dy7kKV1rzFyd9MPS Ks/APkuHFdX9QCqQtowL2h98P8DCLP2hI5cy4aX2JAJpBEMSM+Lr01/xpVUgZIwLhEi1 jnDK00RWFltPVhSaf0iW/VgMM9RT/KMKAAG9LfXD//HJWnvkMMMGqhj0IMnGSbFe81NF 9HpA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id m14-20020a056a00080e00b0052d4f3e07a2si688035pfk.21.2022.08.04.04.15.39; Thu, 04 Aug 2022 04:15:53 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S239066AbiHDK2R (ORCPT + 99 others); Thu, 4 Aug 2022 06:28:17 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:59030 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236209AbiHDK2O (ORCPT ); Thu, 4 Aug 2022 06:28:14 -0400 Received: from metis.ext.pengutronix.de (metis.ext.pengutronix.de [IPv6:2001:67c:670:201:290:27ff:fe1d:cc33]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id DC880422FA for ; Thu, 4 Aug 2022 03:28:13 -0700 (PDT) Received: from ptx.hi.pengutronix.de ([2001:67c:670:100:1d::c0]) by metis.ext.pengutronix.de with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oJY59-0003UY-H3; Thu, 04 Aug 2022 12:27:59 +0200 Received: from mfe by ptx.hi.pengutronix.de with local (Exim 4.92) (envelope-from ) id 1oJY57-0001fs-D1; Thu, 04 Aug 2022 12:27:57 +0200 Date: Thu, 4 Aug 2022 12:27:57 +0200 From: Marco Felsch To: Dave Stevenson Cc: Adam Ford , Neil Armstrong , David Airlie , dri-devel , Laurent Pinchart , Andrzej Hajda , Marek Szyprowski , Marek Vasut , Jernej Skrabec , Jagan Teki , robert.chiras@nxp.com, laurentiu.palcu@nxp.com, NXP Linux Team , Jonas Karlman , Sascha Hauer , arm-soc , Linux Kernel Mailing List , Robert Foss , Pengutronix Kernel Team , Shawn Guo Subject: Re: imx8mm lcdif->dsi->adv7535 no video, no errors Message-ID: <20220804102757.pc7hljonea43ytwg@pengutronix.de> References: <20220802080820.jyf3tfpgcj3pvbtp@pengutronix.de> <20220803062024.vn7awasmifkp5xow@pengutronix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: NeoMutt/20180716 X-SA-Exim-Connect-IP: 2001:67c:670:100:1d::c0 X-SA-Exim-Mail-From: mfe@pengutronix.de X-SA-Exim-Scanned: No (on metis.ext.pengutronix.de); SAEximRunCond expanded to false X-PTX-Original-Recipient: linux-kernel@vger.kernel.org X-Spam-Status: No, score=-4.2 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED, SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 22-08-03, Dave Stevenson wrote: > On Wed, 3 Aug 2022 at 13:31, Adam Ford wrote: ... > > Mine also states the DSI source needs to provide correct video timing > > with start and stop sync packets. > > > > If I remember correctly, it seemed like Marek V wanted the hard coded > > samsung,burst-clock-frequency to go away so the clock frequency could > > be set dynamically. > > I've never worked with Exynos or imx8, but my view would be that > samsung,burst-clock-frequency should only be used if > MIPI_DSI_MODE_VIDEO_BURST is set in the mode_flags (it isn't for > adv7533/5). Some notes on that. The samsung,burst-clock-frequency is the hs-bit-clock-rate which is twice the dsi-clock-rate. This has nothing to do with the MIPI_DSI_MODE_VIDEO_BURST. > Without that flag the DSI link frequency should be running at the rate > defined by the mode clock, number of lanes, bpp, etc. IMHO the DSI link have only to guarantee the bandwidth is sufficient for the mode. > From the DSI spec (v 1.1 section 8.11.1): > "Non-Burst Mode with Sync Pulses – enables the peripheral to > accurately reconstruct original video timing, including sync pulse > widths." > "RGB pixel packets are time-compressed, leaving more time during a > scan line for LP mode (saving power) or for multiplexing other > transmissions onto the DSI link." > How can the peripheral reconstruct the video timing off a quirky link frequency? If the ADV couldn't reconstruct the sync signals, then we should not get any mode working but we get the 1080P mode working. > Unless the Exynos DSIM_CONFIG_REG register bit DSIM_BURST_MODE [1] > reconfigures the clock setup of the DSI block, then I don't see how > the Exynos driver can follow the DSI spec in that regard. Why do you think that the Exynos driver isn't following the spec? We configure the host into video mode with sync signals which is working for the 1080P mode. Regards, Marco