From: Alyssa Rosenzweig <alyssa@collabora.com>
To: Robin Murphy <robin.murphy@arm.com>
Cc: Stephen Boyd <sboyd@kernel.org>,
Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com>,
linux-mediatek@lists.infradead.org,
Michael Turquette <mturquette@baylibre.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
Ikjoon Jang <ikjn@chromium.org>,
Chun-Jie Chen <chun-jie.chen@mediatek.com>,
Weiyi Lu <weiyi.lu@mediatek.com>,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Nick Fan <Nick.Fan@mediatek.com>,
Nicolas Boichat <drinkcat@chromium.org>,
Chen-Yu Tsai <wenst@chromium.org>
Subject: Re: [PATCH] clk: mediatek: Disable ACP to fix 3D on MT8192
Date: Thu, 20 Jan 2022 09:27:03 -0500 [thread overview]
Message-ID: <YelxN/zpdkukBBqy@maud> (raw)
In-Reply-To: <5d839338-6072-9c52-1893-2f804d937ea1@arm.com>
> We also already have SoC-specific GPU compatibles because even without
> experimental interconnect easter eggs, people integrate these IPs in fairly
> involved ways and there's a fair degree of variety. However unless we want
> to be super-strict it's also not too hard to simply assume that if we can
> find a "mediatek,mt8192-infracfg" syscon then we set the MT8192 magic bit
> within it, and if we can't then we don't.
We need a MT8192-specific compatible for the GPU anyway due to "unique"
power management requirements, this is why the MT8183 before it has a
specific GPU compatible. So I'm not worried about the compatible.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-01-20 14:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-10 18:13 [PATCH] clk: mediatek: Disable ACP to fix 3D on MT8192 Alyssa Rosenzweig
2022-01-14 2:08 ` Stephen Boyd
2022-01-14 13:23 ` Robin Murphy
2022-01-14 13:47 ` Alyssa Rosenzweig
2022-01-18 7:19 ` Chen-Yu Tsai
2022-01-18 15:01 ` Robin Murphy
2022-01-19 2:18 ` Stephen Boyd
2022-01-20 14:22 ` Robin Murphy
2022-01-20 14:27 ` Alyssa Rosenzweig [this message]
2022-02-15 10:44 ` AngeloGioacchino Del Regno
2022-02-15 15:21 ` Robin Murphy
2022-02-15 16:12 ` AngeloGioacchino Del Regno
2022-02-17 21:40 ` Stephen Boyd
2022-01-14 22:55 ` Stephen Boyd
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=YelxN/zpdkukBBqy@maud \
--to=alyssa@collabora.com \
--cc=Nick.Fan@mediatek.com \
--cc=alyssa.rosenzweig@collabora.com \
--cc=chun-jie.chen@mediatek.com \
--cc=drinkcat@chromium.org \
--cc=ikjn@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=mturquette@baylibre.com \
--cc=robin.murphy@arm.com \
--cc=sboyd@kernel.org \
--cc=weiyi.lu@mediatek.com \
--cc=wenst@chromium.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