From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: Chris Healy <cphealy@gmail.com>, dmitry.baryshkov@linaro.org
Cc: airlied@gmail.com, Daniel Vetter <daniel@ffwll.ch>,
DRI mailing list <dri-devel@lists.freedesktop.org>,
freedreno <freedreno@lists.freedesktop.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
quic_abhinavk@quicinc.com, Rob Clark <robdclark@gmail.com>,
sean@poorly.run, Marek Vasut <marex@denx.de>
Subject: Re: [PATCH 1/5] drm/msm/adreno: Use OPP for every GPU generation
Date: Mon, 27 Feb 2023 11:45:15 +0100 [thread overview]
Message-ID: <3d951b70-ecea-c97c-8a2e-72ca6b1a2bf7@linaro.org> (raw)
In-Reply-To: <CAFXsbZqnstOLFBrVVa7aFLSGCPNj4VkjExqq1XUoRdUUuBKdog@mail.gmail.com>
On 24.02.2023 17:56, Chris Healy wrote:
> I may be missing something, but looking at the code path for a2xx,
> it's not clear to me how this would work with SoCs with a2xx that
> don't support 200MHz for GPU frequency. For example, the NXP i.MX51
> requires the A205 GPU to run at 166MHz while the NXP i.MX53 requires
> the A205 GPU to run at 200MHz.
This is something outside the scope of this patch, I feel like.
If I'm reading the code correctly, the driver always assumed 200 MHz
for non-pwrlevels and non-OPP targets before this patch, and this
patch is meant to bring no difference in the rates selected.
Konrad
next prev parent reply other threads:[~2023-02-27 10:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 16:56 [PATCH 1/5] drm/msm/adreno: Use OPP for every GPU generation Chris Healy
2023-02-27 10:45 ` Konrad Dybcio [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-22 21:47 [PATCH 0/5] OPP and devfreq for all Adrenos Konrad Dybcio
2023-02-22 21:47 ` [PATCH 1/5] drm/msm/adreno: Use OPP for every GPU generation Konrad Dybcio
2023-02-22 22:38 ` Dmitry Baryshkov
2023-02-22 22:40 ` Konrad Dybcio
2023-02-22 23:16 ` Dmitry Baryshkov
2023-02-23 1:02 ` Konrad Dybcio
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=3d951b70-ecea-c97c-8a2e-72ca6b1a2bf7@linaro.org \
--to=konrad.dybcio@linaro.org \
--cc=airlied@gmail.com \
--cc=cphealy@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marex@denx.de \
--cc=quic_abhinavk@quicinc.com \
--cc=robdclark@gmail.com \
--cc=sean@poorly.run \
/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