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=-12.3 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH, MAILING_LIST_MULTI,NICE_REPLY_A,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 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 A6EADC433ED for ; Thu, 22 Apr 2021 16:22:26 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 71F3361405 for ; Thu, 22 Apr 2021 16:22:26 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236504AbhDVQXA (ORCPT ); Thu, 22 Apr 2021 12:23:00 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:33352 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236236AbhDVQW5 (ORCPT ); Thu, 22 Apr 2021 12:22:57 -0400 Received: from phobos.denx.de (phobos.denx.de [IPv6:2a01:238:438b:c500:173d:9f52:ddab:ee01]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B71AEC06174A for ; Thu, 22 Apr 2021 09:22:21 -0700 (PDT) Received: from [127.0.0.1] (p578adb1c.dip0.t-ipconnect.de [87.138.219.28]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: marex@denx.de) by phobos.denx.de (Postfix) with ESMTPSA id 317EF81D3B; Thu, 22 Apr 2021 18:22:16 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=denx.de; s=phobos-20191101; t=1619108536; bh=4gpqWFxwNYO1QYUDHarnRmhKuH2r+gsiCwEhJJ3k7pg=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=dqhE8JQ6biJwaMcEXLVp2m4iE0QB3oDulwp481eV5+/YNCsaefTF0cJs2O2HP9Hnm xsnfHw+tQxFw0FN5ixdtbaQEjsxLzgwI/6y5SDiErZOWwmExv/vq2TLN2Bzn3x48hj egAT2pdz6mH2RbBGVvrlOq51F5nrLxMIuGuxU1RVZyEqcdiE25U9LyfhaoB4qMGIzd JjGWtlRr6nVQ8pjjKZtrgpFk8OY+S9i1ckq4IuHeDly7b9c1D2RmA69cgCbWl2UDY7 GLfVUdWwtmyzJafRkfCjOWCFYke30A0LyPkDfJGlYQuKsyCvNG+K1nZzROXFReWMMV 1+AtAvX6XHg1w== Subject: Re: [PATCH V2 1/2] dt-bindings: drm/bridge: ti-sn65dsi83: Add TI SN65DSI83 and SN65DSI84 bindings To: Jagan Teki Cc: dri-devel , Claudius Heine , Douglas Anderson , Laurent Pinchart , Linus Walleij , Rob Herring , Sam Ravnborg , Stephen Boyd , devicetree References: <20210421223122.112736-1-marex@denx.de> From: Marek Vasut Message-ID: Date: Thu, 22 Apr 2021 18:22:15 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.9.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamav-milter 0.102.4 at phobos.denx.de X-Virus-Status: Clean Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org On 4/22/21 10:43 AM, Jagan Teki wrote: [...] >> diff --git a/Documentation/devicetree/bindings/display/bridge/ti,sn65dsi83.yaml b/Documentation/devicetree/bindings/display/bridge/ti,sn65dsi83.yaml >> new file mode 100644 >> index 000000000000..42d11b46a1eb >> --- /dev/null >> +++ b/Documentation/devicetree/bindings/display/bridge/ti,sn65dsi83.yaml >> @@ -0,0 +1,134 @@ >> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) >> +%YAML 1.2 >> +--- >> +$id: http://devicetree.org/schemas/display/bridge/ti,sn65dsi83.yaml# >> +$schema: http://devicetree.org/meta-schemas/core.yaml# >> + >> +title: SN65DSI83 and SN65DSI84 DSI to LVDS bridge chip > > Can it possible to wait for my v4 to have dual-link LVDS supported > which is quite discussing points on previous versions? This driver already has the dual-link LVDS support on DSI84 and it is tested on real hardware. So is the single-link LVDS on DSI83, on multiple hardware instances. In addition to that, this driver has proper regmap support and constant time calculation of DSI83/84 clock register settings. Note that I did wait for your v4 for over two weeks already, it just didn't materialize, so I determined it might be a good idea to restart work on this driver instead. Maybe you can test this driver and check what is missing for your usecase?