[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20251227-overjoyed-illustrious-snail-9323e9@quoll>
Date: Sat, 27 Dec 2025 13:34:30 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Jianhua Lin <jianhua.lin@...iatek.com>
Cc: mchehab@...nel.org, robh@...nel.org, krzk+dt@...nel.org,
conor+dt@...nel.org, matthias.bgg@...il.com, angelogioacchino.delregno@...labora.com,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org, linux-media@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-mediatek@...ts.infradead.org,
Project_Global_Chrome_Upstream_Group@...iatek.com, sirius.wang@...iatek.com, vince-wl.liu@...iatek.com,
jh.hsu@...iatek.com
Subject: Re: [PATCH v2 1/4] arm64: dts: mt8188: update JPEG encoder/decoder
compatible
On Wed, Dec 24, 2025 at 11:17:18AM +0800, Jianhua Lin wrote:
> The JPEG encoder and decoder of MT8188 share the same architecture
> and features as those of MT8189, both use a 34-bit iova
> address-space (16GB) and a single clock configuration.
>
> Previously, MT8188 was incorrectly defined alongside SoCs with 32-bit
> iova address-space (4GB), such as "mediatek,mt2701-jpgdec" and
> "mediatek,mtk-jpgenc". This mismatch results in an ABI break,
How this mismatch can result in ABI break?
> as MT8188 cannot function correctly under the 32-bit iova
> address-space (4GB) configuration.
Do you understand what is an ABI break? This commit is the ABI break.
Best regards,
Krzysztof
Powered by blists - more mailing lists