On Wed, Aug 20, 2025 at 02:13:02PM -0300, Ariel D'Alessandro wrote: > Commit 14176e94bb35d ("arm64: dts: mediatek: mt8195: Fix ranges for jpeg
That commit is not in any upstream tree. > enc/decoder nodes") redefined jpeg encoder/decoder children node ranges. > Update the related device tree binding yaml definition to match > mediatek/mt8195.dtsi, as this is currently the only one using it. > > Signed-off-by: Ariel D'Alessandro <ariel.dalessan...@collabora.com> > --- > .../media/mediatek,mt8195-jpegdec.yaml | 31 ++++++++++--------- > .../media/mediatek,mt8195-jpegenc.yaml | 15 ++++----- > 2 files changed, 24 insertions(+), 22 deletions(-) > > diff --git > a/Documentation/devicetree/bindings/media/mediatek,mt8195-jpegdec.yaml > b/Documentation/devicetree/bindings/media/mediatek,mt8195-jpegdec.yaml > index e5448c60e3eb5..b1f3df258dc87 100644 > --- a/Documentation/devicetree/bindings/media/mediatek,mt8195-jpegdec.yaml > +++ b/Documentation/devicetree/bindings/media/mediatek,mt8195-jpegdec.yaml > @@ -36,7 +36,7 @@ properties: > > # Required child node: > patternProperties: > - "^jpgdec@[0-9a-f]+$": > + "^jpgdec@[0-9],[0-9a-f]+$": This is wrong unless 0-9 is a separate, distinct address (like a chip select #). Rob