Received: by 2002:a05:6358:11c7:b0:104:8066:f915 with SMTP id i7csp1016183rwl; Wed, 12 Apr 2023 07:14:55 -0700 (PDT) X-Google-Smtp-Source: AKy350bh1fh72DZrnYTGHnvZoX8jdL52C1hS35G8c5E1ksifq024oH9qldRHO+KMNOSZWQiqCe2J X-Received: by 2002:a17:906:3958:b0:94a:4ec9:cf27 with SMTP id g24-20020a170906395800b0094a4ec9cf27mr10510639eje.20.1681308894614; Wed, 12 Apr 2023 07:14:54 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1681308894; cv=none; d=google.com; s=arc-20160816; b=ZR68G1YvJDsmA0d9mOqpPCU0x7gV5F1ptUxEiu7sMfnBGTgZEj9RZ6BUtjCHFZjIrp UJ4bSR8OB+b2VWw7wmXoas6+xaM5oFwvXRweC6tWlhMcgE3yHIDRr1gqk/kFSdhMhfDL W+KCvk5ajr5l4ZlE9vQJSC1ffqupn9z4x0NtPNo/qieU0FfGhBrF43Y5cjmfmYIwQE5H C6Eo+5fM+QyHaSUv4D96EjrtaEGUhZuK0vYPZn9Z3Og2WOJOJrf9G1MjVE5cNs43InOr ia8Els8sJScUST/29kTIp/4zZM1GxMP1bDrYLQWyS7FoyY+c6blcijDQXeVwEOE4M2AE bF2w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:feedback-id :dkim-signature:dkim-signature; bh=+6c91CjmYIxtUqQXd3hOvEtB9DdbEY6oIma7Y8N/Mjo=; b=sPRlxw7qKrxxGVzRy3BFe03osEDBZFFtQz2KnTSJ301CIKALxDvmPgSbKhfE7q5WMq 7LpII0hlQDqbB64bl3Nz2YYFLYgUtVjsph27+ngR1B/dCZES7xJB1UwHGyGpU47Q90f/ w6eHVZNSzXIG68NI1/BLwcMXmIp8zJ7Ut9IXc+4uZGRejmY2+ikGqF0H6G7FLPxv3pof IsDaSeUmj19Ph1GS9Kfl3wUi2nuKQR2CTYyxB/rGXCaeJcRyFHkp8oSbenH6SgTO1LEA 5EfDDPCYSoc9Ud10xDJHVGYlyfUwPbaGz9bfw8TnH4/H5FMyzKu2HMxjMn5c+WJgb0zx yTlA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@cerno.tech header.s=fm2 header.b=ib7pWYB1; dkim=pass header.i=@messagingengine.com header.s=fm3 header.b=KJ7yfzAf; 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=NONE dis=NONE) header.from=cerno.tech Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id s27-20020a170906061b00b009476a8cb01esi1058291ejb.654.2023.04.12.07.14.30; Wed, 12 Apr 2023 07:14:54 -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=@cerno.tech header.s=fm2 header.b=ib7pWYB1; dkim=pass header.i=@messagingengine.com header.s=fm3 header.b=KJ7yfzAf; 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=NONE dis=NONE) header.from=cerno.tech Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230409AbjDLOKB (ORCPT + 99 others); Wed, 12 Apr 2023 10:10:01 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40508 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229536AbjDLOKA (ORCPT ); Wed, 12 Apr 2023 10:10:00 -0400 Received: from new2-smtp.messagingengine.com (new2-smtp.messagingengine.com [66.111.4.224]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id F1F84E49 for ; Wed, 12 Apr 2023 07:09:58 -0700 (PDT) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailnew.nyi.internal (Postfix) with ESMTP id 68600582A85; Wed, 12 Apr 2023 10:09:57 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Wed, 12 Apr 2023 10:09:57 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cerno.tech; h=cc :cc:content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:sender :subject:subject:to:to; s=fm2; t=1681308597; x=1681315797; bh=+6 c91CjmYIxtUqQXd3hOvEtB9DdbEY6oIma7Y8N/Mjo=; b=ib7pWYB1n6aJSdrpJQ fY5o9y+RlaIb0qfrmsZSmlILn6qzjK9sSETdoq0/hb36Y4zhDs7vUX8e/m3CX8cP aiRH2h0Bv0MYH4qsODXwgzQYDD2p5a7gZQvi5GMY2MCHoSGiN8GZ5f78iOohcV6J vgAsGGKmlt0Dsl3YFMGXHlUnjA1XTET8FHRQ06Z87e4JInI2XyMbXEi2l6Kfszzd DLR88XpeOdzXVuqOWfJWsTnWRH8vCvYdVQ5eXC9MoNsDrinFg7GwnyCBxkTu7BN1 hWGYHHcprJJeYU7A9R5MfecL+sfwZjCV3iMo3V3JmyrAhjEsOfMmL93ohOCj1okf JzkA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; t=1681308597; x=1681315797; bh=+6c91CjmYIxtU qQXd3hOvEtB9DdbEY6oIma7Y8N/Mjo=; b=KJ7yfzAf7FGIldi78fa7VdpD4gtBS +wv58kmjpp1ujCZD9slNbsIFzGgIAll3f6UpPJ7KfsngSI+3WSBqC6xK9enuFBVl 3pq37O8Uch5OJokDOImpb0TfUwgZzSBVm47bzA29iMVenfXZ1R/AZLKA/dlpwiqP f/S79HmOwJAZ0IWVIyND9NU2rL/LCmyB8YfqIkhFP4qDLtFs0b8uIGouvJ1sVyLe PBGZN/v+mdJXlEWE4dY1AptiSEBeYABovZijA4/PtVOV9A9zEtXtdRSfVD98a/3g 6vJShHBPDrIOvIrkWQG2p4wEwg3uQvPruFkIMzeWqHmxBUsUgbUbGMXSA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrvdekiedgjeehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvfevuffkfhggtggujgesghdtsfertddtvdenucfhrhhomhepofgrgihi mhgvucftihhprghrugcuoehmrgigihhmvgestggvrhhnohdrthgvtghhqeenucggtffrrg htthgvrhhnpeeuveduheeutdekvefgudevjeeufedvvdevhfejgfelgfdtkeevueegteek gfelfeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpe hmrgigihhmvgestggvrhhnohdrthgvtghh X-ME-Proxy: Feedback-ID: i8771445c:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 12 Apr 2023 10:09:56 -0400 (EDT) Date: Wed, 12 Apr 2023 16:09:54 +0200 From: Maxime Ripard To: Roman Beranek Cc: Frank Oltmanns , Chen-Yu Tsai , David Airlie , Daniel Vetter , Jernej Skrabec , Samuel Holland , dri-devel@lists.freedesktop.org, linux-arm-kernel@lists.infradead.org, linux-sunxi@lists.linux.dev, linux-kernel@vger.kernel.org Subject: Re: [PATCH] drm/sun4i: uncouple DSI dotclock divider from TCON0_DCLK_REG Message-ID: References: <20230320161636.24411-1-romanberanek@icloud.com> <87wn356ni4.fsf@oltmanns.dev> <20230327202045.ceeqqwjug4ktxtsf@penduick> <20230329195802.veybo3367zifw77n@penduick> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="gw23oqhzikhjtwgb" Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-2.8 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS, SPF_PASS,URIBL_BLOCKED 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 --gw23oqhzikhjtwgb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Apr 12, 2023 at 09:14:59AM +0200, Roman Beranek wrote: > On Wed Apr 5, 2023 at 5:03 PM CEST, Maxime Ripard wrote: > > On Wed, Apr 05, 2023 at 02:34:11PM +0200, Roman Beranek wrote: > > > It turns out however that the new dclk rates can't be set exactly as > > > requested without touching pll-video0*, tcon0 now therefore gets > > > reparented from pll-mipi to pll-video0-2x which, as it further turns > > > out, breaks DSI. While simply forbidding the video0-2x mux option see= ms > > > to me as the right way to go because there's not much use for it with > > > non-DSI interfaces either besides the opportunity to power pll-mipi > > > down, I'd like to run by you first. > > > > Sounds reasonable >=20 > Okay, I'm unsure of how to denote that in the code however. Should I > just comment the parent out of the table and put an explanation in > a comment nearby? Or just erase it? I couldn't find an applicable > precedent. I think that forcing the parent at boot, and adding the CLK_SET_RATE_NOREPARENT flag should be enough. > > > * As pll-mipi doesn't have CLK_SET_RATE_PARENT flag set, pll-video0 > > > retains its boot-time rate of 294 MHz set by sunxi-dw-hdmi driver > > > in u-boot. Why 294 MHz (as opposed to the default rate of 297 MHz)? > > > The driver actually asks for 297 MHz, clock_set_pll3 rounds it to > > > 294 MHz though because it limits itself to 6 MHz steps. > > > > We could also address that though >=20 > Should I include it in v2 of the series, or leave it for later? I guess you can include it into this one too Maxime --gw23oqhzikhjtwgb Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEABYKAB0WIQRcEzekXsqa64kGDp7j7w1vZxhRxQUCZDa7sgAKCRDj7w1vZxhR xcbdAQDlABOUSRin2TeBWh2nNqjI2tuMlU0bJZQjxFS9a+mQiQEAv5twOP7R+ugi y49VRW9d7AF34brzpVy7yy+Tzffp1A8= =0sQH -----END PGP SIGNATURE----- --gw23oqhzikhjtwgb--