Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp777237rwd; Wed, 7 Jun 2023 06:51:31 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ7mOGJ/xxIiO/+CJmeKQvuaVV2baIoz/qVBL0l5aXbOXl9ANbzdMf50olD67Fm9D/jm7T1Z X-Received: by 2002:a05:6808:1d8:b0:39a:bd0e:449 with SMTP id x24-20020a05680801d800b0039abd0e0449mr5450611oic.26.1686145891104; Wed, 07 Jun 2023 06:51:31 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1686145891; cv=none; d=google.com; s=arc-20160816; b=RyWysytEfwPDErgTFC859Du6/Pi/rewN7J6TUPMKi7dVgT/ttZuaq9fNMZ9W0Z8SkW aH6wkyXkuohMTuR/jtodM1OPffPN7eqtgxJWHOPpNcjSfkS/GqWCRTl+ESSuoycKmUFF fw3f8vfOlkkCfYNu8pIqAOQLOw4mXEEpCfqKfLkB35sDaYSTzX1dGYoevryvvxOpDSxy SSNvtnBIc0nK1BJd0uXw10xDypx91HJ95C9ri14DWFtPKP/MQWIgwk9VDLA+cHSrMAt4 400B+aR8Nwp8P3h15bfSsxnB2wG+vT6Mq+G4hr10tG3G3jYyKDWhGlRdXoK+gq1ZPwct 06Gw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:cc:to:subject :message-id:date:from:in-reply-to:references:mime-version :dkim-signature; bh=96K7mim4wjsUFSyoNjyPRj89jwQvp4OefH01N5hbH5I=; b=LmiKVCgP1TUU7Vh4oa02izYXY0w3ROSmUA50smdd7RV5rG+s4t6HnFp+uayvAAOu7X 61ubVWhCZc27fJJpJCEj9ZNsPzQkIrmFaJ5WHiXM5jhw435ZEUkHJdBHFB9pcizxS7y4 uKe+GP92ZA+jRS5hthH0iT/OrMOM2fDva4A25Vk49blSD7sinJRrTwzVCaWI+wDT7i25 XnHfQMmDDVY+EtaqcT1cKJtUYnxrIf7/Um0D8f0BVQCg2MoZUimduJSK5gYgldbmZlBj w1Zv4Ahu9vok/M7H2wvc1kFm7r7CxAahKXcCcQEoqbfpklGOl4n1RVkVs6XaU7rC05EU Ae+Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20221208 header.b=kKmqUbHh; 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; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id kk1-20020a17090b4a0100b00256a98800absi1133122pjb.186.2023.06.07.06.51.17; Wed, 07 Jun 2023 06:51:31 -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; dkim=pass header.i=@gmail.com header.s=20221208 header.b=kKmqUbHh; 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; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S240680AbjFGN1x (ORCPT + 99 others); Wed, 7 Jun 2023 09:27:53 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:51210 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235032AbjFGN1v (ORCPT ); Wed, 7 Jun 2023 09:27:51 -0400 Received: from mail-oi1-x235.google.com (mail-oi1-x235.google.com [IPv6:2607:f8b0:4864:20::235]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A88851732; Wed, 7 Jun 2023 06:27:49 -0700 (PDT) Received: by mail-oi1-x235.google.com with SMTP id 5614622812f47-39a50fcc719so4979069b6e.2; Wed, 07 Jun 2023 06:27:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1686144469; x=1688736469; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=96K7mim4wjsUFSyoNjyPRj89jwQvp4OefH01N5hbH5I=; b=kKmqUbHhKvKv4wuODjZBcxBIOinIDVcbAF01ceisdhnKQA79OBhnjwwfC4LUDuxvvL QRHcLkUnUsnkt8lWRCZGxshGXRe5rC7MKUSiTyh0m/h9+IHeveHim1dVe+eRE6UybS62 s4R7VX4U8/vdCKXJKXOY8Xlmw3nCm15dI4vQlOnvwvCreBCJSqZwFjkhPS3LAdXALnLm rHT1EUk5JgDKaYdTe5RD44EIqnmnZd57XEdqdy5ApO94SoIs7Y8jWgf863APYPgwmukn RNZS5y4DuvLMYB7oEXcYxyIUc6TFbL02K9yeRQ65k7v7AfwsY13sb7ad3R+cnIfz8IGy 0L5Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1686144469; x=1688736469; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=96K7mim4wjsUFSyoNjyPRj89jwQvp4OefH01N5hbH5I=; b=NsFeCI1xaycoXmyGGnDUrBLHoID/ukUNHBWmbcAxdkjv0xhFB8TUml4Sr9CpF2y0fW zYSJWfffoyU66WVOMT9lxRLkieKRRs8/w9WpdSWBInzg1NWPN8i0wYv1N76lsv1PAYSl 0IULA0lF995mFJFxgmkBd7cyL/wF2hHp89elztcpQF6eW9tWY0/6Je/tDUxLyFXse8XR 3+HMDIVPEhZm/RfyDsyc2z+JcgZRItyeq2Wa+A0fpJRWMmMoVuFTRziAYGrGKChsXZ57 04JRxdwyNxjPbMzzlN7vk915G6DBH1UfyH9lSCTUW1mUKO9aU86jsTcSKDItsxEK2eZL rV8w== X-Gm-Message-State: AC+VfDxVGG+7MMkNtaK6+Nnt3P/oObnx4Qz7KIBvid4dgUmMdGcaSHd+ PkxV+etlzdyQhZCQODacsWfuxAbesfkrOxEQRmo= X-Received: by 2002:aca:210d:0:b0:398:6008:f460 with SMTP id 13-20020aca210d000000b003986008f460mr5491140oiz.28.1686144468671; Wed, 07 Jun 2023 06:27:48 -0700 (PDT) MIME-Version: 1.0 References: <20230526030559.326566-1-aford173@gmail.com> In-Reply-To: From: Adam Ford Date: Wed, 7 Jun 2023 08:27:37 -0500 Message-ID: Subject: Re: [PATCH V8 0/7] drm: bridge: samsung-dsim: Support variable clocking To: Rasmus Villemoes Cc: dri-devel@lists.freedesktop.org, aford@beaconembedded.com, Inki Dae , Jagan Teki , Marek Szyprowski , Andrzej Hajda , Neil Armstrong , Robert Foss , Laurent Pinchart , Jonas Karlman , Jernej Skrabec , David Airlie , Daniel Vetter , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Marek Vasut , Frieder Schrempf , devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_ENVFROM_END_DIGIT, FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS, T_SCC_BODY_TEXT_LINE 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 Wed, Jun 7, 2023 at 8:15=E2=80=AFAM Rasmus Villemoes wrote: > > On 26/05/2023 05.05, Adam Ford wrote: > > This series fixes the blanking pack size and the PMS calculation. It t= hen > > adds support to allows the DSIM to dynamically DPHY clocks, and support > > non-burst mode while allowing the removal of the hard-coded clock value= s > > for the PLL for imx8m mini/nano/plus, and it allows the removal of the > > burst-clock device tree entry when burst-mode isn't supported by connec= ted > > devices like an HDMI brige. In that event, the HS clock is set to the > > value requested by the bridge chip. > > > > This has been tested on both an i.MX8M Nano and i.MX8M Plus, and should > > work on i.MX8M Mini as well. Marek Szyprowski has tested it on various > > Exynos boards. > > Hi all > > We're testing this on top of v6.4-rc4 on our imx8mp board, which has a > ti-sn65dsi86 DSI -> DisplayPort bridge. We do get an image at > 1920x1200, but the monitor says it's only at 58Hz, and measuring on the > DSI signals does seem to confirm that the update frequency is about 57.7 > or 57.8Hz (it's pretty hard to get a good measurement). It looks like > it's the lines that are too long, by a time that corresponds to about 80 > pixels. But all the frontporch/backporch/hsync values look sane and > completely standard for that resolution. > > Setting samsung,burst-clock-frequency explicitly to something large > enough or letting it be derived from the 154MHz pixel clock makes no > difference. > > Any ideas? What refresh rate are you trying to achieve? It seems like 57.7 or 57.8 is really close to the 58 the Monitor states. I would expect the refresh to be driven by whatever the monitor states it can handle. Have you tried using modetest to see what refresh rates are available? When I was doing this driver work, I would use modetest to determine the connector ID, then use modetest -s :- to display various resolutions and refresh rates. The 8MP shares the video-pll clock with both disp1 and disp2 clocks, and the imx-lcdif driver, which sends the display signals to the DSI, uses the disp clock, so the video-pll needs to be an exact multiple of the pixel clock or the output won't sink. Modetest should also show you the desired pixel clock for a given resolution and refresh. My displays didn't show 19200x1200 as an option, so I wasn't able to test that configuration. adam > > Thanks, > Rasmus >