Received: by 2002:a05:6358:53a8:b0:117:f937:c515 with SMTP id z40csp4473294rwe; Mon, 17 Apr 2023 13:16:08 -0700 (PDT) X-Google-Smtp-Source: AKy350YnQNX9bjY3ra5BJomd3rgo/urh4bWC4xjo8mp3hEH3r+fBPMXz3o0mf/1PHM1M2AtfsUjN X-Received: by 2002:a05:6a20:2896:b0:eb:bbd1:6d6c with SMTP id q22-20020a056a20289600b000ebbbd16d6cmr15287495pzf.21.1681762568097; Mon, 17 Apr 2023 13:16:08 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1681762568; cv=none; d=google.com; s=arc-20160816; b=kfN9AsX6mrx7KIcexkLiLIdEH3S4ftGSEsUuQyUR0ho8EOWpZvrhJzkF0IcwDunUmC Zn7JsQDkUAO/wbXSO+AjfKcJyMnzARkU1k/8H1aJQxyNUfJ1eeRPGwWdARJjWVRwFiiJ Ux/Us8JzwLL4+3WvB+qFEB5rwF+Blr8iagzjHj82a4xiYvlX9z6vJhXm6qzmIRLitEm3 Zlu+LYTrpUF0Sk/jR2dL5i8Mn8px1ahqMivCKhKb4k/WF6Gpb4vPej8a1c00y4YDu1KT zXSpsiAWlybH5er3vkT0rcMwNAEV1kL4c1sX++TXqfC0BwUYnszYJTCofIOhAJbdurYK yCHQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :references:cc:to:content-language:subject:user-agent:mime-version :date:message-id:dkim-signature; bh=XPP/G+qQIG5sSIyEjLZmdN2TPpVm52+eBjT1AvxiWxQ=; b=Af7uFlAShwSWN7qJXXSl3hCsZ0bSGt8/2ZkAT023LcR8y3oW76LLeEJuhszGjtEu5e uLBQaGYLcqwr6xSq8OfI1PieYs/bwhPRHTOpJryOoMge/eiyFZliX0TkAiqCbnofXE3I +tk3Zdbthy8LzkkozRhpY5EwQmfO5SB9p/nRyhAfh/3JT8hV6Wso/YVgCwbUo/zFVZKn vPZQNwOyllcZvgkUM4h7r36JjPJIyitgZyJsnHjdJfbvQUj/9WgPeZ1/P7T+MVpQfEy6 /YZWe+Bjhk8si973e7Xaw5z6DlKd/UmyB4Ekpg4D+hzi1P/ersmlRe7mv4KSf1bGmwvU X5ew== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@denx.de header.s=phobos-20191101 header.b=ugfZ3KIJ; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id j3-20020a654303000000b00513af1fa0b5si12228403pgq.797.2023.04.17.13.15.56; Mon, 17 Apr 2023 13:16:08 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@denx.de header.s=phobos-20191101 header.b=ugfZ3KIJ; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230186AbjDQUIE (ORCPT + 99 others); Mon, 17 Apr 2023 16:08:04 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40748 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229738AbjDQUID (ORCPT ); Mon, 17 Apr 2023 16:08:03 -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 C00C197; Mon, 17 Apr 2023 13:08:01 -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 F0E8685EA1; Mon, 17 Apr 2023 22:07:56 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=denx.de; s=phobos-20191101; t=1681762079; bh=XPP/G+qQIG5sSIyEjLZmdN2TPpVm52+eBjT1AvxiWxQ=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=ugfZ3KIJ+KaeTax2ZVm6VcUGnx/XmsCQNR9m1m11D15ktTdAorJBuZyU05wGA9oMx RlldaNA58RLUIXAEwcdDnatL7YFxkUJAwMKGGhUSuLY4alntaoIxQmV1tRs8dJK0nL YMGf275S3W/KJ3CDm0SZf0l4/GSa4SRWm+r93ccZi3Tq4+kpmAirWDjNNp3ificymF CRwcsgDWCKs+p1pSLfEBScSma2AOXQhferBU5spwvB+DfCKIc46LUMImYJ+aUxRNmx 748L+r0eXYExBJphenJMetA02XGNHZxefwlbGOdaT3s4miBhdDZDyNiK7SS8opvt4m K4o51Ca4P4wog== Message-ID: <88e53197-2819-c068-eba6-a218a19d8d15@denx.de> Date: Mon, 17 Apr 2023 22:07:56 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.9.0 Subject: Re: [PATCH 5/6] drm: bridge: samsung-dsim: Support non-burst mode Content-Language: en-US To: Adam Ford Cc: dri-devel@lists.freedesktop.org, m.szyprowski@samsung.com, aford@beaconembedded.com, Rob Herring , Krzysztof Kozlowski , Shawn Guo , Sascha Hauer , Pengutronix Kernel Team , Fabio Estevam , NXP Linux Team , Inki Dae , Jagan Teki , Andrzej Hajda , Neil Armstrong , Robert Foss , Laurent Pinchart , Jonas Karlman , Jernej Skrabec , David Airlie , Daniel Vetter , Frieder Schrempf , devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Lucas Stach References: <20230415104104.5537-1-aford173@gmail.com> <20230415104104.5537-5-aford173@gmail.com> <807aa6c6-bbea-abcc-172d-17e22d1a3988@denx.de> From: Marek Vasut In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: clamav-milter 0.103.8 at phobos.denx.de X-Virus-Status: Clean X-Spam-Status: No, score=-6.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A,RCVD_IN_DNSWL_MED, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 4/17/23 13:57, Adam Ford wrote: > On Sun, Apr 16, 2023 at 5:13 PM Marek Vasut wrote: >> >> On 4/15/23 12:41, Adam Ford wrote: >>> The high-speed clock is hard-coded to the burst-clock >>> frequency specified in the device tree. However, when >>> using devices like certain bridge chips without burst mode >>> and varying resolutions and refresh rates, it may be >>> necessary to set the high-speed clock dynamically based >>> on the desired pixel clock for the connected device. >> >> The link rate negotiation should happen internally between the nearest >> bridge and DSIM, so please add that to DRM core instead of hacking >> around it by tweaking the HS clock again. > > I thought you tried to add something like this before and had some resistance. Yes, all my attempts were rejected by a single reviewer. I suspended my efforts in that area for now. > The Pixel clock is set by the bridge already without any new code > added to the DRM core.. I am just reading that value that's there, > and setting the clock accordingly. I don't see how this is a hack. Assume you have a DSI-to-HDMI bridge attached to your DSIM bridge, it operates in non-burst mode, like ADV7533 . How would you configure the HS clock rate for such a bridge in DT ? (hint: you cannot, because the required clock comes from the EDID, which may not be available just yet)