Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp2019323rwd; Wed, 17 May 2023 04:49:27 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ4xCufzq4WHBN8H6xlK9LFLF+oN9jDvhyfQarVntLGYDmyxN2K8e6FB9As0H2nHEmeExiSe X-Received: by 2002:a05:6a00:a0d:b0:64c:c453:244f with SMTP id p13-20020a056a000a0d00b0064cc453244fmr659974pfh.15.1684324167594; Wed, 17 May 2023 04:49:27 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1684324167; cv=none; d=google.com; s=arc-20160816; b=SkwPbldsJ8T8TuQunbyZE7VzN4lSanAzJ6IVNHn4ywDAdO955aLAQhSH0RzZLzRQmR wUs8X82/d+uAXXHut6McQ39siA/sl34VcmGufLgPW3J0nBmSYumNfyGa2tjwFJvWttgz dJe8kU5MBtvp89mm10HpoVkddAEEa9qL81XMeuH1nMhSz5+X4aja4wwyI98vAMSPy6OK AK4cw5UvdBpN2CdK2sCH9GwnmU/xzn70giWi2teRHojqqwVysvSZlr0oP51nL3NGrohh lQ5+GzOpIftsKbe5+bJGu365EjRky6j5ocmZoZOQ3E7nH1UF2KpQjKJX5X6vQf4JM2f4 O1+g== 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=3o2tVJQBKqbYOhLGPD0uYl/0T73lg7VFfZy9i2I0OMY=; b=tyDp70iHPx4HVnDp498NPSpy1ucuEK/pAYEq2VmnZPN6dGIelBS9Fk9PKuU93v1pIv Ux/z7BN27S5zXUAnECAFWPrCtwNEdSF25aiUtXe0JWegDN46OJg0nlwTp5glgLzAo8Ec IjCbvAGNMIQpgiBDHndpM7/qkEQmHnRk721DrotZCzeQI9e72fjf/aCPsNlMWkcb+d7p n01r3IneFke1hWgiVa9dHDzAOowGFErVDm+EgeuN4nwZyd3+hZKIGqbJLux+/ryOAr/7 B5N0Aowt3l+fT532N2c95uENz9xXkb3IIzyUfspApMpWrQ+e30ZxKIlkwWyvDQIArIJ3 ytQw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@amarulasolutions.com header.s=google header.b="oqT/+gSq"; 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 y18-20020a63b512000000b0052c2061447dsi21032053pge.522.2023.05.17.04.49.13; Wed, 17 May 2023 04:49:27 -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="oqT/+gSq"; 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 S230443AbjEQL2G (ORCPT + 99 others); Wed, 17 May 2023 07:28:06 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45374 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231211AbjEQL2F (ORCPT ); Wed, 17 May 2023 07:28:05 -0400 Received: from mail-yb1-xb33.google.com (mail-yb1-xb33.google.com [IPv6:2607:f8b0:4864:20::b33]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 106C93C34 for ; Wed, 17 May 2023 04:28:04 -0700 (PDT) Received: by mail-yb1-xb33.google.com with SMTP id 3f1490d57ef6-ba865ac594bso607664276.0 for ; Wed, 17 May 2023 04:28:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=amarulasolutions.com; s=google; t=1684322883; x=1686914883; 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=3o2tVJQBKqbYOhLGPD0uYl/0T73lg7VFfZy9i2I0OMY=; b=oqT/+gSqpHczmyKhxBcrWwriOapQ7izKdPneKcvVuY+gcz4PUY3eB9dPNj0ZRml9ku NN/tDywHPagraF2TSqg8TBauWdnBhJYR0TiMPnvhCAZOCENkd13b7LgoofwCeOvCceHU BRWj5EJ/F0fd1LvOn01GKFTO0980EW7ZqjHnI= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1684322883; x=1686914883; 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=3o2tVJQBKqbYOhLGPD0uYl/0T73lg7VFfZy9i2I0OMY=; b=H2P0fZo8nJXOqv1r2wuY9uoMjfHvQ3TdPfRygKRYPFE2hQFzBlw6w20dRDIsxmrFXS Bl4N0RVDtYi4R/fimkGieA/3103Xt+lqJ9f0Vpig+iplDaf1qewa8t/KnlRg5zysGK3W 8YjIYjk/T28uD7UuQk000Bzg8Kyo81LmWUey2SmWgndK7+IKb1Jji6wCt7jMXcmth6l1 +8zJBICSU8gQD1JvceM5mRcwjDU2LREnLI+pzQuwnvcTq5xsyPBUpvxrwjyKrWyUmdkH ZICV5L9VUe7cG5UHAL7wWPZNaI7kQ+wImokxry2locK8VCW1sktV466fKyD4utKPsmyt OmgQ== X-Gm-Message-State: AC+VfDzFTRswgiPPlAmtJx5BjnE+VIvof5szghCeaAlOOTdthP9S5qCj jm9TbgIScrkmBzVzpmO4JRr3wHGsUhvI8U9f2bdqaw== X-Received: by 2002:a0d:d895:0:b0:561:9800:81f4 with SMTP id a143-20020a0dd895000000b00561980081f4mr3239721ywe.50.1684322883168; Wed, 17 May 2023 04:28:03 -0700 (PDT) MIME-Version: 1.0 References: <20230515235713.232939-1-aford173@gmail.com> <20230515235713.232939-6-aford173@gmail.com> In-Reply-To: <20230515235713.232939-6-aford173@gmail.com> From: Jagan Teki Date: Wed, 17 May 2023 16:57:50 +0530 Message-ID: Subject: Re: [PATCH V6 5/6] drm: bridge: samsung-dsim: Dynamically configure DPHY timing To: Adam Ford Cc: dri-devel@lists.freedesktop.org, aford@beaconembedded.com, Lucas Stach , Chen-Yu Tsai , Frieder Schrempf , Michael Walle , 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,URIBL_BLOCKED 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 DPHY timings are currently hard coded. Since the input > clock can be variable, the phy timings need to be variable > too. To facilitate this, we need to cache the hs_clock > based on what is generated from the PLL. > > The phy_mipi_dphy_get_default_config_for_hsclk function > configures the DPHY timings in pico-seconds, and a small macro > converts those timings into clock cycles based on the hs_clk. > > Signed-off-by: Adam Ford > Signed-off-by: Lucas Stach > Tested-by: Chen-Yu Tsai > Tested-by: Frieder Schrempf > Reviewed-by: Frieder Schrempf > Tested-by: Michael Walle > --- > drivers/gpu/drm/bridge/samsung-dsim.c | 57 +++++++++++++++++++++++---- > include/drm/bridge/samsung-dsim.h | 1 + > 2 files changed, 51 insertions(+), 7 deletions(-) > > diff --git a/drivers/gpu/drm/bridge/samsung-dsim.c b/drivers/gpu/drm/brid= ge/samsung-dsim.c > index 08266303c261..3944b7cfbbdf 100644 > --- a/drivers/gpu/drm/bridge/samsung-dsim.c > +++ b/drivers/gpu/drm/bridge/samsung-dsim.c > @@ -218,6 +218,8 @@ > > #define OLD_SCLK_MIPI_CLK_NAME "pll_clk" > > +#define PS_TO_CYCLE(ps, hz) DIV64_U64_ROUND_CLOSEST(((ps) * (hz)), 10000= 00000000ULL) > + > static const char *const clk_names[5] =3D { > "bus_clk", > "sclk_mipi", > @@ -651,6 +653,8 @@ static unsigned long samsung_dsim_set_pll(struct sams= ung_dsim *dsi, > reg =3D samsung_dsim_read(dsi, DSIM_STATUS_REG); > } while ((reg & DSIM_PLL_STABLE) =3D=3D 0); > > + dsi->hs_clock =3D fout; > + > return fout; > } > > @@ -698,13 +702,46 @@ static void samsung_dsim_set_phy_ctrl(struct samsun= g_dsim *dsi) > const struct samsung_dsim_driver_data *driver_data =3D dsi->drive= r_data; > const unsigned int *reg_values =3D driver_data->reg_values; > u32 reg; > + struct phy_configure_opts_mipi_dphy cfg; > + int clk_prepare, lpx, clk_zero, clk_post, clk_trail; > + int hs_exit, hs_prepare, hs_zero, hs_trail; > + unsigned long long byte_clock =3D dsi->hs_clock / 8; > > if (driver_data->has_freqband) > return; > > + phy_mipi_dphy_get_default_config_for_hsclk(dsi->hs_clock, > + dsi->lanes, &cfg); > + > + /* > + * TODO: > + * The tech reference manual for i.MX8M Mini/Nano/Plus Does it mean, Applications Processor Reference Manual? better add it clear reference. > + * doesn't state what the definition of the PHYTIMING > + * bits are beyond their address and bit position. > + * After reviewing NXP's downstream code, it appears > + * that the various PHYTIMING registers take the number > + * of cycles and use various dividers on them. This > + * calculation does not result in an exact match to the > + * downstream code, but it is very close, and it appears > + * to sync at a variety of resolutions. If someone > + * can get a more accurate mathematical equation needed > + * for these registers, this should be updated. > + */ > + > + lpx =3D PS_TO_CYCLE(cfg.lpx, byte_clock); > + hs_exit =3D PS_TO_CYCLE(cfg.hs_exit, byte_clock); > + clk_prepare =3D PS_TO_CYCLE(cfg.clk_prepare, byte_clock); > + clk_zero =3D PS_TO_CYCLE(cfg.clk_zero, byte_clock); > + clk_post =3D PS_TO_CYCLE(cfg.clk_post, byte_clock); > + clk_trail =3D PS_TO_CYCLE(cfg.clk_trail, byte_clock); > + hs_prepare =3D PS_TO_CYCLE(cfg.hs_prepare, byte_clock); > + hs_zero =3D PS_TO_CYCLE(cfg.hs_zero, byte_clock); > + hs_trail =3D PS_TO_CYCLE(cfg.hs_trail, byte_clock); I think we can do some kind of negotiation has done similar in bsp by taking inputs from bit_clk and PLL_1432X table. Did you try this? we thought this approach while writing dsim to support dynamic dphy. Thanks, Jagan.