Received: by 2002:a6b:500f:0:0:0:0:0 with SMTP id e15csp4204081iob; Sun, 8 May 2022 06:10:15 -0700 (PDT) X-Google-Smtp-Source: ABdhPJw8b7Jm36JnIov33IAhG8vrjZxPBX1g3UL9U/v29OL1tta9mvIlgTLIrW8hkk+xm4KUlEoa X-Received: by 2002:aa7:c418:0:b0:428:44a0:9967 with SMTP id j24-20020aa7c418000000b0042844a09967mr12873406edq.342.1652015415716; Sun, 08 May 2022 06:10:15 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1652015415; cv=none; d=google.com; s=arc-20160816; b=WCuigLeTMlQ14pl7OmsX6hsOgTkzmj11o5XgxDQcGPTnek6PXY6l0x9zjDms4MznIq YvZtzN0wb8QfuLJB6qkfPSFmiodiXRQH2MjdCusOfEHFEn06D1fA4h5wA3rtOrAInK5w p4Z3ZtiVG+TWrCxUBrcLvHlulOQdbWSH+uR43qufTmx+8X+4HLv2suBlhNm4lgFa9xAV ne2DmGNmLeSaOCwN5H/C2wSn8/fNo2lh6Z1FP2f8sQdK7s7R5h9rFDcMsCIOwP9p33Bp PTQlzd+GJzEHu7L/yVqlGs9nFtXK7jzJHZjKTvqgwyRojcuEQDTy+mmwLEea37ock5LT kAcQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:message-id:date:references :organization:in-reply-to:subject:cc:to:from:dkim-signature; bh=eNO3AXbFQifeDKXgtrKqkR+vM9epidMSOBVrp32PqiU=; b=p5dKVJwyABnmS1iTwI8PQzlJ6+O4WETZ9V2jMujpOeBM7uLAzirOoe7cUlLAatn5WN /efdI/SDnwORWYmQPzPd+oL7/Bg3sLF+2Nh9lMz01tQWWUJusboORNeKNyd327sLCgEH Rn9rEK1p3gXOStXP+Rf21J1qvTpEDp2BnYUk/omA1xng4CZT5AJTxi0v7Gvj7Eic/MFO TUFBwhfJTOLOW+0hDzlbr2HPo8Hd5inIFS/Lh6jAUqe8gNblitSDSmc+NzzXJJmw7Cqq kQ6fpXtf4K/urB+Z/ytsu1EvQK9yHN9O4Yrgi/7VUspMBSakYS4/oDKDJuId15lBL2I7 /glQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=AqEcMMxg; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id o15-20020a170906860f00b006e86d1b6cbdsi9524400ejx.920.2022.05.08.06.09.51; Sun, 08 May 2022 06:10:15 -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; dkim=pass header.i=@intel.com header.s=Intel header.b=AqEcMMxg; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1391233AbiEFLUO (ORCPT + 99 others); Fri, 6 May 2022 07:20:14 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:53780 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S244042AbiEFLUM (ORCPT ); Fri, 6 May 2022 07:20:12 -0400 Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 76B385DA36; Fri, 6 May 2022 04:16:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1651835790; x=1683371790; h=from:to:cc:subject:in-reply-to:references:date: message-id:mime-version; bh=Ffv8NjpypTctGSjcYAJAG04MB4c0QqG3L0uxm5pUCHs=; b=AqEcMMxg4dcJxqjyswDOJZb32SkX5hEiCSErwZnKdJhLsWvY8vTXlky3 /xhA7Z00ErdU8WMVLdUg/ucpV4IF4DPyH5xwnI+zdE38R3roCqdvE2FVB /Q/EH8QwA+ElyK4WstwVVyne2wybmxKDDyCA+Aym3mOUGrv0/INh4TMVl 6mkgc5GtNayfewMg1eMVR71FeN5mbKPvgzRFVsd6XteEsTX8PEHJeCUMx HZoE2TtkS97rLxIRfY8UBjG5FJ5sa2floO4bbFjMUYloBm3kYIdmAOOi1 v4ryZP8pM5vLgE6v9XViBUaOEN6NplPKqFxhGO1SN1fp8v6I6u0vRfaP0 A==; X-IronPort-AV: E=McAfee;i="6400,9594,10338"; a="354873953" X-IronPort-AV: E=Sophos;i="5.91,203,1647327600"; d="scan'208";a="354873953" Received: from orsmga004.jf.intel.com ([10.7.209.38]) by fmsmga105.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 06 May 2022 04:16:30 -0700 X-IronPort-AV: E=Sophos;i="5.91,203,1647327600"; d="scan'208";a="695132735" Received: from psikora-mobl.ger.corp.intel.com (HELO localhost) ([10.249.157.88]) by orsmga004-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 06 May 2022 04:16:25 -0700 From: Jani Nikula To: Doug Anderson , dri-devel , Ville =?utf-8?B?U3lyasOkbMOk?= Cc: Sankeerth Billakanti , Thomas Zimmermann , David Airlie , linux-arm-msm , "Abhinav Kumar (QUIC)" , Stephen Boyd , Dmitry Baryshkov , "Aravind Venkateswaran (QUIC)" , "Kuogee Hsieh (QUIC)" , LKML Subject: Re: [RFC PATCH] drm/edid: drm_add_modes_noedid() should set lowest resolution as preferred In-Reply-To: Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo References: <20220426132121.RFC.1.I31ec454f8d4ffce51a7708a8092f8a6f9c929092@changeid> Date: Fri, 06 May 2022 14:16:22 +0300 Message-ID: <874k22lxmh.fsf@intel.com> MIME-Version: 1.0 Content-Type: text/plain X-Spam-Status: No, score=-4.9 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_EF,RCVD_IN_DNSWL_MED,SPF_HELO_NONE, SPF_NONE,T_SCC_BODY_TEXT_LINE autolearn=ham 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 On Thu, 05 May 2022, Doug Anderson wrote: > Ville, > > On Tue, Apr 26, 2022 at 1:21 PM Douglas Anderson wrote: >> >> If we're unable to read the EDID for a display because it's corrupt / >> bogus / invalid then we'll add a set of standard modes for the >> display. When userspace looks at these modes it doesn't really have a >> good concept for which mode to pick and it'll likely pick the highest >> resolution one by default. That's probably not ideal because the modes >> were purely guesses on the part of the Linux kernel. >> >> Let's instead set 640x480 as the "preferred" mode when we have no EDID. >> >> Signed-off-by: Douglas Anderson >> --- >> >> drivers/gpu/drm/drm_edid.c | 9 +++++++++ >> 1 file changed, 9 insertions(+) > > Someone suggested that you might have an opinion on this patch and > another one I posted recently [1]. Do you have any thoughts on it? > Just to be clear: I'm hoping to land _both_ this patch and [1]. If you > don't have an opinion, that's OK too. > > [1] https://lore.kernel.org/r/20220426114627.2.I4ac7f55aa446699f8c200a23c10463256f6f439f@changeid There are a number of drivers with combos: drm_add_modes_noedid() drm_set_preferred_mode() which I think would be affected by the change. Perhaps you should just call drm_set_preferred_mode() in your referenced patch? Alternatively, perhaps drm_set_preferred_mode() should erase the previous preferred mode(s) if it finds a matching new preferred mode. BR, Jani. -- Jani Nikula, Intel Open Source Graphics Center