Received: by 2002:ad5:4acb:0:0:0:0:0 with SMTP id n11csp384293imw; Thu, 14 Jul 2022 03:16:58 -0700 (PDT) X-Google-Smtp-Source: AGRyM1uP/kkqv6mWPDfSlmjQ+ItSftDnZYXdTUi8gFPJ11a/zP7pIRHy3B/vJilR3RIUfxfjSBjT X-Received: by 2002:a63:8ac3:0:b0:419:c3bb:7d99 with SMTP id y186-20020a638ac3000000b00419c3bb7d99mr757284pgd.57.1657793818687; Thu, 14 Jul 2022 03:16:58 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1657793818; cv=none; d=google.com; s=arc-20160816; b=G2Pdn9IkJR4bhir8i017tt+Mn7yynN9mSxOZZUUstSESiddelL48LbltziRTOHn90N zrpZ1IcWfGHi9lfZxHRsTrran9stFlvR17sHxc25t+gVH9BV72W3lKRqIdBu3QR9p43z kG9wOP4YMYfJibhZ8XoYmv5mLWpRBtPTVPoWSJQFgoah/zmUbsYnjwziH8dzYprhGCha Lgohq7C8k6x/h4QmEaZL3ZBtwdO/qlKZqVubVGXQ0NJ6X/xjrNFJ9jJDlQpQLS10HrJ/ HClY/JRzcC4Pd/RTlXl2ATlRxd+MkvfvHqtEcXYTDFWlhrK9zAKpYXK7den5GgQIGfO2 NlWw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date :dkim-signature; bh=GG2OghbfeEiwCwpcVygyN5cz67fyHMa6aNx/SHrWo5U=; b=rPLPhER3oLeJBBgaTDdZ0TS12WUY+IX21fPt1voIsGIQZNjcfso0HY/q4RJmAkZCT2 j5RE597CGPfKqLZtDsUDFK3h1DDaIHIFyFXH3bSVb1k8mDrp8pMWsge320RrpsXViYKA wMxazRiw3Y5AZtQ+vLwTMD3L25+eC9xwXpDDO3mn74TTl81mV461sl6iyBETn8w8P0nZ MGKe1wGsg05xD/8RrqN8Y1sY6mED5Iuc5rHUHRvP2XFA5PMCsdbqx16F8KO/nDfJG6BX TDqMX2D3lf6OxzxChVj4PUXDud5OjBiJCZXfbnv+bxjG6+tNt7c+wW67qeQxov3O2V6Z f4UA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b="BL6dl+/N"; 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 d15-20020a170902aa8f00b0016be3f2b61fsi1431283plr.114.2022.07.14.03.16.46; Thu, 14 Jul 2022 03:16:58 -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="BL6dl+/N"; 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 S236586AbiGNKB4 (ORCPT + 99 others); Thu, 14 Jul 2022 06:01:56 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41734 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234293AbiGNKBw (ORCPT ); Thu, 14 Jul 2022 06:01:52 -0400 Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 18350237 for ; Thu, 14 Jul 2022 03:01:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1657792910; x=1689328910; h=date:from:to:cc:subject:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=CKGB/yo/ih8xEbnORUj5mJ3VqyPJ4af0U9ygsNoB2do=; b=BL6dl+/NuQnZMCpBcyx7vsMV7jOuWxyxrCSi1QaIFvBOMksRnQTYqqVy x/BSpBWyi1y83ofu1QxWm6ErW2GnhKkHWKUrz+sK6zQSug9qYToZyGrfS u4gUzzKQ9ki+v1HGEchFltXIPGh/yY1mAhiigJETcQGvZyhLpZB9OzYFu Zv8yDUr+zRxM1yVLwLpKHzYtsB+IC/SVoJGl36z4/OAAGFCfihQ6KyzZI CDRt4bvcaTbnnInX/wxwc4Zz2uVdW0RQXzHrn1Y9SgnkSHooFeBHSsaZn p9QTMkKdzX5Vt70M+JON5ZvWH2kDoagoveUz1k9xx+aQ9W6+i0Hb6ZFrL Q==; X-IronPort-AV: E=McAfee;i="6400,9594,10407"; a="311121050" X-IronPort-AV: E=Sophos;i="5.92,269,1650956400"; d="scan'208";a="311121050" Received: from orsmga008.jf.intel.com ([10.7.209.65]) by fmsmga101.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 14 Jul 2022 03:01:49 -0700 X-IronPort-AV: E=Sophos;i="5.92,269,1650956400"; d="scan'208";a="623354560" Received: from acsok-mobl.ti.intel.com (HELO maurocar-mobl2) ([10.252.37.128]) by orsmga008-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 14 Jul 2022 03:01:44 -0700 Date: Thu, 14 Jul 2022 12:01:41 +0200 From: Mauro Carvalho Chehab To: Rodrigo Vivi Cc: Mauro Carvalho Chehab , Thomas =?UTF-8?B?SGVsbHN0?= =?UTF-8?B?csO2bQ==?= , Michael Cheng , Alan Previn , David Airlie , Sebastian Andrzej Siewior , Lucas De Marchi , linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org, Chris Wilson , Matthew Auld , =?UTF-8?B?TWljaGHFgg==?= Winiarski , Tejas Upadhyay , intel-gfx@lists.freedesktop.org, Nirmoy Das Subject: Re: [Intel-gfx] [PATCH v2 06/39] drm/i915: gt: fix some Kernel-doc issues Message-ID: <20220714120141.18b5e69d@maurocar-mobl2> In-Reply-To: References: <3cb8ebff378fc0634e992eba68176ed30842572a.1657699522.git.mchehab@kernel.org> X-Mailer: Claws Mail 4.1.0 (GTK 3.24.34; x86_64-redhat-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-7.6 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_EF,RCVD_IN_DNSWL_HI, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,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 Wed, 13 Jul 2022 18:07:44 -0400 Rodrigo Vivi wrote: > On Wed, Jul 13, 2022 at 09:11:54AM +0100, Mauro Carvalho Chehab wrote: > > There are several trivial warnings there, due to trivial things: > > - lack of function name at the kerneldoc markup; > > - undocumented structs with kernel-doc markups; > > - wrong parameter syntax. > > > > Fix such warnings: > > > > drivers/gpu/drm/i915/gt/intel_context.h:107: warning: Function parameter or member 'ce' not described in 'intel_context_lock_pinned' > > drivers/gpu/drm/i915/gt/intel_context.h:122: warning: Function parameter or member 'ce' not described in 'intel_context_is_pinned' > > drivers/gpu/drm/i915/gt/intel_context.h:141: warning: Function parameter or member 'ce' not described in 'intel_context_unlock_pinned' > > drivers/gpu/drm/i915/gt/intel_gtt.h:510: warning: Function parameter or member 'vm' not described in 'i915_vm_resv_put' > > drivers/gpu/drm/i915/gt/intel_gtt.h:510: warning: Excess function parameter 'resv' description in 'i915_vm_resv_put' > > drivers/gpu/drm/i915/gt/intel_gtt.h:615: warning: Function parameter or member 'i915' not described in 'i915_ggtt_mark_pte_lost' > > drivers/gpu/drm/i915/gt/intel_gtt.h:615: warning: Function parameter or member 'val' not described in 'i915_ggtt_mark_pte_lost' > > drivers/gpu/drm/i915/gt/intel_rps.c:2343: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst > > * Tells the intel_ips driver that the i915 driver is now loaded, if > > drivers/gpu/drm/i915/gt/uc/guc_capture_fwif.h:28: warning: Function parameter or member 'size' not described in '__guc_capture_bufstate' > > drivers/gpu/drm/i915/gt/uc/guc_capture_fwif.h:28: warning: Function parameter or member 'data' not described in '__guc_capture_bufstate' > > drivers/gpu/drm/i915/gt/uc/guc_capture_fwif.h:28: warning: Function parameter or member 'rd' not described in '__guc_capture_bufstate' > > drivers/gpu/drm/i915/gt/uc/guc_capture_fwif.h:28: warning: Function parameter or member 'wr' not described in '__guc_capture_bufstate' > > drivers/gpu/drm/i915/gt/uc/guc_capture_fwif.h:60: warning: Function parameter or member 'link' not described in '__guc_capture_parsed_output' > > drivers/gpu/drm/i915/gt/uc/guc_capture_fwif.h:60: warning: Function parameter or member 'is_partial' not described in '__guc_capture_parsed_output' > > drivers/gpu/drm/i915/gt/uc/guc_capture_fwif.h:60: warning: Function parameter or member 'eng_class' not described in '__guc_capture_parsed_output' > > drivers/gpu/drm/i915/gt/uc/guc_capture_fwif.h:60: warning: Function parameter or member 'eng_inst' not described in '__guc_capture_parsed_output' > > drivers/gpu/drm/i915/gt/uc/guc_capture_fwif.h:60: warning: Function parameter or member 'guc_id' not described in '__guc_capture_parsed_output' > > drivers/gpu/drm/i915/gt/uc/guc_capture_fwif.h:60: warning: Function parameter or member 'lrca' not described in '__guc_capture_parsed_output' > > drivers/gpu/drm/i915/gt/uc/guc_capture_fwif.h:60: warning: Function parameter or member 'reginfo' not described in '__guc_capture_parsed_output' > > drivers/gpu/drm/i915/gt/uc/guc_capture_fwif.h:63: warning: wrong kernel-doc identifier on line: > > * struct guc_debug_capture_list_header / struct guc_debug_capture_list > > drivers/gpu/drm/i915/gt/uc/guc_capture_fwif.h:81: warning: wrong kernel-doc identifier on line: > > * struct __guc_mmio_reg_descr / struct __guc_mmio_reg_descr_group > > drivers/gpu/drm/i915/gt/uc/guc_capture_fwif.h:106: warning: wrong kernel-doc identifier on line: > > * struct guc_state_capture_header_t / struct guc_state_capture_t / > > drivers/gpu/drm/i915/gt/uc/guc_capture_fwif.h:164: warning: Function parameter or member 'is_valid' not described in '__guc_capture_ads_cache' > > drivers/gpu/drm/i915/gt/uc/guc_capture_fwif.h:164: warning: Function parameter or member 'ptr' not described in '__guc_capture_ads_cache' > > drivers/gpu/drm/i915/gt/uc/guc_capture_fwif.h:164: warning: Function parameter or member 'size' not described in '__guc_capture_ads_cache' > > drivers/gpu/drm/i915/gt/uc/guc_capture_fwif.h:164: warning: Function parameter or member 'status' not described in '__guc_capture_ads_cache' > > drivers/gpu/drm/i915/gt/uc/guc_capture_fwif.h:217: warning: Function parameter or member 'ads_null_cache' not described in 'intel_guc_state_capture' > > drivers/gpu/drm/i915/gt/uc/guc_capture_fwif.h:217: warning: Function parameter or member 'max_mmio_per_node' not described in 'intel_guc_state_capture' > > drivers/gpu/drm/i915/gt/uc/intel_guc_fwif.h:401: warning: Function parameter or member 'marker' not described in 'guc_log_buffer_state' > > drivers/gpu/drm/i915/gt/uc/intel_guc_fwif.h:401: warning: Function parameter or member 'read_ptr' not described in 'guc_log_buffer_state' > > drivers/gpu/drm/i915/gt/uc/intel_guc_fwif.h:401: warning: Function parameter or member 'write_ptr' not described in 'guc_log_buffer_state' > > drivers/gpu/drm/i915/gt/uc/intel_guc_fwif.h:401: warning: Function parameter or member 'size' not described in 'guc_log_buffer_state' > > drivers/gpu/drm/i915/gt/uc/intel_guc_fwif.h:401: warning: Function parameter or member 'sampled_write_ptr' not described in 'guc_log_buffer_state' > > drivers/gpu/drm/i915/gt/uc/intel_guc_fwif.h:401: warning: Function parameter or member 'wrap_offset' not described in 'guc_log_buffer_state' > > drivers/gpu/drm/i915/gt/uc/intel_guc_fwif.h:401: warning: Function parameter or member 'flush_to_file' not described in 'guc_log_buffer_state' > > drivers/gpu/drm/i915/gt/uc/intel_guc_fwif.h:401: warning: Function parameter or member 'buffer_full_cnt' not described in 'guc_log_buffer_state' > > drivers/gpu/drm/i915/gt/uc/intel_guc_fwif.h:401: warning: Function parameter or member 'reserved' not described in 'guc_log_buffer_state' > > drivers/gpu/drm/i915/gt/uc/intel_guc_fwif.h:401: warning: Function parameter or member 'flags' not described in 'guc_log_buffer_state' > > drivers/gpu/drm/i915/gt/uc/intel_guc_fwif.h:401: warning: Function parameter or member 'version' not described in 'guc_log_buffer_state' > > > > Signed-off-by: Mauro Carvalho Chehab > > --- > > > > To avoid mailbombing on a large number of people, only mailing lists were C/C on the cover. > > See [PATCH v2 00/39] at: https://lore.kernel.org/all/cover.1657699522.git.mchehab@kernel.org/ > > > > drivers/gpu/drm/i915/gt/intel_context.h | 6 +++--- > > drivers/gpu/drm/i915/gt/intel_engine_cs.c | 4 ++-- > > drivers/gpu/drm/i915/gt/intel_gtt.h | 6 +++--- > > drivers/gpu/drm/i915/gt/intel_rps.c | 4 ++-- > > drivers/gpu/drm/i915/gt/uc/guc_capture_fwif.h | 14 +++++++------- > > drivers/gpu/drm/i915/gt/uc/intel_guc_fwif.h | 2 +- > > 6 files changed, 18 insertions(+), 18 deletions(-) > > > > diff --git a/drivers/gpu/drm/i915/gt/intel_context.h b/drivers/gpu/drm/i915/gt/intel_context.h > > index 8e2d70630c49..91c092d5deae 100644 > > --- a/drivers/gpu/drm/i915/gt/intel_context.h > > +++ b/drivers/gpu/drm/i915/gt/intel_context.h > > @@ -96,7 +96,7 @@ void intel_context_bind_parent_child(struct intel_context *parent, > > > > /** > > * intel_context_lock_pinned - Stablises the 'pinned' status of the HW context > > - * @ce - the context > > + * @ce: the context > > * > > * Acquire a lock on the pinned status of the HW context, such that the context > > * can neither be bound to the GPU or unbound whilst the lock is held, i.e. > > @@ -110,7 +110,7 @@ static inline int intel_context_lock_pinned(struct intel_context *ce) > > > > /** > > * intel_context_is_pinned - Reports the 'pinned' status > > - * @ce - the context > > + * @ce: the context > > * > > * While in use by the GPU, the context, along with its ring and page > > * tables is pinned into memory and the GTT. > > @@ -132,7 +132,7 @@ static inline void intel_context_cancel_request(struct intel_context *ce, > > > > /** > > * intel_context_unlock_pinned - Releases the earlier locking of 'pinned' status > > - * @ce - the context > > + * @ce: the context > > * > > * Releases the lock earlier acquired by intel_context_unlock_pinned(). > > */ > > diff --git a/drivers/gpu/drm/i915/gt/intel_engine_cs.c b/drivers/gpu/drm/i915/gt/intel_engine_cs.c > > index 37fa813af766..da225f5db2a4 100644 > > --- a/drivers/gpu/drm/i915/gt/intel_engine_cs.c > > +++ b/drivers/gpu/drm/i915/gt/intel_engine_cs.c > > @@ -1197,7 +1197,7 @@ create_kernel_context(struct intel_engine_cs *engine) > > } > > > > /** > > - * intel_engines_init_common - initialize cengine state which might require hw access > > + * engine_init_common - initialize cengine state which might require hw access > > * @engine: Engine to initialize. > > * > > * Initializes @engine@ structure members shared between legacy and execlists > > @@ -1278,7 +1278,7 @@ int intel_engines_init(struct intel_gt *gt) > > } > > > > /** > > - * intel_engines_cleanup_common - cleans up the engine state created by > > + * intel_engine_cleanup_common - cleans up the engine state created by > > * the common initiailizers. > > * @engine: Engine to cleanup. > > * > > diff --git a/drivers/gpu/drm/i915/gt/intel_gtt.h b/drivers/gpu/drm/i915/gt/intel_gtt.h > > index e639434e97fd..fca8eedee1d8 100644 > > --- a/drivers/gpu/drm/i915/gt/intel_gtt.h > > +++ b/drivers/gpu/drm/i915/gt/intel_gtt.h > > @@ -503,7 +503,7 @@ static inline void i915_vm_put(struct i915_address_space *vm) > > > > /** > > * i915_vm_resv_put - Release a reference on the vm's reservation lock > > - * @resv: Pointer to a reservation lock obtained from i915_vm_resv_get() > > + * @vm: The vm whose reservation lock was obtained from i915_vm_resv_get() > > */ > > static inline void i915_vm_resv_put(struct i915_address_space *vm) > > { > > @@ -604,8 +604,8 @@ void i915_ggtt_resume(struct i915_ggtt *ggtt); > > > > /** > > * i915_ggtt_mark_pte_lost - Mark ggtt ptes as lost or clear such a marking > > - * @i915 The device private. > > - * @val whether the ptes should be marked as lost. > > + * @i915: The device private. > > + * @val: whether the ptes should be marked as lost. > > * > > * In some cases pte content is retained across suspend, but typically lost > > * across hibernate. Typically they should be marked as lost on > > diff --git a/drivers/gpu/drm/i915/gt/intel_rps.c b/drivers/gpu/drm/i915/gt/intel_rps.c > > index fb3f57ee450b..8aefc427e06e 100644 > > --- a/drivers/gpu/drm/i915/gt/intel_rps.c > > +++ b/drivers/gpu/drm/i915/gt/intel_rps.c > > @@ -2339,8 +2339,8 @@ bool rps_read_mask_mmio(struct intel_rps *rps, > > static struct drm_i915_private __rcu *ips_mchdev; > > > > /** > > - * Tells the intel_ips driver that the i915 driver is now loaded, if > > - * IPS got loaded first. > > + * ips_ping_for_i915_load - Tells the intel_ips driver that the i915 driver > > + * is now loaded, if IPS got loaded first. > > * > > * This awkward dance is so that neither module has to depend on the > > * other in order for IPS to do the appropriate communication of > > diff --git a/drivers/gpu/drm/i915/gt/uc/guc_capture_fwif.h b/drivers/gpu/drm/i915/gt/uc/guc_capture_fwif.h > > index 3624abfd22d1..58f93226b1c1 100644 > > --- a/drivers/gpu/drm/i915/gt/uc/guc_capture_fwif.h > > +++ b/drivers/gpu/drm/i915/gt/uc/guc_capture_fwif.h > > @@ -12,7 +12,7 @@ > > struct intel_guc; > > struct file; > > > > -/** > > +/* > > * struct __guc_capture_bufstate > > * > > * Book-keeping structure used to track read and write pointers > > @@ -26,7 +26,7 @@ struct __guc_capture_bufstate { > > u32 wr; > > }; > > > > -/** > > +/* > > * struct __guc_capture_parsed_output - extracted error capture node > > * > > * A single unit of extracted error-capture output data grouped together > > @@ -58,7 +58,7 @@ struct __guc_capture_parsed_output { > > #define GCAP_PARSED_REGLIST_INDEX_ENGINST BIT(GUC_CAPTURE_LIST_TYPE_ENGINE_INSTANCE) > > }; > > > > -/** > > +/* > > * struct guc_debug_capture_list_header / struct guc_debug_capture_list > > * > > * As part of ADS registration, these header structures (followed by > > @@ -76,7 +76,7 @@ struct guc_debug_capture_list { > > struct guc_mmio_reg regs[0]; > > } __packed; > > > > -/** > > +/* > > * struct __guc_mmio_reg_descr / struct __guc_mmio_reg_descr_group > > * > > * intel_guc_capture module uses these structures to maintain static > > @@ -101,7 +101,7 @@ struct __guc_mmio_reg_descr_group { > > struct __guc_mmio_reg_descr *extlist; /* only used for steered registers */ > > }; > > > > -/** > > +/* > > * struct guc_state_capture_header_t / struct guc_state_capture_t / > > * guc_state_capture_group_header_t / guc_state_capture_group_t > > * > > @@ -148,7 +148,7 @@ struct guc_state_capture_group_t { > > struct guc_state_capture_t capture_entries[0]; > > } __packed; > > > > -/** > > +/* > > * struct __guc_capture_ads_cache > > and many more here... :/ > Hopefully this great work on the docs will make these ugly > "exported" "__" prefixes visible and we will fix them Yeah, while I can see why __function would be ok on some cases (like for lock/unlock variants and on some special macros like the ones that use THIS_MODULE), I can't see any reason why struct/enum/union would ever need to have __ prefixes on it ;-) > Reviewed-by: Rodrigo Vivi Thanks! Regards, Mauro