[PATCH RFC 3/3] arm64: dts: qcom: x1e80100: Add ACD levels for GPU
Akhil P Oommen
quic_akhilpo at quicinc.com
Sat Oct 19 08:29:44 UTC 2024
On Thu, Oct 17, 2024 at 09:05:50AM +0200, Krzysztof Kozlowski wrote:
> On 17/10/2024 08:12, Akhil P Oommen wrote:
> > On Wed, Oct 16, 2024 at 09:50:04AM +0200, Krzysztof Kozlowski wrote:
> >> On 15/10/2024 21:35, Akhil P Oommen wrote:
> >>> On Mon, Oct 14, 2024 at 09:40:13AM +0200, Krzysztof Kozlowski wrote:
> >>>> On Sat, Oct 12, 2024 at 01:59:30AM +0530, Akhil P Oommen wrote:
> >>>>> Update GPU node to include acd level values.
> >>>>>
> >>>>> Signed-off-by: Akhil P Oommen <quic_akhilpo at quicinc.com>
> >>>>> ---
> >>>>> arch/arm64/boot/dts/qcom/x1e80100.dtsi | 11 ++++++++++-
> >>>>> 1 file changed, 10 insertions(+), 1 deletion(-)
> >>>>>
> >>>>> diff --git a/arch/arm64/boot/dts/qcom/x1e80100.dtsi b/arch/arm64/boot/dts/qcom/x1e80100.dtsi
> >>>>> index a36076e3c56b..e6c500480eb1 100644
> >>>>> --- a/arch/arm64/boot/dts/qcom/x1e80100.dtsi
> >>>>> +++ b/arch/arm64/boot/dts/qcom/x1e80100.dtsi
> >>>>> @@ -3323,60 +3323,69 @@ zap-shader {
> >>>>> };
> >>>>>
> >>>>> gpu_opp_table: opp-table {
> >>>>> - compatible = "operating-points-v2";
> >>>>> + compatible = "operating-points-v2-adreno";
> >>>>
> >>>> This nicely breaks all existing users of this DTS. Sorry, no. We are way
> >>>> past initial bringup/development. One year past.
> >
> > How do I identify when devicetree is considered stable? An arbitrary
> > time period doesn't sound like a good idea. Is there a general consensus
> > on this?
> >
> > X1E chipset is still considered under development at least till the end of this
> > year, right?
>
> Stable could be when people already get their consumer/final product
> with it. I got some weeks ago Lenovo T14s laptop and since yesterday
> working fine with Ubuntu:
> https://discourse.ubuntu.com/t/ubuntu-24-10-concept-snapdragon-x-elite/48800
>
> All chipsets are under development, even old SM8450, but we avoid
> breaking it while doing that.
>
I still have questions about the practicality especially in IoT/Auto chipsets,
but I will try to get it clarified when I face them.
I will go ahead and send out the v2 series addressing the suggestions.
-Akhil.
>
>
> Best regards,
> Krzysztof
>
More information about the dri-devel
mailing list