From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (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 498B1394786; Thu, 5 Mar 2026 14:54:09 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=185.176.79.56 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1772722451; cv=none; b=I13hV5xF2bvPGZ4V5OqbHKIfjIQYlEhix0U4P9pE2rl5CJ6gV88y4YqI9HuJ0PLjSRC6StGASO0ktjFqNZjVvN2rB7MOUUWSPzqbfKVBZpmxF6Dwb0AJJomz3M/y3rtw0Z2UeV6R0K8oygN4Abpk4H/4byL5IgSKExDEd12YMVM= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1772722451; c=relaxed/simple; bh=e9jryshronyw/hf+XUuhNDCAysBrxR3TuZBcZe/Tgdc=; h=Date:From:To:CC:Subject:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=Yt+0cO9A0zsOl6GkOTDcmthYizhX/imDz2pjvaXVw21CPvvWv6m+XsELC0CkLLcdGnMPnq56PPkiLQ1jjnnJZPNml+Jf0A+DMqwEkBwUuh3/6ziEBvrTd0lsQ4ViFkKqhPQQM8TEwxo+liLOd95TmLv+54BBiCwtx0zqM78NAno= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=huawei.com; spf=pass smtp.mailfrom=huawei.com; arc=none smtp.client-ip=185.176.79.56 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=huawei.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=huawei.com Received: from mail.maildlp.com (unknown [172.18.224.150]) by frasgout.his.huawei.com (SkyGuard) with ESMTPS id 4fRXb85pd4zHnGkd; Thu, 5 Mar 2026 22:53:08 +0800 (CST) Received: from dubpeml500005.china.huawei.com (unknown [7.214.145.207]) by mail.maildlp.com (Postfix) with ESMTPS id A5CEC4056B; Thu, 5 Mar 2026 22:54:06 +0800 (CST) Received: from localhost (10.203.177.15) by dubpeml500005.china.huawei.com (7.214.145.207) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1544.11; Thu, 5 Mar 2026 14:54:04 +0000 Date: Thu, 5 Mar 2026 14:54:03 +0000 From: Jonathan Cameron To: fengchengwen CC: Huacai Chen , , , Jonathan Corbet , Shuah Khan , Catalin Marinas , Will Deacon , WANG Xuerui , "Paul Walmsley" , Palmer Dabbelt , Albert Ou , Alexandre Ghiti , Thomas Gleixner , Ingo Molnar , Borislav Petkov , Dave Hansen , , "H. Peter Anvin" , "Rafael J. Wysocki" , Len Brown , Andy Gospodarek , Eric Van Tassell , Ajit Khaparde , Somnath Kotur , , , , , , , , , , , , , , , , Subject: Re: [PATCH v2] PCI/TPH: Fix get cpu steer-tag fail on ARM64 platform Message-ID: <20260305145403.0000394e@huawei.com> In-Reply-To: <795a9167-6c49-4c7c-9a36-385bf543cacf@huawei.com> References: <20260303003625.39035-1-fengchengwen@huawei.com> <20260305083650.54611-1-fengchengwen@huawei.com> <795a9167-6c49-4c7c-9a36-385bf543cacf@huawei.com> X-Mailer: Claws Mail 4.3.0 (GTK 3.24.42; x86_64-w64-mingw32) Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-ClientProxiedBy: lhrpeml100009.china.huawei.com (7.191.174.83) To dubpeml500005.china.huawei.com (7.214.145.207) > >> + ret = acpi_get_cpu_acpi_id(cpu); > > Can we use get_acpi_id_for_cpu() directly? Then just x86 needs a wrapper. > > Yes, it indeed simple. > > But I prefer to have the acpi_ prefix for such API names because it's a cross-subsystem API reference. Can we just do a global rename of get_acpi_id_for_cpu() as a precursor patch? Then this just becomes adding x86 implementation and using it on all architectures. J