From mboxrd@z Thu Jan 1 00:00:00 1970 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 gabe.freedesktop.org (gabe.freedesktop.org [131.252.210.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 9445CCA0FFE for ; Sat, 30 Aug 2025 07:30:15 +0000 (UTC) Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id 0B82C10E239; Sat, 30 Aug 2025 07:30:15 +0000 (UTC) Authentication-Results: gabe.freedesktop.org; dkim=pass (2048-bit key; unprotected) header.d=fooishbar.org header.i=@fooishbar.org header.b="XSY91wXb"; dkim-atps=neutral Received: from mail-qt1-f178.google.com (mail-qt1-f178.google.com [209.85.160.178]) by gabe.freedesktop.org (Postfix) with ESMTPS id ADE4C10E240 for ; Sat, 30 Aug 2025 07:30:13 +0000 (UTC) Received: by mail-qt1-f178.google.com with SMTP id d75a77b69052e-4b2f4ac4786so20839801cf.1 for ; Sat, 30 Aug 2025 00:30:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fooishbar.org; s=google; t=1756539012; x=1757143812; darn=lists.freedesktop.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=u5ZG8/bv7fEyY7/sBaZXohrNcXIrZPRq+HcTim4TiEo=; b=XSY91wXb1yJ6X+wUjuEzetW2VA1JfudmCQaj5WOgxbDx7iUpT7M96X5qNHDxNNnI4l 2JOzLQ5lZOPEW4SDuI0yTz5LqVqKZo+mEetREEwRcizSbElOgSufvWwmQYThoAgRUu+Y jLz7id2v4nkkTYqJL4LEhJVdaIMdFf0wdLVNoAvuDonnuXC8jY+dMkxgFxyL92PKWmma kK6jV1QlWzZTbAhny8WeXz+QTe1RHiiv12yk0GIDMARHnC7QjwKQTE66+zbgZL9PwAs2 r8IFt2Oia7LuXy/akisi1R2jvDOj1b9oo0sxgaDC6os40FrlIROzj9XlSCv8IXJgzY/Y +/nw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1756539012; x=1757143812; h=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=u5ZG8/bv7fEyY7/sBaZXohrNcXIrZPRq+HcTim4TiEo=; b=Dk84nSaN5TEobm//O+UJ0yURphDQ9LHWydQxFu1xF98TYcwaMElVloLFv33rdR2+vt 8iY2zR3lxMmL6EwSLLIwOZWqddmOEaYttRIWURTv5PeSp6iMyWqgKDEeIP4/e49vsXOo 2wVgfWrWFK1uC+33Qevn4fj8M9aszqWH6PTHOTxgmFGJCuQYWL87LT/H1iaRRRZ/rya0 mbJjFU4sVlLr7igkUV+wrl21tkMK7COjtwDHj2BJZnJTMMfAN6lQM6rJm4yYcVfwKr48 /7lRH5o7Ex8/nVgcUD9xn2zRPIDYRcC1MojhO+6F9KtvjVbLQp4zFMj1osQ0no3uqOoV IniA== X-Forwarded-Encrypted: i=1; AJvYcCUb68dUZbuQCoyUx/Kk5KlBcVZp4bnv6wp2khLsuisA4ntrMPY60I2C8bjPxkX/oEytSISLDbHf2TY=@lists.freedesktop.org X-Gm-Message-State: AOJu0YzXwKFmaCz9MYFA3vWEdt28/D/Rg406+NCNcOvSwsJALaS9ZYVw a0YI5DhLyZQQMJIeNK+eaennDh1/XvCaj8ip723qvg3rpkkR65SdfTtD79rwAXOGZvtGW/ptfPA OjK59rgAF2yrM48VSZ2FC/56jLyv1lG6dmKbZwmBD9g== X-Gm-Gg: ASbGncv+SwvNeVOOwp9dKRJ21WzUDuPuw8cWkuyytgdid1h50X//3lmgzhCEYP7ecZO rsvEFzY0vVNf+AAspMpBokvwW1eU4HUrd9QhpLo3lsGygs9LYGRGzJwuP3JBf9dy0Upm7HH0QA3 /eGiEJYNLWt0DERN6DxPIAs6zTIlAeiC5exuWN8pk6wY8xntsBs8iSD4mo3YJrUQt39zNATqeSN PtA9jthU4b8G2R9 X-Google-Smtp-Source: AGHT+IEoXuFZJwCV9cwGNvRYz37SGk7fTBsYXDUKkjm0VNio3cHCVlLucdjG7nkDJhE227CIqVsjn4jhHmK64RhHXes= X-Received: by 2002:ac8:5a12:0:b0:4b2:d607:16cb with SMTP id d75a77b69052e-4b31d855a89mr14707801cf.22.1756539012519; Sat, 30 Aug 2025 00:30:12 -0700 (PDT) MIME-Version: 1.0 References: <20250830-drm-limit-infoframes-v3-0-32fcbec4634e@oss.qualcomm.com> In-Reply-To: <20250830-drm-limit-infoframes-v3-0-32fcbec4634e@oss.qualcomm.com> From: Daniel Stone Date: Sat, 30 Aug 2025 09:30:01 +0200 X-Gm-Features: Ac12FXwherP7pCCw1eIolUuD4CaoGI8lRnTYIDVTJZ8XE8BvqysFq5xqSgK9g3A Message-ID: Subject: Re: [PATCH v3 00/11] drm/connector: hdmi: limit infoframes per driver capabilities To: Dmitry Baryshkov Cc: Andrzej Hajda , Neil Armstrong , Robert Foss , Laurent Pinchart , Jonas Karlman , Jernej Skrabec , Maarten Lankhorst , Maxime Ripard , Thomas Zimmermann , David Airlie , Simona Vetter , Sandy Huang , =?UTF-8?Q?Heiko_St=C3=BCbner?= , Andy Yan , Chen-Yu Tsai , Samuel Holland , Dave Stevenson , =?UTF-8?B?TWHDrXJhIENhbmFs?= , Raspberry Pi Kernel Maintenance , Liu Ying , Rob Clark , Dmitry Baryshkov , Abhinav Kumar , Jessica Zhang , Sean Paul , Marijn Suijten , dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-rockchip@lists.infradead.org, linux-sunxi@lists.linux.dev, linux-arm-msm@vger.kernel.org, freedreno@lists.freedesktop.org Content-Type: text/plain; charset="UTF-8" X-BeenThere: dri-devel@lists.freedesktop.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Direct Rendering Infrastructure - Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" Hi Dmitry, On Sat, 30 Aug 2025 at 02:23, Dmitry Baryshkov wrote: > It's not uncommon for the particular device to support only a subset of > HDMI InfoFrames. It's not a big problem for the kernel, since we adopted > a model of ignoring the unsupported Infoframes, but it's a bigger > problem for the userspace: we end up having files in debugfs which do > mot match what is being sent on the wire. > > Sort that out, making sure that all interfaces are consistent. Thanks for the series, it's a really good cleanup. I know that dw-hdmi-qp can support _any_ infoframe, by manually packing it into the two GHDMI banks. So the supported set there is 'all of the currently well-known ones, plus any two others, but only two and not more'. I wonder if that has any effect on the interface you were thinking about for userspace? Cheers, Daniel