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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 4B78FC001E0 for ; Tue, 25 Jul 2023 10:05:25 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233569AbjGYKFX (ORCPT ); Tue, 25 Jul 2023 06:05:23 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:60966 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232974AbjGYKE7 (ORCPT ); Tue, 25 Jul 2023 06:04:59 -0400 Received: from mblankhorst.nl (lankhorst.se [IPv6:2a02:2308:0:7ec:e79c:4e97:b6c4:f0ae]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id BED8F1FC0 for ; Tue, 25 Jul 2023 03:04:25 -0700 (PDT) Message-ID: Date: Tue, 25 Jul 2023 12:04:19 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.11.0 Subject: Re: [PATCH v2 4/9] ALSA: hda/i915: Allow xe as match for i915_component_master_match Content-Language: en-US To: Pierre-Louis Bossart , alsa-devel@alsa-project.org Cc: sound-open-firmware@alsa-project.org, linux-kernel@vger.kernel.org, Jaroslav Kysela , Takashi Iwai , Cezary Rojewski , Liam Girdwood , Peter Ujfalusi , Bard Liao , Ranjani Sridharan , Kai Vehmanen , Mark Brown , Daniel Baluta References: <20230719164141.228073-1-maarten.lankhorst@linux.intel.com> <20230719164141.228073-5-maarten.lankhorst@linux.intel.com> <518bb7a9-3a85-2c13-68bf-63baaff176ef@linux.intel.com> From: Maarten Lankhorst In-Reply-To: <518bb7a9-3a85-2c13-68bf-63baaff176ef@linux.intel.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hey, On 2023-07-24 12:28, Pierre-Louis Bossart wrote: > > > On 7/19/23 18:41, Maarten Lankhorst wrote: >> xe is a new driver for intel GPU's that shares the sound related code >> with i915. >> >> Don't allow it to be modprobed though; the module is not upstream yet >> and we should exclusively use the EPROBE_DEFER mechanism. > > I can't figure out what this comment means. > > how would the -EPROBE_DEFER mechanism help if the driver that will > trigger a new probe is not upstream? > > Not following at all what you intended to explain. What I mean is that there is code inside the current code that does request_module("i915"), the comment meant I didn't try to add any logic for request_module("xe"), as the driver is not merged yet. Additionally I am removing the request_module logic, but this comment was written when I first tried the simple solution of request_module("xe"). Turns out telepathy is hard, and using -EPROBE_DEFER is much simpler. :-) Cheers, ~Maarten