Received: by 2002:a05:6358:4e97:b0:b3:742d:4702 with SMTP id ce23csp588747rwb; Thu, 18 Aug 2022 08:46:49 -0700 (PDT) X-Google-Smtp-Source: AA6agR6mnlPDhRS7Sz7qdLbfdXrsQV9xdg5Vx/43AjFvJ/vKPdQbx/UV11pFzfdTurKv5GYOIEcM X-Received: by 2002:a17:906:730c:b0:730:da74:3453 with SMTP id di12-20020a170906730c00b00730da743453mr2234845ejc.270.1660837609498; Thu, 18 Aug 2022 08:46:49 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1660837609; cv=none; d=google.com; s=arc-20160816; b=YasPVg4eDxfRlxRveF8gicrK7lbFnPSUo0o2AVeLw6Eb66FN/7nOV7mXpDWA1Jsux7 KlgjmnWzCUN0D6ij8k4kHADHdOg1uY3Qx0fIbjdXKFmVLFMQAbStap94W2ELG0cJ2zAG kuIunSSHqlIEGVdAb0CaEWWhv37q6nHSO4NszHdTsvnxjKGTI7O+n+fa17qYlQsZDYW6 Xs2Xtg7SvwCr3gotVu8Txz46dH8cFckKfdfMHfSYiEIHvpi/mSBij8MIngXeYI2W+cNA xBUiNBCMLRjOBiObj4TYFYYI4xHOaRuc2xL9ab7GMOlEBCAJgenUJIkWT/WDmWE3P2ep KpXg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version; bh=T9A28BLo2B0nLzuZtZ0Ejl0zLIHzqGciO6GeX7JAOrM=; b=Jl25vLVFlcHS1eQQZptlUxSDGyzqALPS2c+1OUFwU79JVlkTQG5/4I/+7OqbFeNBl+ crEQKZmK2GevZFF5yEy1in7ZwyWkSO6VEWuLUJuNRoNqW+hLZUAlK+SC4TV3IZ/K0l6G VArN4fp5txcRrBOVbzeQ8LUzSTVaQfkLZbUE7i7HR5XUssPKrHmAyCbN6bJ4JLfE6KTU VS4tnTNes+IHqa3TPS7P3wmDfB8oEj38RozNCPkTwM0JsDY0pJfgeuS96/E7FAciPjqY NO1mOo70gbPDp7N7EDUnmL53mL1+OWkm1wzY4BF/qi5/FB9mXz30LbhFirNpZUFbArpB e2Cg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id y65-20020a50bb47000000b0043de73e065bsi1436498ede.269.2022.08.18.08.46.21; Thu, 18 Aug 2022 08:46:49 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1343985AbiHRPVM (ORCPT + 99 others); Thu, 18 Aug 2022 11:21:12 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36300 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1344315AbiHRPU7 (ORCPT ); Thu, 18 Aug 2022 11:20:59 -0400 Received: from mail-qt1-f179.google.com (mail-qt1-f179.google.com [209.85.160.179]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 81FD766123 for ; Thu, 18 Aug 2022 08:20:58 -0700 (PDT) Received: by mail-qt1-f179.google.com with SMTP id y18so1346291qtv.5 for ; Thu, 18 Aug 2022 08:20:58 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc; bh=T9A28BLo2B0nLzuZtZ0Ejl0zLIHzqGciO6GeX7JAOrM=; b=lgBc9DoW7EKRPuC+cP42dPk4UvU6Rik/GYPaQkHEIMFMLQU7i46UltqammHm4TmTXZ QATESz3amJncCUjeqAT9Do6TWDXwqiMPd9XrUXamzmjTsbWxP6vqKwo/etCgAEHdIRlf u83OgE3fAkA0to6afaCzRitL8qC5UIkRgBzv+OprfYqJybV73d9wiZ+JIPS4CMGzd09M tp32YIrlI0SuFUpKReaJJoRRQFWVvNAjCwN24Ohm87AOXRrqF/eJDaLsp1t88uubBJE5 454GjQf9Y5gq+03m8mAtE44AUp+x1Xu0bBH3fgSADVq3Mfy4BSoaRrJx3fyrhciZ16fy PV8g== X-Gm-Message-State: ACgBeo0AW1GFff107iYjSNBETzuBJEVBcQyBbX/GWisNP8Xl20veN96C oALFnRpB7QbmbGmyTQriFQZlHCvTZFwExg== X-Received: by 2002:a05:622a:6027:b0:343:5691:93de with SMTP id he39-20020a05622a602700b00343569193demr3020500qtb.165.1660836057268; Thu, 18 Aug 2022 08:20:57 -0700 (PDT) Received: from mail-yw1-f182.google.com (mail-yw1-f182.google.com. [209.85.128.182]) by smtp.gmail.com with ESMTPSA id v16-20020a05620a0f1000b006b97151d2b3sm1787602qkl.67.2022.08.18.08.20.55 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 18 Aug 2022 08:20:56 -0700 (PDT) Received: by mail-yw1-f182.google.com with SMTP id 00721157ae682-3376851fe13so16492137b3.6 for ; Thu, 18 Aug 2022 08:20:55 -0700 (PDT) X-Received: by 2002:a25:250b:0:b0:68f:425b:3ee0 with SMTP id l11-20020a25250b000000b0068f425b3ee0mr3357401ybl.89.1660836055065; Thu, 18 Aug 2022 08:20:55 -0700 (PDT) MIME-Version: 1.0 References: <20220816141116.5nuszmilqv2exdb3@houat> <20220816154956.pkdpxmmw27mia5ix@houat> <20220817074710.w4c4xwj7edly2b5p@houat> <20220817111454.pn2iltvyo2drebq7@houat> <20220817131854.jwmhqvhfhp77bbr3@houat> <20220818145436.vqojnhmvhjxdzooe@houat> In-Reply-To: <20220818145436.vqojnhmvhjxdzooe@houat> From: Geert Uytterhoeven Date: Thu, 18 Aug 2022 17:20:42 +0200 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v1 05/35] drm/connector: Add TV standard property To: Maxime Ripard Cc: Jernej Skrabec , Martin Blumenstingl , Chen-Yu Tsai , Philipp Zabel , Jerome Brunet , Samuel Holland , Thomas Zimmermann , Daniel Vetter , Emma Anholt , David Airlie , Maarten Lankhorst , =?UTF-8?Q?Noralf_Tr=C3=B8nnes?= , Kevin Hilman , Neil Armstrong , linux-sunxi@lists.linux.dev, Linux Kernel Mailing List , Phil Elwell , Mateusz Kwiatkowski , Linux ARM , Dave Stevenson , "open list:ARM/Amlogic Meson..." , DRI Development , Dom Cobley Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-1.4 required=5.0 tests=BAYES_00, FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM,HEADER_FROM_DIFFERENT_DOMAINS, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE, SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Maxime, On Thu, Aug 18, 2022 at 4:54 PM Maxime Ripard wrote: > On Wed, Aug 17, 2022 at 04:04:24PM +0200, Geert Uytterhoeven wrote: > > On Wed, Aug 17, 2022 at 3:19 PM Maxime Ripard wrote: > > > On Wed, Aug 17, 2022 at 03:05:52PM +0200, Geert Uytterhoeven wrote: > > > > On Wed, Aug 17, 2022 at 1:15 PM Maxime Ripard wrote: > > > > > On Wed, Aug 17, 2022 at 10:35:07AM +0200, Geert Uytterhoeven wrote: > > > > > > On Wed, Aug 17, 2022 at 9:47 AM Maxime Ripard wrote: > > > > > > > On Wed, Aug 17, 2022 at 09:31:18AM +0200, Geert Uytterhoeven wrote: > > > > > > > > On Tue, Aug 16, 2022 at 5:50 PM Maxime Ripard wrote: > > > > > > > > > On Tue, Aug 16, 2022 at 04:43:44PM +0200, Geert Uytterhoeven wrote: > > > > > > > > > > > > > > Either you have to add them here (e.g. "hd720p50" and "hd720p60"), or > > > > > > > > > > > > > > handle them through "@". The latter would impact "[PATCH v1 > > > > > > > > > > > > > > 09/35] drm/modes: Move named modes parsing to a separate function", as > > > > > > > > > > > > > > currently a named mode and a refresh rate can't be specified both. > > > > > > > > > > > > > > > > > > > > > > > > > > I think the former would make more sense. It simplifies a bit the > > > > > > > > > > > > > parser, and we're going to use a named mode anyway. > > > > > > > > > > > > > > > > > > > > > > > > > > > As "[PATCH v1 34/35] drm/modes: Introduce the tv_mode property as a > > > > > > > > > > > > > > command-line option" uses a separate "tv_mode" option, and not the main > > > > > > > > > > > > > > mode name, I think you want to add them here. > > > > > > > > > > > > > > > > > > > > > > > > > > It's a separate story I think, we could have a named mode hd720p50, > > > > > > > > > > > > > which would be equivalent to 1280x720,tv_mode=hd720p > > > > > > > > > > > > > > > > > > > > > > > > So where's the field rate in "1280x720,tv_mode=hd720p"? > > > > > > > > > > > > > > > > > > > > > > Yeah, sorry I meant 1280x720@50,tv_mode=hd720p > > > > > > > > > > > > > > > > > > > > Above you said "I think the former would make more sense", so that > > > > > > > > > > should be "1280x720,tv_mode=hd720p50"? > > > > > > > > > > > > > > > > > > No, 720p at 50Hz would be either hd720p50 or 1280x720@50,tv_mode=hd720p > > > > > > > > > and 60Hz would be hd720p60 or 1280x720@60,tv_mode=hd720p > > > > > > > > > > > > > > > > I disagree: hd720p50 and hd720p60 are different TV modes. > > > > > > > > > > > > > > I agree, and I don't see how that command-line doesn't express that? > > > > > > > > > > > > Oh, I see what you mean: yes, it expresses that. > > > > > > But it is inconsistent with the NTSC/PAL/SECAM/hd{480,576}[ip] modes, > > > > > > where the TV mode specifies both number of lines and frame rate. > > > > > > > > > > Only if we're using a named mode, and naming is hard :) > > > > > > > > That's not true: "640x480,tv_mode=PAL-N" would give me a mode with > > > > 625 lines and 25 frames/s, "640x480,tv_mode=PAL-M" would give me a > > > > mode with 525 lines and 30 frames/s. > > > > > > In that series, "640x480,tv_mode=PAL-N" would be rejected as invalid: > > > > > > https://lore.kernel.org/dri-devel/20220728-rpi-analog-tv-properties-v1-14-3d53ae722097@cerno.tech/ > > > > It would become supported once the ideas from thread "[PATCH v1 04/35] > > drm/modes: Introduce 480i and 576i modes" are implemented... > > Indeed, but I'm still not sure what your concern is here. > "640x480,tv_mode=PAL-N" and "640x480,tv_mode=PAL-M" are both fairly > obvious. > > You were initially saying that you had concern over the inconsistency of > NTSC/PAL/SECAM where the TV mode would specify a number of lines and > frame rate, but hd720p50 also specifies a number of line and frame rate? My concern is that you want to call the TV mode "hd720p", which does not dictate the frame rate. I would like to have both "720p50" and "720p60", as they do dictate the frame rate, like all the non-hd modes. Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds