From: Petr Vorel <pvorel@suse.cz>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Konrad Dybcio <konrad.dybcio@linaro.org>,
Bjorn Andersson <andersson@kernel.org>,
linux-arm-msm@vger.kernel.org, Petr Vorel <petr.vorel@gmail.com>,
Martin Botka <martin.botka@somainline.org>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Aboothahir U <aboothahirpkd@gmail.com>,
Alexey Minnekhanov <alexeymin@postmarketos.org>
Subject: Re: [PATCH v2 1/1] arm64: defconfig: Enable SDM660 Clock Controllers
Date: Thu, 7 Dec 2023 22:48:09 +0100 [thread overview]
Message-ID: <20231207214809.GA302808@pevik> (raw)
In-Reply-To: <CAA8EJpqmvKQHzPtzseCJ=y0GwP5Y5H_cR4RpjU97y=8q=b-zDQ@mail.gmail.com>
Hi all,
[ Cc Alexey Minnekhanov ]
> On Thu, 7 Dec 2023 at 21:26, Konrad Dybcio <konrad.dybcio@linaro.org> wrote:
> > On 12/7/23 19:54, Dmitry Baryshkov wrote:
> > > On Thu, 7 Dec 2023 at 18:27, Bjorn Andersson <andersson@kernel.org> wrote:
> > >> On Wed, Nov 15, 2023 at 09:53:18PM +0100, Petr Vorel wrote:
> > >>> From: Petr Vorel <petr.vorel@gmail.com>
> > >>> Enable support for the multimedia clock controller on SDM660 devices
> > >>> and graphics clock controller on SDM630/636/660 devices.
> > >>> Signed-off-by: Petr Vorel <petr.vorel@gmail.com>
> > >>> ---
> > >>> Changes v1->v2:
> > >>> * added commit message (not just the subject)
> > >>> NOTE motivation for this is that some not yet mainlined DTS already use
> > >>> both:
> > >>> https://github.com/sdm660-mainline/linux/blob/sdm660-next-stable/arch/arm64/boot/dts/qcom/sdm636-asus-x00td.dts
> > >>> Kind regards,
> > >>> Petr
> > >>> arch/arm64/configs/defconfig | 2 ++
> > >>> 1 file changed, 2 insertions(+)
> > >>> diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
> > >>> index acba803835b9..10a098aa8b1b 100644
> > >>> --- a/arch/arm64/configs/defconfig
> > >>> +++ b/arch/arm64/configs/defconfig
> > >>> @@ -1235,6 +1235,8 @@ CONFIG_SC_GCC_8180X=y
> > >>> CONFIG_SC_GCC_8280XP=y
> > >>> CONFIG_SC_GPUCC_8280XP=m
> > >>> CONFIG_SC_LPASSCC_8280XP=m
> > >>> +CONFIG_SDM_MMCC_660=m
> > >>> +CONFIG_SDM_GPUCC_660=y
> > >> I'd expect the GPU clock controller to be a module, can you please
> > >> clarify why it needs to be builtin?
> > > To allow the display to be enabled early enough?
Yes, I feared that it would not work when it's a module.
Also, we already have CONFIG_SDM_GPUCC_845=y.
I suppose I'm wrong, but I don't have any sdm660 device to test that.
BTW people who are using this use both as builtin (CONFIG_SDM_MMCC_660) [2], but
maybe it's just to help testing (boot the kernel and don't bother with modules).
@Alexey, you added sdm660_defconfig [2], do you have sdm660 based device to test
if both options work well when compiled as modules?
> > That sounds like a terrible bug in drm/msm.. Display should
> > be wholly separate from Adreno.
> Let me quote Rob's email ([1])
> Userspace does have better support for split display/gpu these days
> than it did when drm/msm was first merged. It _might_ just work if
> one device only advertised DRIVER_RENDER and the other
> MODESET/ATOMIC.. but I'd be a bit concerned about breaking things. I
> guess you could try some sort of kconfig knob to have two "msm"
> devices and see what breaks, but I'm a bit skeptical that we could
> make this the default anytime soon.
Thanks for pointing out this.
Kind regards,
Petr
> [1] https://lore.kernel.org/dri-devel/CAF6AEGs89FRmFsENLkP-Dg1ZJN2LzCfxY2-+do9jH9b8L-XZxg@mail.gmail.com/
[2] https://github.com/sdm660-mainline/linux/blob/sdm660-next-stable/arch/arm64/configs/sdm660_defconfig#L504-L505
next prev parent reply other threads:[~2023-12-07 21:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-15 20:53 [PATCH v2 1/1] arm64: defconfig: Enable SDM660 Clock Controllers Petr Vorel
2023-11-15 21:40 ` Martin Botka
2023-12-07 16:30 ` Bjorn Andersson
2023-12-07 18:54 ` Dmitry Baryshkov
2023-12-07 19:26 ` Konrad Dybcio
2023-12-07 20:50 ` Dmitry Baryshkov
2023-12-07 21:48 ` Petr Vorel [this message]
2023-12-09 3:08 ` Bjorn Andersson
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=20231207214809.GA302808@pevik \
--to=pvorel@suse.cz \
--cc=aboothahirpkd@gmail.com \
--cc=alexeymin@postmarketos.org \
--cc=andersson@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=dmitry.baryshkov@linaro.org \
--cc=konrad.dybcio@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=martin.botka@somainline.org \
--cc=petr.vorel@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;
as well as URLs for NNTP newsgroup(s).