From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.5 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id D27C4C04AB5 for ; Thu, 6 Jun 2019 09:27:08 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id B071020684 for ; Thu, 6 Jun 2019 09:27:08 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727748AbfFFJ1I (ORCPT ); Thu, 6 Jun 2019 05:27:08 -0400 Received: from asavdk4.altibox.net ([109.247.116.15]:54442 "EHLO asavdk4.altibox.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727664AbfFFJ1I (ORCPT ); Thu, 6 Jun 2019 05:27:08 -0400 Received: from ravnborg.org (unknown [158.248.194.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by asavdk4.altibox.net (Postfix) with ESMTPS id E37BE8051D; Thu, 6 Jun 2019 11:27:04 +0200 (CEST) Date: Thu, 6 Jun 2019 11:27:03 +0200 From: Sam Ravnborg To: Laurent Pinchart Cc: devicetree@vger.kernel.org, Jacopo Mondi , Laurent Pinchart , Kieran Bingham , dri-devel@lists.freedesktop.org, linux-renesas-soc@vger.kernel.org, Jacopo Mondi Subject: Re: [PATCH v3 04/10] dt-bindings: display: renesas: lvds: Add renesas, companion property Message-ID: <20190606092703.GA17442@ravnborg.org> References: <20190528141234.15425-1-laurent.pinchart+renesas@ideasonboard.com> <20190528141234.15425-5-laurent.pinchart+renesas@ideasonboard.com> <20190528163730.GA9610@ravnborg.org> <20190528164916.GA17874@pendragon.ideasonboard.com> <20190528165900.GA10262@ravnborg.org> <20190606075435.GD4931@pendragon.ideasonboard.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190606075435.GD4931@pendragon.ideasonboard.com> User-Agent: Mutt/1.10.1 (2018-07-13) X-CMAE-Score: 0 X-CMAE-Analysis: v=2.3 cv=VcLZwmh9 c=1 sm=1 tr=0 a=UWs3HLbX/2nnQ3s7vZ42gw==:117 a=UWs3HLbX/2nnQ3s7vZ42gw==:17 a=jpOVt7BSZ2e4Z31A5e1TngXxSK0=:19 a=kj9zAlcOel0A:10 a=XN0FE8mA5ZG9_mJlrPoA:9 a=7Zwj6sZBwVKJAoWSPKxL6X1jA+E=:19 a=CjuIK1q_8ugA:10 Sender: linux-renesas-soc-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-renesas-soc@vger.kernel.org Hi Laurent. > > > > The main difference is "when dual-link mode is supported". > > As per my understanding this property is only relevant when the actual > > HW supports / uses dual-link mode. > > So for a board that do not even wire up dual-link, then setting the > > property would be confusing. > > That's not quite correct. The property shall be specified when the SoC > supports dual-link mode (which is the case for the D3 and E3 SoCs only), > regardless of whether the board is wired up in single-link or dual-link > mode. Selection of the mode is performed at runtime by looking at the > requirements of the LVDS sink, not based on the companion property in > DT. The renesas,companion property is thus SoC-specific, but not > board-specific. Thanks for taking your time to clarify this. Sam