Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id CC39AC678D5 for ; Sat, 4 Mar 2023 21:45:12 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229616AbjCDVpL (ORCPT ); Sat, 4 Mar 2023 16:45:11 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40280 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229484AbjCDVpI (ORCPT ); Sat, 4 Mar 2023 16:45:08 -0500 Received: from mail-ed1-x532.google.com (mail-ed1-x532.google.com [IPv6:2a00:1450:4864:20::532]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C2DC2125B4 for ; Sat, 4 Mar 2023 13:45:06 -0800 (PST) Received: by mail-ed1-x532.google.com with SMTP id o15so23714291edr.13 for ; Sat, 04 Mar 2023 13:45:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20210112; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=WKDIxvFH4F3D/Bp8+BmLpjtlutHoc8KA5An4csidBcU=; b=jzS3yeCClEU5ic+r6pgQ/vQwrY4Lj324IPOIkZYoWfvdmucb1ln4sYfsza2nWDWTNL 4mtcMhMyNlIRWv24QYhcwEtOU12QAYKj9EURBj5bcbmpQoF5570sCwvVOR+IWU30DjI/ 7AB3YMigQcTKQX2rwSYrtfKZwOPcSK7sXlBMzB89QkV5CPJhzpYwTu0LTWwr1CPk5bfT 5fkm41zDUcAzcqfeaR4Sq3b9aKdO1oRkZ3f6dXusQwZ70heMW1IzC3n+O7Kpew8BPliH 4AQkZ6ptMn5c7dafr/RgoabPd0AAMGkJUl0j6IH8PTgxEdPCpRvcIzAKTKg/4oLKEwWd WXfw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=WKDIxvFH4F3D/Bp8+BmLpjtlutHoc8KA5An4csidBcU=; b=jFbmOm178PoFBnQoaAgaH5jagQrU3H0uHnDP2OLaARgDXEG4iY4R7n4Lx7HASeY9lr luMmhjdQBeQRo5pcNOwVrW1XZOvkbigNGA1YJJ66vn2aDe2WWbtH45hQvqa0Nd9NGJBe O/9eMuQW64eaWN7mulTiTZ7ms2tcaXWAFyX2sapCw8hv8Kh+4m6GMLSqvtEpeJVAPCfS V54r4nUclSpUnZwTUuA/H7d7DGmL8sSdummP3t3IJqcTMZZ8G0I1HXFlLZ/dg/gGd1ZF 9G0sWz57InsVksF8SgpM95TmdWGybdUJboKBo1kK73KJ8wyiAnqrkO81VETccIbKEY8O mQ0A== X-Gm-Message-State: AO0yUKX+F8vs50XgqtAvyEKW6yPM9DGG+WsGvRs+3vtZal9qMQc2fBOu CP5q6vIJbvjvpgWdQrDPhNHWxAktgPQWZywKiJQ= X-Google-Smtp-Source: AK7set9wY0tIW78yGxDw99q432fpv27SQCH8++tgi5/mw5cQNNLf7m3KivFDf11whC1GeXIRw82onTzmkovP2vSJ4lI= X-Received: by 2002:a17:906:f18f:b0:8af:2ad8:3453 with SMTP id gs15-20020a170906f18f00b008af2ad83453mr5871550ejb.6.1677966304797; Sat, 04 Mar 2023 13:45:04 -0800 (PST) MIME-Version: 1.0 References: <20230303123312.155164-1-christianshewitt@gmail.com> In-Reply-To: <20230303123312.155164-1-christianshewitt@gmail.com> From: Martin Blumenstingl Date: Sat, 4 Mar 2023 22:44:53 +0100 Message-ID: Subject: Re: [PATCH v2] drm/meson: fix 1px pink line on GXM when scaling video overlay To: Christian Hewitt Cc: Neil Armstrong , David Airlie , Daniel Vetter , Kevin Hilman , Jerome Brunet , dri-devel@lists.freedesktop.org, linux-amlogic@lists.infradead.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Mar 3, 2023 at 1:33=E2=80=AFPM Christian Hewitt wrote: > > Playing media with a resolution smaller than the crtc size requires the > video overlay to be scaled for output and GXM boards display a 1px pink > line on the bottom of the scaled overlay. Comparing with the downstream > vendor driver revealed VPP_DUMMY_DATA not being set [0]. > > Setting VPP_DUMMY_DATA prevents the 1px pink line from being seen. > > [0] https://github.com/endlessm/linux-s905x/blob/master/drivers/amlogic/a= mports/video.c#L7869 > > Fixes: bbbe775ec5b5 ("drm: Add support for Amlogic Meson Graphic Controll= er") > Suggested-by: Martin Blumenstingl > Signed-off-by: Christian Hewitt Acked-by: Martin Blumenstingl > --- > Change since v1: > This time I sent the right patch from the correct branch; the wording in > v1 is incorrect and the change to meson_registers.h is not required. Thanks Christian - I was about to ask whether you could isolate which part of the original patch fixes the issue, but you've been quicker :-)