Received: by 2002:a25:ad19:0:0:0:0:0 with SMTP id y25csp75349ybi; Thu, 11 Jul 2019 15:02:28 -0700 (PDT) X-Google-Smtp-Source: APXvYqz2eCBkmf404CuGvZdKTJYes5uYZNN7GkVb2Dw14wxePg6bEXkEsJ+fnXhEbPXPHA6vhWzk X-Received: by 2002:a65:6089:: with SMTP id t9mr6627816pgu.170.1562882548009; Thu, 11 Jul 2019 15:02:28 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1562882548; cv=none; d=google.com; s=arc-20160816; b=kLjSSeXTXtT6oGW8mGfwsxnp2K4G/dC8xKLzqNEcSMgiHYKkOaFQCTuSbaTznev9qs kklVbS3yCaiFQLtOPIIU6NhNk0WKBxKLu7U9RXeEqXTFU9ljaCTjyzYi5o8QYuQw/4A0 cglE+NcKIMjLoTmHkvrkMJ9MncZ1r0V9X+R8zErYLGw+wIjVXCiAk7fkFAItQvfB4PRZ kx0ArMMTYX/u0TTmpp+jREQ5n7IOtMRrcasCZJTkrtjZWChK+xYgKzcZlsclkoiv26ll aHH+EtDUUugng6qeASJG4GGGLWGRNXaBmR2UdlThc/trFRCcSAFlRrTR9vSrbI6WUZd0 vHjw== 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=vlPmi4i67iunyyXCIWMURI9Az6NevUyumThWf/93j2g=; b=AA34frlhinzddYMm2G9HxsRHIIFoIJqZS/M0DytTdhVL442Nz4prir5NwJXVn0Ulzs 8brv/6vepx9yJkQnqsvZePrvJocpz+5OLOAeAjO0q5O7Hj0rNqNGac9oa+EB+YQ3mnoo EMrHPjWtqa1L4jG+tzJfjpM1LTsnvFVSOsrjsdN7oK5sx3/M4b5VJIh7gRYPt2HgXynR GuH2qu2mYY5GDq3YMjMI796B+6lYBeUyTfu0XURUaKACFoHndlewdM1mQWUOQgg3HZVM mUqvGsbbhWPUBJ6chDkoCFq+5+0lCJdd2CfMMrbWZ/M7yQ/FpxlH792ZTHNsZgRHEcOu G1aw== 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 r33si6459163pgm.371.2019.07.11.15.02.00; Thu, 11 Jul 2019 15:02:27 -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 S1728745AbfGKV1w (ORCPT + 99 others); Thu, 11 Jul 2019 17:27:52 -0400 Received: from gloria.sntech.de ([185.11.138.130]:36148 "EHLO gloria.sntech.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726446AbfGKV1w (ORCPT ); Thu, 11 Jul 2019 17:27:52 -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 1hlgbR-0006mP-RG; Thu, 11 Jul 2019 23:27:45 +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:27:44 +0200 Message-ID: <4744731.Gbjux09qzx@diego> In-Reply-To: <20190401171724.215780-7-dianders@chromium.org> References: <20190401171724.215780-1-dianders@chromium.org> <20190401171724.215780-7-dianders@chromium.org> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 Thanks Heiko