All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sylwester Nawrocki <s.nawrocki@samsung.com>
To: Marek Szyprowski <m.szyprowski@samsung.com>,
	Stephen Boyd <sboyd@kernel.org>,
	linux-clk@vger.kernel.org, linux-samsung-soc@vger.kernel.org
Cc: Sylwester Nawrocki <snawrocki@kernel.org>,
	Chanwoo Choi <cw00.choi@samsung.com>,
	Krzysztof Kozlowski <krzk@kernel.org>,
	Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
	Marian Mihailescu <mihailescu2m@gmail.com>,
	Michael Turquette <mturquette@baylibre.com>
Subject: Re: [PATCH] clk: samsung: exynos5420: Keep top G3D clocks enabled
Date: Mon, 16 Dec 2019 12:05:16 +0100	[thread overview]
Message-ID: <26b1c535-b942-29f8-ca93-f841a01f0441@samsung.com> (raw)
In-Reply-To: <f7fbb6a3-6890-7a25-3a15-b608aa2e69dc@samsung.com>

On 12/13/19 08:11, Marek Szyprowski wrote:
> The real issue here is that some SoC internal busses (not assigned to 
> any driver at all) are sourced from the same MUX, which that patch 
> flagged as CRITICAL without any additional gates, thus if the only 
> client of that MUX disables its gate clock, the whole path up to the 
> root PLL is disabled what causes the HW issue. The driver (or user via 
> dts) might change the root PLL, so that CRITICAL flag cannot be moved to 
> the top clock in this hierarchy.
> 
> I can change that CRITICAL flag to a explicit call to 
> clk_prepare_enable() during exynos542x-clk driver probe, but IMHO the 
> flag better fits in such case.

I would prefer an explicit clk_prepare_enable() call, similarly as it is 
done in drivers/clk/samsung/clk-exynos-audss.c. This would somewhat separate
proper clocks definition from workarounds. The CLK_IS_CRITICAL flag might be 
a bit misleading IMO because the clock for which it is being added now doesn't 
have gating ability. The flag really applies to some root PLL clock which is
behind few other muxes going up in the clk tree.

-- 
Regards
Sylwester

      reply	other threads:[~2019-12-16 11:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20191121101158eucas1p26b1f74cd2396a2461530e684d17a82e8@eucas1p2.samsung.com>
2019-11-21 10:11 ` [PATCH] clk: samsung: exynos5420: Keep top G3D clocks enabled Marek Szyprowski
2019-11-22  1:43   ` Chanwoo Choi
2019-12-12 11:53   ` Sylwester Nawrocki
2019-12-13  3:03     ` Stephen Boyd
2019-12-13  7:11       ` Marek Szyprowski
2019-12-16 11:05         ` Sylwester Nawrocki [this message]

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=26b1c535-b942-29f8-ca93-f841a01f0441@samsung.com \
    --to=s.nawrocki@samsung.com \
    --cc=b.zolnierkie@samsung.com \
    --cc=cw00.choi@samsung.com \
    --cc=krzk@kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    --cc=mihailescu2m@gmail.com \
    --cc=mturquette@baylibre.com \
    --cc=sboyd@kernel.org \
    --cc=snawrocki@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.