From: Sylwester Nawrocki <s.nawrocki@samsung.com>
To: Marek Szyprowski <m.szyprowski@samsung.com>,
linux-samsung-soc@vger.kernel.org
Cc: linux-clk@vger.kernel.org,
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>
Subject: Re: [PATCH] clk: samsung: exynos542x: Move G3D subsystem clocks to its sub-CMU
Date: Wed, 23 Oct 2019 15:03:45 +0200 [thread overview]
Message-ID: <9b9d013d-3bbb-e9e9-b161-e885cb6b1c2f@samsung.com> (raw)
In-Reply-To: <20191023074118.3012-1-m.szyprowski@samsung.com>
On 10/23/19 09:41, Marek Szyprowski wrote:
> G3D clocks require special handling of their parent bus clock during power
> domain on/off sequences. Those clocks were not initially added to the
> sub-CMU handler, because that time there was no open-source driver for the
> G3D (MALI Panfrost) hardware module and it was not possible to test it.
>
> This patch fixes this issue. Parent clock for G3D hardware block is now
> properly preserved during G3D power domain on/off sequence. This restores
> proper MALI Panfrost performance broken by commit 8686764fc071
> ("ARM: dts: exynos: Add G3D power domain to Exynos542x").
>
> Reported-by: Marian Mihailescu <mihailescu2m@gmail.com>
> Fixes: b06a532bf1fa ("clk: samsung: Add Exynos5 sub-CMU clock driver")
> Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
> Tested-by: Marian Mihailescu <mihailescu2m@gmail.com>
Applied, thanks.
prev parent reply other threads:[~2019-10-23 13:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20191023074140eucas1p2c236bde672f33d4fe32ed61545515cc3@eucas1p2.samsung.com>
2019-10-23 7:41 ` [PATCH] clk: samsung: exynos542x: Move G3D subsystem clocks to its sub-CMU Marek Szyprowski
2019-10-23 7:46 ` Krzysztof Kozlowski
2019-10-23 13:03 ` 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=9b9d013d-3bbb-e9e9-b161-e885cb6b1c2f@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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox