From: Alexandre Mergnat <amergnat@baylibre.com>
To: Eugen Hristev <eugen.hristev@collabora.com>,
matthias.bgg@gmail.com, angelogioacchino.delregno@collabora.com
Cc: allen-kh.cheng@mediatek.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH] arm64: dts: mediatek: mt8186: fix clock names for power domains
Date: Tue, 10 Oct 2023 14:31:48 +0200 [thread overview]
Message-ID: <ea2b3e42-9bf8-489c-b2d9-584ee2d909f4@baylibre.com> (raw)
In-Reply-To: <20231005103041.352478-1-eugen.hristev@collabora.com>
Reviewed-by: Alexandre Mergnat <amergnat@baylibre.com>
On 05/10/2023 12:30, Eugen Hristev wrote:
> Clocks for each power domain are split into big categories: pd clocks
> and subsys clocks. According to the binding, all clocks which have a
> dash '-' in their name are treated as subsys clocks, and must be placed
> at the end of the list. The other clocks which are pd clocks must come
> first. Fixed the naming and the placing of all clocks in the power
> domains. For the avoidance of doubt, prefixed all subsys clocks with the
> 'subsys' prefix. The binding does not enforce strict clock names, the
> driver uses them in bulk, only making a difference for pd clocks vs
> subsys clocks. The above problem appears to be trivial, however, it
> leads to incorrect power up and power down sequence of the power
> domains, because some clocks will be mistakenly taken for subsys clocks
> and viceversa. One consequence is the fact that if the DIS power domain
> goes power down and power back up during the boot process, when it comes
> back up, there are still transactions left on the bus which makes the
> display inoperable. Some of the clocks for the DIS power domain were
> wrongly using '_' instead of '-', which again made these clocks being
> treated as pd clocks instead of subsys clocks.
--
Regards,
Alexandre
next prev parent reply other threads:[~2023-10-10 12:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-05 10:30 Eugen Hristev
2023-10-05 10:42 ` Chen-Yu Tsai
2023-10-05 12:41 ` AngeloGioacchino Del Regno
2023-10-10 12:31 ` Alexandre Mergnat [this message]
2023-11-29 13:27 ` AngeloGioacchino Del Regno
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=ea2b3e42-9bf8-489c-b2d9-584ee2d909f4@baylibre.com \
--to=amergnat@baylibre.com \
--cc=allen-kh.cheng@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=eugen.hristev@collabora.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
/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
all inboxes | Powered by JetHome®