From: "대인기/Tizen Platform Lab(SR)/삼성전자" <inki.dae@samsung.com>
To: "'Michael Tretter'" <m.tretter@pengutronix.de>,
"'Inki Dae'" <daeinki@gmail.com>
Cc: "'Neil Armstrong'" <neil.armstrong@linaro.org>,
"'Robert Foss'" <rfoss@kernel.org>,
"'Jonas Karlman'" <jonas@kwiboo.se>,
<dri-devel@lists.freedesktop.org>, <linux-kernel@vger.kernel.org>,
"'Jernej Skrabec'" <jernej.skrabec@gmail.com>,
"'Laurent Pinchart'" <Laurent.pinchart@ideasonboard.com>,
"'Andrzej Hajda'" <andrzej.hajda@intel.com>,
"'Marek Szyprowski'" <m.szyprowski@samsung.com>,
<kernel@pengutronix.de>,
"'Jagan Teki'" <jagan@amarulasolutions.com>
Subject: RE: [PATCH 3/5] drm/bridge: samsung-dsim: update PLL reference clock
Date: Tue, 5 Sep 2023 18:06:06 +0900 [thread overview]
Message-ID: <001001d9dfd8$3444bbb0$9cce3310$@samsung.com> (raw)
In-Reply-To: <20230904111520.GC224131@pengutronix.de>
> -----Original Message-----
> From: dri-devel <dri-devel-bounces@lists.freedesktop.org> On Behalf Of
> Michael Tretter
> Sent: Monday, September 4, 2023 8:15 PM
> To: Inki Dae <daeinki@gmail.com>
> Cc: Neil Armstrong <neil.armstrong@linaro.org>; Robert Foss
> <rfoss@kernel.org>; Jonas Karlman <jonas@kwiboo.se>; dri-
> devel@lists.freedesktop.org; linux-kernel@vger.kernel.org; Jernej Skrabec
> <jernej.skrabec@gmail.com>; Laurent Pinchart
> <Laurent.pinchart@ideasonboard.com>; Andrzej Hajda
> <andrzej.hajda@intel.com>; Marek Szyprowski <m.szyprowski@samsung.com>;
> kernel@pengutronix.de; Jagan Teki <jagan@amarulasolutions.com>
> Subject: Re: [PATCH 3/5] drm/bridge: samsung-dsim: update PLL reference
> clock
>
> On Mon, 04 Sep 2023 14:44:41 +0900, Inki Dae wrote:
> > 2023년 8월 29일 (화) 오전 12:59, Michael Tretter <m.tretter@pengutronix.de>
> 님이 작성:
> > >
> > > The PLL requires a clock between 2 MHz and 30 MHz after the pre-
> divider.
> > > The reference clock for the PLL may change due to changes to it's
> parent
> > > clock. Thus, the frequency may be out of range or unsuited for
> > > generating the high speed clock for MIPI DSI.
> > >
> > > Try to keep the pre-devider small, and set the reference clock close
> to
> > > 30 MHz before recalculating the PLL configuration. Use a divider with
> a
> > > power of two for the reference clock as this seems to work best in
> > > my tests.
> >
> > Clock frequency is specific to SoC architecture so we have to handle
> > it carefully because samsung-dsim.c is a common module for I.MX and
> > Exynos series.
> > You mentioned "The PLL requires a clock between 2 MHz and 3MHz after
> > pre-divider", and the clock means that fin_pll - PFD input frequency -
> > which can be calculated with oscillator clock frequency / P value?
> > According to Exynos datasheet, the fin_pll should be 6 ~ 12Mhz.
> >
> > For example,
> > In case of Exyhos, we use 24MHz as oscillator clock frequency, so
> > fin_pll frequency, 8MHz = 24MHz / P(3).
> >
> > Can you tell me the source of the constraint that clocks must be
> > between 2MHz and 30MHz?
>
> The source is the i.MX8M Nano reference manual, Table 13-40. DPHY PLL
> Parameters. It documents that the P divider frequency (fin_pll) has a
> frequency range of 2 MHz to 30 MHz. According to the same table, the input
In case of Exynos, the range is from 6MHz to 12MHz according to Exynos4212 reference manual, Table 1-5.
> frequency (fin) has a range of 6 MHz to 300 MHz.
In case of Exynos, the range is from 6MHz to 200MHz.
>
> Is the table incorrect?
It's correct for I.MX but incorrect for Exynos. I think it would mean that the valid range depends on SoC architecture. So I'd say that this patch is specific to I.MX. This was one of what I concerted about when trying to move samsung-dsim.c module to bridge directory for common use between I.MX and Exynos Platforms, and this will be what we have to solve together - I.MX and Exynos engineers. How about using platform specific data - samsung_dsim_driver_data structure?
I.e,
static const struct samsung_dsim_driver_data imx8mm_dsi_driver_data = {
...
.min_fin_pll = 2,
.max_fin_pll = 30,
...
};
static const struct samsung_dsim_driver_data exynosxxxx_dsi_driver_data = {
...
.min_fin_pll = 6,
.max_fin_pll = 12,
...
};
And then,
while (fin > driver_data->max_fin_pll * MHZ)
fin = fin / 2;
>
> I also tried to always set the reference clock to 24 MHz, but depending on
> the
> display clock this isn't always possible.
According to dt binding, if samsung,pll-clock-frequency exists then we have to use it first. I'm not sure but could we check if the pll_clk_rate is valid or not depending on the given display clock in advance? If so then maybe we could update the pll_clk_rate correctly by reading the pll_clk frequency again.
Thanks,
Inki Dae
>
> Michael
>
> >
> > To other I.MX and Exynos engineers, please do not merge this patch
> > until two SoC platforms are tested correctly.
> >
> > Thanks,
> > Inki Dae
> >
> > >
> > > Signed-off-by: Michael Tretter <m.tretter@pengutronix.de>
> > > ---
> > > drivers/gpu/drm/bridge/samsung-dsim.c | 15 +++++++++++++--
> > > 1 file changed, 13 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/drivers/gpu/drm/bridge/samsung-dsim.c
> b/drivers/gpu/drm/bridge/samsung-dsim.c
> > > index da90c2038042..4de6e4f116db 100644
> > > --- a/drivers/gpu/drm/bridge/samsung-dsim.c
> > > +++ b/drivers/gpu/drm/bridge/samsung-dsim.c
> > > @@ -611,10 +611,21 @@ static unsigned long samsung_dsim_set_pll(struct
> samsung_dsim *dsi,
> > > u16 m;
> > > u32 reg;
> > >
> > > - if (dsi->pll_clk)
> > > + if (dsi->pll_clk) {
> > > + /*
> > > + * Ensure that the reference clock is generated with a
> power of
> > > + * two divider from its parent, but close to the PLLs
> upper
> > > + * limit of the valid range of 2 MHz to 30 MHz.
> > > + */
> > > + fin = clk_get_rate(clk_get_parent(dsi->pll_clk));
> > > + while (fin > 30 * MHZ)
> > > + fin = fin / 2;
> > > + clk_set_rate(dsi->pll_clk, fin);
> > > +
> > > fin = clk_get_rate(dsi->pll_clk);
> > > - else
> > > + } else {
> > > fin = dsi->pll_clk_rate;
> > > + }
> > > dev_dbg(dsi->dev, "PLL ref clock freq %lu\n", fin);
> > >
> > > fout = samsung_dsim_pll_find_pms(dsi, fin, freq, &p, &m, &s);
> > >
> > > --
> > > 2.39.2
> > >
> >
next prev parent reply other threads:[~2023-09-05 16:57 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-28 15:59 [PATCH 0/5] drm/bridge: samsung-dsim: fix various modes with ADV7535 bridge Michael Tretter
2023-08-28 15:59 ` [PATCH 1/5] drm/bridge: samsung-dsim: add more mipi-dsi device debug information Michael Tretter
2023-08-28 22:37 ` Adam Ford
2023-09-04 1:04 ` Inki Dae
2023-09-27 12:47 ` Adam Ford
2023-10-04 15:22 ` Michael Tretter
2023-08-28 15:59 ` [PATCH 2/5] drm/bridge: samsung-dsim: reread ref clock before configuring PLL Michael Tretter
2023-09-04 4:38 ` Inki Dae
2023-09-04 11:04 ` Michael Tretter
2023-08-28 15:59 ` [PATCH 3/5] drm/bridge: samsung-dsim: update PLL reference clock Michael Tretter
2023-08-28 16:41 ` Marco Felsch
2023-08-28 18:17 ` Adam Ford
2023-08-29 7:49 ` Michael Tretter
2023-09-04 5:44 ` Inki Dae
2023-09-04 11:15 ` Michael Tretter
2023-09-05 9:06 ` 대인기/Tizen Platform Lab(SR)/삼성전자 [this message]
2023-09-08 9:47 ` Michael Tretter
2023-09-18 8:42 ` 대인기/Tizen Platform Lab(SR)/삼성전자
2023-08-28 15:59 ` [PATCH 4/5] drm/bridge: samsung-dsim: adjust porches by rounding up Michael Tretter
2023-08-28 18:26 ` Fabio Estevam
2023-08-28 22:39 ` Adam Ford
2023-08-29 7:51 ` Michael Tretter
2023-08-28 15:59 ` [PATCH 5/5] drm/bridge: samsung-dsim: calculate porches in Hz Michael Tretter
2023-08-28 22:41 ` Adam Ford
2023-09-04 14:28 ` Maxim Schwalm
2023-09-08 8:20 ` Michael Tretter
2023-08-28 16:13 ` [PATCH 0/5] drm/bridge: samsung-dsim: fix various modes with ADV7535 bridge Adam Ford
2023-08-28 23:07 ` Adam Ford
2023-08-29 8:03 ` Michael Tretter
2023-08-28 16:42 ` Marco Felsch
2023-09-04 14:02 ` Frieder Schrempf
2023-09-06 9:31 ` Frieder Schrempf
2023-09-06 9:56 ` Michael Tretter
2023-09-07 8:20 ` Frieder Schrempf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='001001d9dfd8$3444bbb0$9cce3310$@samsung.com' \
--to=inki.dae@samsung.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=andrzej.hajda@intel.com \
--cc=daeinki@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jagan@amarulasolutions.com \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=m.tretter@pengutronix.de \
--cc=neil.armstrong@linaro.org \
--cc=rfoss@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox