Received: by 2002:a05:6a10:af89:0:0:0:0 with SMTP id iu9csp3359963pxb; Mon, 17 Jan 2022 18:33:52 -0800 (PST) X-Google-Smtp-Source: ABdhPJziLxSCbfMFJ9v/jFjX6n02F4XXtV1rARgeOKfgazFnKYLyBzS7XwOcjQP3J1VMEfF/SLJB X-Received: by 2002:a17:90a:de01:: with SMTP id m1mr37832849pjv.215.1642473232540; Mon, 17 Jan 2022 18:33:52 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1642473232; cv=none; d=google.com; s=arc-20160816; b=mQtowJKnsuuvcbmhzgU7pysUcbJSv1WgoCOWwOXa1mdENx27vb43eP3LOkzKJGcG7h Tj9ym7Q+oixJt0g7x4Xt5IC5wlwBAJ7oik+yvzlCqK/tdiIEeFClI5mugw2Tw+5pxagN uTbGGbnLto/kI0YPcD23DzVLp3vUIxrUkudfEDFT0wYLZj/woAlEs+hyj25wO3lOBTWe GVob5uL43dw2Fu6S5qPG8V3i5KaIk3qgIEbZ/rmsCDXBb4PLiaOUrzBc8F8rnwXskdAj lOqElW0UFM+hOEodQ1I8YnB4moWe5Te5LcbqD16q2nkLzbci1NoHBzhJfHxIIzXKghe7 a+Hg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:organization :from:references:cc:to:subject:dkim-signature; bh=iobZ9nIGQYOcCvMsLNiuSueXQIR4Q93XXCRE5G/Gobc=; b=m6w3fVLM7EYVQUoyVofMsjBn2VMHeWBE7VHiSAIa2f1eXtU5Gfnd2oEAlaQ2+Qh5h8 DmrH0Lv0h1zd+5Ln75tKxxJrV9xWXLAmHm8OS5aWZ2sohQPgVtQY/ZGn0Vq95Pc2H69g 7u3x8cSJM2z3w3+F/81l5/xYmdjohRo/B8MUJpl+DIJsfChYUaGenzLRpk4k6bUB5AnG YsLfdI6bDcc9TVwCWHHrTL9/a8EGJJkGU3ZSDEnAoeGUzazIsci8oE9bE4pURNpDXCwk rql7dSJVgp5l4svkekGQ3mATGDVitkc1vd5XiERkMl6lfeimUfTKz3FGUaMEDT2Rz2oc zPgw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@baylibre-com.20210112.gappssmtp.com header.s=20210112 header.b=uBbnoT68; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id f20si9659589pfv.34.2022.01.17.18.33.40; Mon, 17 Jan 2022 18:33:52 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@baylibre-com.20210112.gappssmtp.com header.s=20210112 header.b=uBbnoT68; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S240276AbiAQPME (ORCPT + 99 others); Mon, 17 Jan 2022 10:12:04 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:48108 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230202AbiAQPMD (ORCPT ); Mon, 17 Jan 2022 10:12:03 -0500 Received: from mail-wm1-x332.google.com (mail-wm1-x332.google.com [IPv6:2a00:1450:4864:20::332]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id DCCD3C061574 for ; Mon, 17 Jan 2022 07:12:02 -0800 (PST) Received: by mail-wm1-x332.google.com with SMTP id p1-20020a1c7401000000b00345c2d068bdso25084387wmc.3 for ; Mon, 17 Jan 2022 07:12:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=baylibre-com.20210112.gappssmtp.com; s=20210112; h=subject:to:cc:references:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=iobZ9nIGQYOcCvMsLNiuSueXQIR4Q93XXCRE5G/Gobc=; b=uBbnoT68ad0CaZ2z4c+QV0CuII+8J3rnGOJVehC4ySqxyK+ZWJj6ihSWXZhrEmH51E 24OHvfLpL0HjzFVLZvrDuS/fFnvQx74Uy2ZU0Z3UUsfOG2Dz08cB6KybWUvIeK5eDTxS phOal6YFDo8zXfOgYjULbSGpF3f2EtKSdgZMuq9JUJSzDHgKTZriArJHisUOk6/0U11e +jK3NfFEfW8GTVIIjSQ6/afnFAfcxP0bCfRKQFunIM2lJkqzcenA/nSnMLjho+hP+KfV 0euUq3vrdA2vZ+lnoNpvD+5AI2JJHRnhcFRwptzKPsqG8AtVikmwB3dcO2x7JVZBAUbs QCGQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:subject:to:cc:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=iobZ9nIGQYOcCvMsLNiuSueXQIR4Q93XXCRE5G/Gobc=; b=GnQprR+/yGxtZDNZFr9OvxoX8wfu/mUZngfAg+IFnX2F8qBOyaWBqBU1iAeDJivAeB 9dKtWK8Tcdpst2w1Ru5vuCPWzgzSKcOiAuFu2U/f2XXww01GgwgnkhHiTkKSTZCnk4RP T9+l3BjJsogHyiqC6/ZHnX52aUQgCvAfBKuytAaHvNL/4Zw9DPBDtA5DICJ6DMXqps1U ZclHNUMEMyZoyH2HmB12AU1xwB3N7drEVu3nxUbNaRUQg14ZmaC68F/cXQ3OcAGnsujo pzY7OzDglA6c47xFN05ee8Rz4axf3ItinIBen/mc6mBRinF9MXdMVCSlG4DblytUhKR7 S9LQ== X-Gm-Message-State: AOAM531MRHk8vPz7v5LTu58DiZy/TXeIyPm601w3eTjWjddyaHA+XEur CFAcVBGHL1RVlMzbYTtlvmLTjw== X-Received: by 2002:a05:600c:3b9a:: with SMTP id n26mr14317988wms.88.1642432321271; Mon, 17 Jan 2022 07:12:01 -0800 (PST) Received: from ?IPv6:2001:861:44c0:66c0:c004:9fe1:fbda:2d0c? ([2001:861:44c0:66c0:c004:9fe1:fbda:2d0c]) by smtp.gmail.com with ESMTPSA id p62sm13589984wmp.10.2022.01.17.07.11.59 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 17 Jan 2022 07:12:00 -0800 (PST) Subject: Re: [PATCH] drm/bridge: dw-hdmi: use safe format when first in bridge chain To: Biju Das , "robert.foss@linaro.org" Cc: "Laurent.pinchart@ideasonboard.com" , "jonas@kwiboo.se" , "jernej.skrabec@gmail.com" , "dri-devel@lists.freedesktop.org" , "linux-kernel@vger.kernel.org" , "kieran.bingham@ideasonboard.com" , Kieran Bingham References: <20220117141750.1182223-1-narmstrong@baylibre.com> From: Neil Armstrong Organization: Baylibre Message-ID: <89d47094-e23f-7c36-7cc8-c261a921c2ab@baylibre.com> Date: Mon, 17 Jan 2022 16:11:59 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 17/01/2022 15:27, Biju Das wrote: > Hi Neil, > > Thanks for the patch > >> Subject: [PATCH] drm/bridge: dw-hdmi: use safe format when first in bridge >> chain >> >> When the dw-hdmi bridge is in first place of the bridge chain, this means >> there is now way to select an input format of the dw-hdmi HW component. >> >> Since introduction of display-connector, negociation was broken since the >> dw-hdmi negociation code only worked when the dw-hdmi bridge was in last >> position of the bridge chain or behind another bridge also supporting >> input & output format negociation. >> >> Commit 0656d1285b79 ("drm/bridge: display-connector: implement bus fmts >> callbacks") was introduced to make negociation work again by making >> display-connector act as a pass-through concerning input & output format >> negociation. >> >> But in the case were the dw-hdmi was single in the bridge chain, for >> example on Renesas SoCs, with the disply-connector bridge the dw-hdmi is >> no more single, breaking output format. >> >> Reported-by: Biju Das >> Bisected-by: Kieran Bingham >> Tested-by: Kieran Bingham >> Fixes: 0656d1285b79 ("drm/bridge: display-connector: implement bus fmts >> callbacks"). >> Signed-off-by: Neil Armstrong >> --- >> drivers/gpu/drm/bridge/synopsys/dw-hdmi.c | 9 +++++++-- >> 1 file changed, 7 insertions(+), 2 deletions(-) >> >> diff --git a/drivers/gpu/drm/bridge/synopsys/dw-hdmi.c >> b/drivers/gpu/drm/bridge/synopsys/dw-hdmi.c >> index 54d8fdad395f..9f2e1cac0ae2 100644 >> --- a/drivers/gpu/drm/bridge/synopsys/dw-hdmi.c >> +++ b/drivers/gpu/drm/bridge/synopsys/dw-hdmi.c >> @@ -2551,8 +2551,9 @@ static u32 >> *dw_hdmi_bridge_atomic_get_output_bus_fmts(struct drm_bridge *bridge, >> if (!output_fmts) >> return NULL; >> >> - /* If dw-hdmi is the only bridge, avoid negociating with ourselves >> */ >> - if (list_is_singular(&bridge->encoder->bridge_chain)) { >> + /* If dw-hdmi is the first or only bridge, avoid negociating with >> ourselves */ >> + if (list_is_singular(&bridge->encoder->bridge_chain) || >> + list_is_first(&bridge->chain_node, >> +&bridge->encoder->bridge_chain)) { >> *num_output_fmts = 1; >> output_fmts[0] = MEDIA_BUS_FMT_FIXED; >> >> @@ -2673,6 +2674,10 @@ static u32 >> *dw_hdmi_bridge_atomic_get_input_bus_fmts(struct drm_bridge *bridge, >> if (!input_fmts) >> return NULL; >> >> + /* If dw-hdmi is the first bridge fall-back to safe output format */ >> + if (list_is_first(&bridge->chain_node, &bridge->encoder- >>> bridge_chain)) >> + output_fmt = MEDIA_BUS_FMT_FIXED; >> + > > Based on my debugging, this looks redundant, as get_output_bus_fmts already sets output_fmt = MEDIA_BUS_FMT_FIXED, > And *num_output_fmts = 1, so the function parameter output_fmt in input_bus_fmts will have MEDIA_BUS_FMT_FIXED > And no need to override output_fmt value. I may be wrong here. You're right, I added this in case another bridge than display-connector is used, but in fact it should instead check if first bridge of the chain and output_fmt == MEDIA_BUS_FMT_RGB888_1X24 || output_fmt == MEDIA_BUS_FMT_FIXED otherwise return an error. I'll send it separately since it's out of the scope of the issue fixed. Neil > > Regards, > Biju > >> switch (output_fmt) { >> /* If MEDIA_BUS_FMT_FIXED is tested, return default bus format */ >> case MEDIA_BUS_FMT_FIXED: >> -- >> 2.25.1 >