Received: by 2002:a25:ad19:0:0:0:0:0 with SMTP id y25csp103824ybi; Thu, 11 Jul 2019 15:37:52 -0700 (PDT) X-Google-Smtp-Source: APXvYqwvdIQXI45hbaU9uveCUppc27a9/G5K2a/oKEaiGu/JF2M6jSq6ewKHOljCtmNdsgnlr+AK X-Received: by 2002:a63:7942:: with SMTP id u63mr6681059pgc.399.1562884672105; Thu, 11 Jul 2019 15:37:52 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1562884672; cv=none; d=google.com; s=arc-20160816; b=1J5ARdxEmWowAmdF2KXS+XbAAlsWTBK6H8jsmL13X1f2PHgZKx9EltfT9y85q0eh9t moR76rM9zAaJ2mJgJ05EEExCJx/NABgLIr6D+eU2hn/mnQv70TivBhmsmTvhtonO9EgN zibjH/BzJ5uYpIKlCgwSupMGU0UhAeXkVltE6mN7SfRQ+D/DXSqEIrJKErbL6mqWBRkJ 2seX9MpL+ESlkFBwsBr3yQj7rSxSb9g3IHc8yyBIv6+Xbg7uSHaKS1pxAT99plDf//BS IdLjM69Sx7vH/cpeOAmnnN3FNImM7q2xlEmxnqM2q72+1Uv1xr7chhs52laP+XRF7MQm WacQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from; bh=ctSoMsCzuoAaEngqZNj/hy+w7A8y/j0KVOJ4RKfhsVM=; b=TR0fmk5JgRU+ii20sD+JJoXZMtsH0oFF0SL3JxwF2qX2yKxdtYtXfJYDejIRmO2OlY eYheDYSzePENXnbDHKPzpepTWV9C2ptyPa7Jyluj6SgeTlzVbuYIF2gtObzBs8VJ94V0 7VJH648B8twU0mzaW8WGzpTb5qznmtc81XOBTU9FRsNItHrwjWWCJ9ss2QESeUHampoX 2R2+kqm5ys43wp7cI7qqtC9LGq0vyFOK2y9cJkgKULI50LGwJevEplHvRGg0QabBGjPj Pk69yhSMQO0E8ZPdQps76ZkZOIEWZC44WjOmaJMDKe+UgGZf1XJ7BDX5dbENtFpdOP0f vFsg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id v1si6532903pgi.309.2019.07.11.15.37.33; Thu, 11 Jul 2019 15:37:52 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728549AbfGKVxE convert rfc822-to-8bit (ORCPT + 99 others); Thu, 11 Jul 2019 17:53:04 -0400 Received: from gloria.sntech.de ([185.11.138.130]:36472 "EHLO gloria.sntech.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726181AbfGKVxD (ORCPT ); Thu, 11 Jul 2019 17:53:03 -0400 Received: from ip5f5a6320.dynamic.kabel-deutschland.de ([95.90.99.32] helo=diego.localnet) by gloria.sntech.de with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1hlgzr-0006th-0q; Thu, 11 Jul 2019 23:52:59 +0200 From: Heiko =?ISO-8859-1?Q?St=FCbner?= To: Douglas Anderson Cc: Thierry Reding , Sean Paul , linux-rockchip@lists.infradead.org, Laurent Pinchart , dri-devel@lists.freedesktop.org, Boris Brezillon , Ezequiel Garcia , Enric =?ISO-8859-1?Q?Balletb=F2?= , Rob Herring , mka@chromium.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, Mark Rutland , linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH v5 6/7] ARM: dts: rockchip: Specify rk3288-veyron-chromebook's display timings Date: Thu, 11 Jul 2019 23:52:58 +0200 Message-ID: <3703486.dL69t9P4Cl@diego> In-Reply-To: <4744731.Gbjux09qzx@diego> References: <20190401171724.215780-1-dianders@chromium.org> <20190401171724.215780-7-dianders@chromium.org> <4744731.Gbjux09qzx@diego> MIME-Version: 1.0 Content-Transfer-Encoding: 8BIT Content-Type: text/plain; charset="iso-8859-1" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Am Donnerstag, 11. Juli 2019, 23:27:44 CEST schrieb Heiko St?bner: > Am Montag, 1. April 2019, 19:17:23 CEST schrieb Douglas Anderson: > > Let's document the display timings that most veyron chromebooks (like > > jaq, jerry, mighty, speedy) have been using out in the field. This > > uses the standard blankings but a slightly slower clock rate, thus > > getting a refresh rate 58.3 Hz. > > > > NOTE: this won't really do anything except cause DRM to properly > > report the refresh rate since vop_crtc_mode_fixup() was rounding the > > pixel clock to 74.25 MHz anyway. Apparently the adjusted rate isn't > > exposed to userspace so it's important that the rate we're trying to > > achieve is mostly right. > > > > For the downstream kernel change related to this see See > > https://crrev.com/c/324558. > > > > NOTE: minnie uses a different panel will be fixed up in a future > > patch, so for now we'll just delete the panel timings there. > > > > Signed-off-by: Douglas Anderson > > applied for 5.3 5.4 obviously [just to not confuse people reading that later]