From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mgamail.intel.com (mgamail.intel.com [192.198.163.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 44F4418DB1F; Mon, 17 Aug 2026 06:35:16 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=192.198.163.10 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1786948518; cv=none; b=JJiX17bw9X3CG1KKksNynJeby0i8uN8svdOSWAId8QIhI9TxOHePz/I9hjQjSgs7SkwbDYkRf3FRDnSFEaqqMhwriXsAUnibaIc4gGNjMj78T3lxlMgLKKb90MjRvzvT+5y76Pjd7AiaC+0UtmqSABUbLmuM7lL4g4E2eCEeYL0= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1786948518; c=relaxed/simple; bh=OHb/Ukkl5wYeXcU02S+w/kjomGU6EOUWgSlaJ0dzaLA=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=gxTToffa/+GnD3RPjl4Rqip1hbCpKThnYg7W8TR835C/zsG7rm3qVQHVN/0DbKh0h5qBNY3ym/mWH8c/DShlBNQUGJdFDuC3ZHsB3Unq+/cVUsHVDcIpsuIaPKHbwkXgo+BdJuwauij4SVYbU5BrVWQD6CBbq9RQbhKavYk6xds= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.intel.com; spf=pass smtp.mailfrom=linux.intel.com; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b=Gt80AMwm; arc=none smtp.client-ip=192.198.163.10 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.intel.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linux.intel.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b="Gt80AMwm" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1786948517; x=1818484517; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=OHb/Ukkl5wYeXcU02S+w/kjomGU6EOUWgSlaJ0dzaLA=; b=Gt80AMwm3dRhwyIlWYe0uwLEBO0GF+ShUN4MLS1uMPOellMpIRM5ZUSI BxHMi+3EFTyGFQ5p1OU1hLrD1xb7k4LNMERy7XBDuFAmryqvzwqA4K29a n5yvb+vtE6EUj5h+IXabgkLqIdkxH/HH2S9VFu5mrfZGaJkBI5jEUegEV kqvFOrYFSwv6MRcFkQwbMiKOjB/tFhC9Km2buQPGP/JltwmjC3nBn139f +oxzFwfU/vkaJWPWlc+4WL3/uXT7Z4Oi+M8u2RWOK0dwsFQ9EU9cbUfDD EEnzYT0PW1YnSou8X++QcnrYgl5PvpVAQVTYQmkK64ZXG7jx2vs9m+IYO Q==; X-CSE-ConnectionGUID: bPZdBcAzTtW+ZqWAkUxZqQ== X-CSE-MsgGUID: gDw6KLBASFmqNheIplwzFw== X-IronPort-AV: E=McAfee;i="6800,10657,11877"; a="98780143" X-IronPort-AV: E=Sophos;i="6.25,228,1779174000"; d="scan'208";a="98780143" Received: from orviesa007.jf.intel.com ([10.64.159.147]) by fmvoesa104.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 16 Aug 2026 23:35:15 -0700 X-CSE-ConnectionGUID: IhYXXzm8SKWwRseS0Ppuig== X-CSE-MsgGUID: LS7+ULQkQqmleKkMf5wgXA== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.25,228,1779174000"; d="scan'208";a="264865206" Received: from klitkey1-mobl1.ger.corp.intel.com (HELO localhost) ([10.245.245.67]) by orviesa007-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 16 Aug 2026 23:35:07 -0700 Date: Mon, 17 Aug 2026 09:35:05 +0300 From: Andy Shevchenko To: Manivannan Sadhasivam Cc: Krzysztof Kozlowski , Dmitry Torokhov , manivannan.sadhasivam@oss.qualcomm.com, Rob Herring , Greg Kroah-Hartman , Jiri Slaby , Nathan Chancellor , Nicolas Schier , Hans de Goede , Ilpo =?iso-8859-1?Q?J=E4rvinen?= , Mark Pearson , "Derek J. Clark" , Conor Dooley , Marcel Holtmann , Luiz Augusto von Dentz , Bartosz Golaszewski , Daniel Scally , Heikki Krogerus , Sakari Ailus , "Rafael J. Wysocki" , Danilo Krummrich , Bartosz Golaszewski , linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org, platform-driver-x86@vger.kernel.org, linux-pci@vger.kernel.org, devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org, linux-bluetooth@vger.kernel.org, linux-pm@vger.kernel.org, Stephan Gerhold , Dmitry Baryshkov , linux-acpi@vger.kernel.org, Sui Jingfeng Subject: Re: [PATCH v3 03/14] software node: Implement device_get_match_data fwnode callback Message-ID: References: <20260110-pci-m2-e-v3-0-4faee7d0d5ae@oss.qualcomm.com> <20260110-pci-m2-e-v3-3-4faee7d0d5ae@oss.qualcomm.com> <6l3rs5pv6xnrbygpvqrdxqoqtybjyefsltk5bl4336q56rfoza@ejo3sxuufghe> <6peb6afhpm4l7opxbdt3b5sx32longevwds5c3dlqji2hr5dlh@kxuvj55jkqgi> Precedence: bulk X-Mailing-List: devicetree@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: Intel Finland Oy - BIC 0357606-4 - c/o Alberga Business Park, 6 krs, Bertel Jungin Aukio 5, 02600 Espoo On Fri, Aug 14, 2026 at 02:49:31PM +0200, Manivannan Sadhasivam wrote: > On Mon, Jan 12, 2026 at 10:01:23PM +0530, Manivannan Sadhasivam wrote: > > On Mon, Jan 12, 2026 at 02:32:21PM +0530, Manivannan Sadhasivam wrote: > > > On Mon, Jan 12, 2026 at 10:27:45AM +0200, Andy Shevchenko wrote: > > > > On Mon, Jan 12, 2026 at 01:49:54PM +0530, Manivannan Sadhasivam wrote: > > > > > + Dmitry Torokhov (who was against this patch previously) > > > > > > > > > > On Mon, Jan 12, 2026 at 09:56:06AM +0200, Andy Shevchenko wrote: > > > > > > On Sat, Jan 10, 2026 at 12:26:21PM +0530, Manivannan Sadhasivam via B4 Relay wrote: > > > > > > > > > > > > > Because the software node backend of the fwnode API framework lacks an > > > > > > > implementation for the .device_get_match_data function callback. > > > > > > > > > > > > Maybe this is done on purpose. Have you thought about this aspect? > > > > > > > > > > IMO, software nodes were introduced to add sub-properties to the existing > > > > > firmware nodes, but it has usecase/potential to go beyond that. More below. > > > > > > > > Potential doesn't mean the necessity. > > > > > > > > > > > This makes it difficult to use(and/or test) a few drivers that originates > > > > > > > from DT world on the non-DT platform. > > > > > > > > > > > > How difficult? DSA implementation went to the way of taking DT overlay > > > > > > approach. Why that one can't be applied here? > > > > > > > > > > Sometimes you do not have any DT node at all. > > > > > > > > Yes, that is exactly the case I have referred to. The PCI core (in Linux) > > > > is able to create DT subtree on non-OF based platforms. > > > > > > > > > > Maybe I should look into creating dynamic DT node for the device and insert it > > > to the uart node. Theoretically it should work. > > > > > > > It worked flawlessly. So I sent v4 incorporating this design: > > https://lore.kernel.org/linux-pci/20260112-pci-m2-e-v4-0-eff84d2c6d26@oss.qualcomm.com/ > > > > Andy, I had to revive this old thread of a merged series as Krzk is not in > favour of adding DT overlay or dynamic OF nodes for these BT devices [1]. His > objections are due to the fact that we are just adding BT nodes of a > discoverable device (M.2 PCIe device) without any resources. So the node just > contains the compatible to match with the serdev driver and nothing else. > > And he suggested to use swnodes or other similar mechanisms to plug with the > serdev driver as that's the only thing we want here, not a true hardware > description. SW nodes are not for describing HW from scratch. They are for fixing missing pieces. If you can justify your case as a missing piece for the *existing* device (which is enumerated using standard mechanisms), you can add a property that fills the gap. Unfortunately I see that there are `PROPERTY_ENTRY_STRING("compatible", ...)` cases in the kernel (only 9 drivers so far), and I can't say if they describing missing pieces or a SW-made descriptions of the hardware. For the latter the DT/ACPI/other means but swnodes should be used. > Since you strongly objected the swnode approach in this series, I wanted to hear > your opinion before I rework the code. > [1] https://lore.kernel.org/linux-pci/768142f0-2638-41f3-a34f-dc80bb99eb7f@kernel.org -- With Best Regards, Andy Shevchenko