Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp186796ybi; Thu, 13 Jun 2019 14:02:37 -0700 (PDT) X-Google-Smtp-Source: APXvYqwRB5hCwjjDqZEJcuLu7FYIgWS36tKucGyoKXGzGmjINY1cuViNZziYnb754nEcfW/z7EUl X-Received: by 2002:a17:902:7295:: with SMTP id d21mr73388551pll.299.1560459757663; Thu, 13 Jun 2019 14:02:37 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1560459757; cv=none; d=google.com; s=arc-20160816; b=0c36dMQ3eQMaki4aaZgvfSV4fpehiXX07v+1GA5WYNvJj7TnaD5DOx2StbQEI0eoqL of3TF6ljdKvBSYtOeokF1e91bPrXuTRnnvShRLvvhq3KqfCU5EKcSyEye6W+xYWHkDB0 omzPQUrz3AwQovEGEkqMb9DUQP+4pJXGMcvaZepDaT4aJCewB29V0GNPhpuQfK/acfDH j93MPDG8kgRjMINp+g+YGhMv/UozF2Ag0ZP45lvoIHVudSA5Gktf0v5voSEqrMfFG7Ze jqLcJGGSnCtlP7e85a7qjWIIIx4NzDIjMpQzan/T5Su6SFEomH6bcXDCGUoZKLaSmpGs ti5w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=ANvjNrcE6QQq73dnlL+mZyHS0xmMxjzetcJMdK2W1jQ=; b=hQb0O+8FoL1CNDIuuL+HXyYtQBW7aV7OCbg2utLmis1v1n7AlxrLOgkdI38dwW3vAh cT7meoYkzcNTGmZj+DXLuKmccZ75+6PeE8QHqkiK6cymMwiA3pxvMIAb5F0KRCwB6Abt u72I3nHtnQXyw8wSAofmapaQMvuI8CJqVUCJnCSyAXxGRR3effuAEHbm9epKuRkb7ZUv QZqBzysXPHGvYqNb7c89f23kr4l0jdKMXWdg4N7quOgwA0h3GHtzH8mAXStVSeFIXbRn kW95eHy/4PT6E9a7tLyux6++Or4vd8x4x/ziyHWrTWp/kKK2qj1fZMDzJorGZldthtni B2gQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=CXaGzb14; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id o26si592445pgv.311.2019.06.13.14.02.23; Thu, 13 Jun 2019 14:02:37 -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; dkim=pass header.i=@chromium.org header.s=google header.b=CXaGzb14; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730320AbfFMVAj (ORCPT + 99 others); Thu, 13 Jun 2019 17:00:39 -0400 Received: from mail-ua1-f68.google.com ([209.85.222.68]:42589 "EHLO mail-ua1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730173AbfFMVAj (ORCPT ); Thu, 13 Jun 2019 17:00:39 -0400 Received: by mail-ua1-f68.google.com with SMTP id a97so84626uaa.9 for ; Thu, 13 Jun 2019 14:00:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ANvjNrcE6QQq73dnlL+mZyHS0xmMxjzetcJMdK2W1jQ=; b=CXaGzb143DooLWuwJbQV6crBWgqXBWrbK4+440tGPl1wKAyG8snXREUHW1cU4JZmsm FByj4Hbh/N7MYr7J1mbnB5t09OsVMCB1N4NOkq7QEs9SD5IFkvvlk2kM4aqXonR4pgZ7 0hbbny8wK43pD9gCj8eWhwnzsqv2xTicEtM7Y= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ANvjNrcE6QQq73dnlL+mZyHS0xmMxjzetcJMdK2W1jQ=; b=Ld+Luvcz48V1iRV2FmOy9lug7Sak5yVU8uWVCuRu24dST1WM09wKxh1maceIB5FnPv iLYE+34GVC5Y5feyGc78lxm1bluh2LzZfe7oGIWXQy0ZRIb8uUOSnS/SzwmI+Ng212pQ VpOI6yLYvWLHnIgKb3aaCkkNCVZ2+wfZitSOtmCbD6LK5b5LLCZDcp3C62sgTyClhtnI 5fAlGphZ6uB589wsY1j0AxGXe5xs00pw8JGjY6OWJIQE94DJe/bIKRmU8fzgZtkqn6PO +53SgYLhgN3z8sprEV/XjPIt4Ya79exSwsvWynQEzTPEykvPo3yJ1jg7Q9Muq0GJoE8M eVFQ== X-Gm-Message-State: APjAAAWfXlaqOZ1tDVRVVtJuboQFDh/rzNNBWN+RFoD1g6cP5y/+CxeT PRikXWLKq2bZl5r4cKa03nLoWKbHjby0engfjhNcpeJc2V0= X-Received: by 2002:ab0:3d2:: with SMTP id 76mr17494821uau.12.1560459637540; Thu, 13 Jun 2019 14:00:37 -0700 (PDT) MIME-Version: 1.0 References: <20190611040350.90064-1-dbasehore@chromium.org> <20190611040350.90064-3-dbasehore@chromium.org> In-Reply-To: From: "dbasehore ." Date: Thu, 13 Jun 2019 14:00:26 -0700 Message-ID: Subject: Re: [PATCH 2/5] dt-bindings: display/panel: Expand rotation documentation To: Rob Herring Cc: "linux-kernel@vger.kernel.org" , Thierry Reding , Sam Ravnborg , David Airlie , Daniel Vetter , Mark Rutland , Maarten Lankhorst , Maxime Ripard , Sean Paul , Jani Nikula , Joonas Lahtinen , Rodrigo Vivi , CK Hu , Philipp Zabel , Matthias Brugger , dri-devel , devicetree@vger.kernel.org, Intel Graphics , "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" , "moderated list:ARM/Mediatek SoC support" Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jun 13, 2019 at 5:52 AM Rob Herring wrote: > > On Tue, Jun 11, 2019 at 4:02 PM dbasehore . wrote: > > > > On Tue, Jun 11, 2019 at 8:25 AM Rob Herring wrote: > > > > > > On Mon, Jun 10, 2019 at 10:03 PM Derek Basehore wrote: > > > > > > > > This adds to the rotation documentation to explain how drivers should > > > > use the property and gives an example of the property in a devicetree > > > > node. > > > > > > > > Signed-off-by: Derek Basehore > > > > --- > > > > .../bindings/display/panel/panel.txt | 32 +++++++++++++++++++ > > > > 1 file changed, 32 insertions(+) > > > > > > > > diff --git a/Documentation/devicetree/bindings/display/panel/panel.txt b/Documentation/devicetree/bindings/display/panel/panel.txt > > > > index e2e6867852b8..f35d62d933fc 100644 > > > > --- a/Documentation/devicetree/bindings/display/panel/panel.txt > > > > +++ b/Documentation/devicetree/bindings/display/panel/panel.txt > > > > @@ -2,3 +2,35 @@ Common display properties > > > > ------------------------- > > > > > > > > - rotation: Display rotation in degrees counter clockwise (0,90,180,270) > > > > + > > > > +Property read from the device tree using of of_drm_get_panel_orientation > > > > > > Don't put kernel specifics into bindings. > > > > Will remove that. I'll clean up the documentation to indicate that > > this binding creates a panel orientation property unless the rotation > > is handled in the Timing Controller on the panel if that sounds fine. > > Even if the timing ctrlr handles it, don't you still need to know what > the native orientation is? Not really. For all intents and purposes, the orientation of the panel has changed. > > > > > + > > > > +The panel driver may apply the rotation at the TCON level, which will > > > > > > What's TCON? Something Mediatek specific IIRC. > > > > The TCON is the Timing controller, which is on the panel. Every panel > > has one. I'll add to the doc that the TCON is in the panel, etc. > > > > > > > > > +make the panel look like it isn't rotated to the kernel and any other > > > > +software. > > > > + > > > > +If not, a panel orientation property should be added through the SoC > > > > +vendor DRM code using the drm_connector_init_panel_orientation_property > > > > +function. > > > > > > The 'rotation' property should be defined purely based on how the > > > panel is mounted relative to a device's orientation. If the display > > > pipeline has some ability to handle rotation, that's a feature of the > > > display pipeline and not the panel. > > > > This is how the panel orientation property is already handled in the > > kernel. See drivers/gpu/drm/i915/vlv_dsi.c for more details. > > The point is your description is all about the kernel. This is a > binding which is not kernel specific. Ah, I see. I thought you were saying what the implementation should be. > > > > > + > > > > +Example: > > > > > > This file is a collection of common properties. It shouldn't have an > > > example especially as this example is mostly non-common properties. > > > > Just copied one of our DTS entries that uses the property. I'll remove > > everything under compatible except for rotation and status. > > Just remove the example or add what you want to the "boe,himax8279d8p" > binding doc. We are moving towards examples being compiled and > validated, so incomplete ones won't work. Ok, will do. > > Rob Thanks for the quick reviews.