From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mgamail.intel.com (mgamail.intel.com [192.198.163.15]) (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 2BD11423A84; Tue, 20 Jan 2026 21:28:50 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=192.198.163.15 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1768944534; cv=none; b=YdmxAhv+c8PcwGvyuxFOlcLf+rzJpZl5AeykUWqd+u2Vjn+PU7aLaxHa5Awm/aOotBc1YN7xsfhnc7OhbMTBqh0eaZVY8fhCDi9CxK1L/KheESvZon4QCbfvr5ZJnodNigsXww4LUe9HhrCh16K0tk98fVoiwHD0z222zoh7BVA= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1768944534; c=relaxed/simple; bh=VAkJ/KITOoPPwFJHwdAoEzuCuhXukFgLDyfcXhDmS98=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=iF/I3zqZ3Y4+qGkwpSWr6KyUarB3CRnIrtriKjGwqzvrQvV58h7LY5Mbqv2WUcb3eq0I88Hogv8xlYfPyUzFvQPuEMl9gzK3qtXVD/AyYqrARtv9AR1EKoYJ+sBVoi4ShSpuZhQgfV5ExEya6qz91ci2RWsGACq68K+oXMfzMfQ= 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=HK/bV4Ro; arc=none smtp.client-ip=192.198.163.15 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="HK/bV4Ro" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1768944532; x=1800480532; h=date:from:to:cc:subject:message-id:references: mime-version:content-transfer-encoding:in-reply-to; bh=VAkJ/KITOoPPwFJHwdAoEzuCuhXukFgLDyfcXhDmS98=; b=HK/bV4RoZDAlMPRij7f+uUJGOPdlpBTyME9LBHfeJV/2jDNXPfQVt4tD pdETsyYiBPnanhfS7TFewp6rs4cDKTMsk7qYqNX6zucASsFEhK0bAbP7z euDshXns6keiplxpjI1Lbw1ZKqxO/qSgn/tDCQpdKWjobAM+edhVJVy0T RZ5f68M9wWRTJ7qoAwM4HxbzPkiqFiHiiL9/rTlMPpRRWWLU99A76VGFE l8un6ZML+gCPi5/jUXbZe3v/i1xtt3D2PCM/SyEzW6bKFHPDQ6+zqBUdD 0FIvy9SEmZrke1wQrB4fWD6AOuMEXxwAT5h0rAjkPpEs1s+ZVb9Yo7aYE Q==; X-CSE-ConnectionGUID: jBALRQ+xROqaoffM3qGlYA== X-CSE-MsgGUID: qd22lN2JQFKwH9IpqeljqQ== X-IronPort-AV: E=McAfee;i="6800,10657,11677"; a="70257757" X-IronPort-AV: E=Sophos;i="6.21,241,1763452800"; d="scan'208";a="70257757" Received: from fmviesa008.fm.intel.com ([10.60.135.148]) by fmvoesa109.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 20 Jan 2026 13:28:50 -0800 X-CSE-ConnectionGUID: dAWGnrmlTsS7OPsMmnwgMA== X-CSE-MsgGUID: ipFP5vVHQK6X3ee9IwH9Xw== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.21,241,1763452800"; d="scan'208";a="206477213" Received: from dhhellew-desk2.ger.corp.intel.com (HELO localhost) ([10.245.244.240]) by fmviesa008-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 20 Jan 2026 13:28:47 -0800 Date: Tue, 20 Jan 2026 23:28:45 +0200 From: Andy Shevchenko To: Mark Brown Cc: Abdurrahman Hussain , Michal Simek , Greg Kroah-Hartman , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Andrew Lunn , linux-spi@vger.kernel.org, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v3 3/3] spi: xilinx: use device property accessors. Message-ID: References: <980ad372-a2c7-417c-91f9-4958d3d1aaca@sirena.org.uk> <4831B269-DFC1-40E0-96B7-67981AC72562@nexthop.ai> <6e06696e-09a4-46e0-98fa-252690b888e0@sirena.org.uk> <80A8F67E-7A01-4F9F-9D84-29722678A2CE@nexthop.ai> <817bcc43-7f10-4329-8924-6c375eb73ff2@sirena.org.uk> Precedence: bulk X-Mailing-List: devicetree@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <817bcc43-7f10-4329-8924-6c375eb73ff2@sirena.org.uk> Organization: Intel Finland Oy - BIC 0357606-4 - c/o Alberga Business Park, 6 krs, Bertel Jungin Aukio 5, 02600 Espoo On Tue, Jan 20, 2026 at 09:04:58PM +0000, Mark Brown wrote: > On Tue, Jan 20, 2026 at 11:11:44AM -0800, Abdurrahman Hussain wrote: > > > On Jan 20, 2026, at 10:45 AM, Mark Brown wrote: > > > On Mon, Jan 19, 2026 at 04:20:06PM -0800, Abdurrahman Hussain wrote: > > Let me once more renew my plea: > > > > To repeat once again: > > > > | Please fix your mail client to word wrap within paragraphs at something > > > | substantially less than 80 columns. Doing this makes your messages much > > > | easier to read and reply to. > > > > To drivers that are used on ACPI systems, yes. Many devices wouldn't be > > > used on ACPI systems, or would be expected to be exposed differently > > > (for example, hidden behind AML). > > > This is not for a normal off the shelf server. In our case we are building an embedded > > switch with an AMD CPU and Xilinx FPGAs that happens to use EDK2 based BIOS and ACPI. > > Sure, AFAICT it's mostly a PCI card with a bunch of stuff on it from a > software point of view. > > > >> I am just trying to get this 2-line small change merged so we can start using the standard spi-xilinx driver today. I am not trying to boil the ocean. > > > > I mean, adding a HID wouldn't take substantially more code. > > > We could, but we don’t own the Xilinx IP blocks. Are we not justified in using PRP0001 > > hack until the driver owner adds the HIDs? Wasn’t PRP0001 created as an escape hatch for > > these kind of scenarios? > > No, it's more there for the cases where embedded ACPI systems need to > import non-trivial DT bindings so they can avoid having to respecify > things that ACPI really doesn't cope with or for local hacks. See > Andy's reply earlier in the thread: > > https://lore.kernel.org/r/aW9JihlsjnJ-uBul@black.igk.intel.com > > AFAICT for ACPI the HID assigment is a bit of a free for all in practice > - board vendors generally seem perfectly happy to just pick something if > the silicon vendor didn't do something. Just look at all the parts with > INTxxxx IDs! That said Michal is on the thread so hopefully that's not INTxxxx was a (historical) mistake, but look at the correct one INTCxxxx which has listed several components Intel doesn't own. Because ACPI HID it's not only about the component in use, it's also about integration of that component in the platform environment. Hence it might require (platform) specific quirks. > an issue and we can get something from Xilinx fairly easily. Exactly! Either from them, or AMD can do, or even NextHop.AI. If you have not yet registered vendor ID, it's pretty much straightforward process. Here is the pointer for your convenience: https://uefi.org/PNP_ACPI_Registry -- With Best Regards, Andy Shevchenko