Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp907029rwd; Thu, 18 May 2023 05:42:09 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ5X7WVles9bx57BEY9ZVCS/1e7GJPat1Fl+HUD0BxfAHZMuo7hMyCrQokjj1Wd7SEQC0qNi X-Received: by 2002:a05:6a00:17aa:b0:64a:5cde:3a8c with SMTP id s42-20020a056a0017aa00b0064a5cde3a8cmr4555325pfg.28.1684413729380; Thu, 18 May 2023 05:42:09 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1684413729; cv=none; d=google.com; s=arc-20160816; b=DhyQ+i1eY7aRpPFkdBtlOl50IicO+KW7ZiMATeUAAhP6A/Z5m2AJcZ9aMzTXFMN/kD LzvA0Dv0aPYgWprikt6dWEYSTPynt4egPEvjf8lm4rymlYoKKeoTkjBpVJpPSh1VE/Hj qpUMNCEfq78YD0WmZvFaGHvgOtnXiDKZL+LK5AS1hfP9xyJPwMLxFTr8rm+azYBYzh7k YE8y1r1wQS6FN9wgDSa6HI2OvUovHq5FPtAb5vf9O3UiYw6BwsXUpoOEESlWKP5n7C6A +eaG2KpTsdlTwH+zUgw8kRVo63b5Vrs3PHLTiCHfNGyvAurtT8A8gs2c5oUZN5DTYIC6 XVBQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:cc:to:subject :message-id:date:from:in-reply-to:references:mime-version :dkim-signature; bh=6+vYjmpxBNlZuPV45+UQsttMirEjwbsfvsjjU7mymMg=; b=TzF527obP30ofDe8LcyioDdq0/nYtOk7yYDzx0GOU/AuUtvNQcuuC7SBI+0IJGKBTv M/ZFcuUGU44QQEwX7nZIYJ5z/ov/Vj2z6WLDP7SmS+AWw0BLRErC+Z3gLuqJzmnHtxxp V5EzF//Q05AvmcNQhwoWiRJYzuBoFRSi617CbWhgwO1c3P4rEdgkel8llHcbUx8sL1Oi 5eZ46sPs1wHZ6un/MQ2qRm7lRtkS1fBgIVKeom9M+5t2RlbsHcGD+x739wZ5Jjey3WfR jaccjgeXPH3Zl6o6hKp7rAwuuEAY+o7rAHwHsmMm1wqgYHnfXlTjJjYx+ZA8nkxIxqPD ixlQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@amarulasolutions.com header.s=google header.b=lDHD9kTy; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=amarulasolutions.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id x15-20020aa7940f000000b0064105588e53si1478488pfo.359.2023.05.18.05.41.57; Thu, 18 May 2023 05:42:09 -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=@amarulasolutions.com header.s=google header.b=lDHD9kTy; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=amarulasolutions.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231499AbjERMHZ (ORCPT + 99 others); Thu, 18 May 2023 08:07:25 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:51584 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230025AbjERMHX (ORCPT ); Thu, 18 May 2023 08:07:23 -0400 Received: from mail-yw1-x1136.google.com (mail-yw1-x1136.google.com [IPv6:2607:f8b0:4864:20::1136]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 890C610A for ; Thu, 18 May 2023 05:07:21 -0700 (PDT) Received: by mail-yw1-x1136.google.com with SMTP id 00721157ae682-561b43fc896so17538447b3.0 for ; Thu, 18 May 2023 05:07:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=amarulasolutions.com; s=google; t=1684411641; x=1687003641; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=6+vYjmpxBNlZuPV45+UQsttMirEjwbsfvsjjU7mymMg=; b=lDHD9kTyu6C900iWJgAaI2zvYQGebe2WQhin5yh6ukpDVVrT7AgP2envsyg2lltUis IlYbmeg4Cul0fO+mjEE5UfTSWx105bkw9tWQ+ekrhA20Oe+A8u8+Ru16OksVoEOR3kL6 xlDFjtqfMAJMQ39F+6lcfqIfZcRtxr7sxCm4U= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1684411641; x=1687003641; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=6+vYjmpxBNlZuPV45+UQsttMirEjwbsfvsjjU7mymMg=; b=ROXbpapBrRkjGuBxynVENOlWKKfcFUS3sZRc8AGGErJx28jzR7s8doHEWwoj6fu/id MT0esShpe/MV26sDux1+6DKsxxMkIV0NmtLUtnEgLGejxboDyzW+MP82p+D4hywoEB6F SdMBz7e6hy7VfS8O7cALRtPazHmqJ/+pHqdOzqA1vFEluWD+4FrxjCNieyZQA2PzGbud /XsitoTcOEYlm0+/TK0VLFR30LJLrY5F1HhPnEmmQJaS+ApnJIE+ruBEmHt4W3DhOAqn tPE3SQQ8hQmM3uDwLbqx8gGmQS/s5q66JRoYMr5Xd5R4XXzFtWi5jW58tTy6g7mi97ZA kKsQ== X-Gm-Message-State: AC+VfDzf0x8567Uf42j3C1jcU7ay4p11Cw9fxe/vXhTFz5lVQy9I0unh SNeJVKm4emxndkXJUJHRJfxoC7VT5yH8U1w7GORz7g== X-Received: by 2002:a0d:cb8b:0:b0:561:d21d:8ce4 with SMTP id n133-20020a0dcb8b000000b00561d21d8ce4mr1018258ywd.19.1684411640769; Thu, 18 May 2023 05:07:20 -0700 (PDT) MIME-Version: 1.0 References: <20230515235713.232939-1-aford173@gmail.com> <20230515235713.232939-7-aford173@gmail.com> In-Reply-To: <20230515235713.232939-7-aford173@gmail.com> From: Jagan Teki Date: Thu, 18 May 2023 17:37:09 +0530 Message-ID: Subject: Re: [PATCH V6 6/6] drm: bridge: samsung-dsim: Support non-burst mode To: Adam Ford Cc: dri-devel@lists.freedesktop.org, aford@beaconembedded.com, Chen-Yu Tsai , Frieder Schrempf , Andrzej Hajda , Neil Armstrong , Robert Foss , Laurent Pinchart , Jonas Karlman , Jernej Skrabec , David Airlie , Daniel Vetter , Inki Dae , Marek Szyprowski , Marek Vasut , linux-kernel@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, 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 Tue, May 16, 2023 at 5:27=E2=80=AFAM Adam Ford wrot= e: > > 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. > > This also removes the need to set a clock speed from > the device tree for non-burst mode operation, since the > pixel clock rate is the rate requested from the attached > device like a bridge chip. This should have no impact > for people using burst-mode and setting the burst clock > rate is still required for those users. If the burst > clock is not present, change the error message to > dev_info indicating the clock use the pixel clock. > > Signed-off-by: Adam Ford > Tested-by: Chen-Yu Tsai > Tested-by: Frieder Schrempf > Reviewed-by: Frieder Schrempf > --- > drivers/gpu/drm/bridge/samsung-dsim.c | 27 +++++++++++++++++++++------ > 1 file changed, 21 insertions(+), 6 deletions(-) > > diff --git a/drivers/gpu/drm/bridge/samsung-dsim.c b/drivers/gpu/drm/brid= ge/samsung-dsim.c > index 3944b7cfbbdf..03b21d13f067 100644 > --- a/drivers/gpu/drm/bridge/samsung-dsim.c > +++ b/drivers/gpu/drm/bridge/samsung-dsim.c > @@ -655,16 +655,28 @@ static unsigned long samsung_dsim_set_pll(struct sa= msung_dsim *dsi, > > dsi->hs_clock =3D fout; > > + dsi->hs_clock =3D fout; I dropped this and tested it. Reviewed-by: Jagan Teki Tested-by: Jagan Teki # imx8mm-icore