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 mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id B95CBC433EF for ; Fri, 12 Nov 2021 10:37:16 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id A278560ED5 for ; Fri, 12 Nov 2021 10:37:16 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234728AbhKLKkG (ORCPT ); Fri, 12 Nov 2021 05:40:06 -0500 Received: from mga11.intel.com ([192.55.52.93]:46699 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234619AbhKLKkE (ORCPT ); Fri, 12 Nov 2021 05:40:04 -0500 X-IronPort-AV: E=McAfee;i="6200,9189,10165"; a="230576258" X-IronPort-AV: E=Sophos;i="5.87,229,1631602800"; d="scan'208";a="230576258" Received: from orsmga008.jf.intel.com ([10.7.209.65]) by fmsmga102.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 12 Nov 2021 02:37:09 -0800 X-IronPort-AV: E=Sophos;i="5.87,229,1631602800"; d="scan'208";a="504838590" Received: from sbacanu-mobl1.ger.corp.intel.com (HELO localhost) ([10.251.217.145]) by orsmga008-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 12 Nov 2021 02:37:06 -0800 From: Jani Nikula To: Pekka Paalanen , Thomas Zimmermann Cc: Javier Martinez Canillas , Daniel Vetter , Michel =?utf-8?Q?D=C3=A4nzer?= , linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org, Peter Robinson Subject: Re: [PATCH v4 0/6] Cleanups for the nomodeset kernel command line parameter logic In-Reply-To: <20211112122239.26b3787c@eldfell> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo References: <20211108140648.795268-1-javierm@redhat.com> <20211112105641.25a4e1a7@eldfell> <20211112122239.26b3787c@eldfell> Date: Fri, 12 Nov 2021 12:37:03 +0200 Message-ID: <877ddd4q40.fsf@intel.com> MIME-Version: 1.0 Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 12 Nov 2021, Pekka Paalanen wrote: > On Fri, 12 Nov 2021 11:09:13 +0100 > Thomas Zimmermann wrote: > >> Hi >> >> Am 12.11.21 um 10:39 schrieb Javier Martinez Canillas: >> > Hello Pekka, >> > >> > On 11/12/21 09:56, Pekka Paalanen wrote: >> > >> > [snip] >> > >> >> >> >> Hi, >> >> >> >> these ideas make sense to me, so FWIW, >> >> >> >> Acked-by: Pekka Paalanen >> >> >> > >> > Thanks. >> > >> >> There is one nitpick I'd like to ask about: >> >> >> >> +bool drm_get_modeset(void) >> >> +{ >> >> + return !drm_nomodeset; >> >> +} >> >> +EXPORT_SYMBOL(drm_get_modeset); >> >> >> >> Doesn't "get" have a special meaning in the kernel land, like "take a >> >> strong reference on an object and return it"? >> > >> > That's a very good point. >> > >> >> As this is just returning bool without changing anything, the usual >> >> word to use is "is". Since this function is also used at most once per >> >> driver, which is rarely, it could have a long and descriptive name. >> >> >> >> For example: >> >> >> >> bool drm_is_modeset_driver_allowed(void); >> >> I'd nominate >> >> bool drm_native_drivers_enabled() >> >> This is what HW-specific drivers want to query in their init/probing >> code. The actual semantics of this decision is hidden from the driver. >> It's also easier to read than the other name IMHO > > Ok, but what is a "native driver"? Or a "non-native driver"? > Is that established kernel terminology? FWIW, it doesn't mean anything to me. drm_modeset_enabled()? *sigh* I worked so hard not to participate in this bikeshed. ;) BR, Jani. > > I'd think a non-native driver is something that e.g. ndiswrapper is > loading. Is simpledrm like ndiswrapper in a sense? IIRC, simpledrm is > the driver that would not consult this function, right? > > > Thanks, > pq > >> >> Best regards >> Thomas >> >> >> >> > >> > Yeah, naming is hard. Jani also mentioned that he didn't like this >> > function name, so I don't mind to re-spin the series only for that. >> > >> >> - "drm" is the namespace >> >> - "is" implies it is a read-only boolean inspection >> >> - "modeset" is the feature being checked >> >> - "driver" implies it is supposed gate driver loading or >> >> initialization, rather than modesets after drivers have loaded >> >> - "allowed" says it is asking about general policy rather than what a >> >> driver does >> >> >> > >> > I believe that name is more verbose than needed. But don't have a >> > strong opinion and could use it if others agree. >> > >> >> Just a bikeshed, I'll leave it to actual kernel devs to say if this >> >> would be more appropriate or worth it. >> >> >> > >> > I think is worth it and better to do it now before the patches land, but >> > we could wait for others to chime in. >> > >> > Best regards, >> > -- >> > Javier Martinez Canillas >> > Linux Engineering >> > Red Hat >> > >> > -- Jani Nikula, Intel Open Source Graphics Center