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 6B6C3C64EC7 for ; Tue, 14 Feb 2023 04:42:29 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229797AbjBNEm2 (ORCPT ); Mon, 13 Feb 2023 23:42:28 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57722 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229604AbjBNEmY (ORCPT ); Mon, 13 Feb 2023 23:42:24 -0500 Received: from mail-pf1-x42e.google.com (mail-pf1-x42e.google.com [IPv6:2607:f8b0:4864:20::42e]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id DFB0817148 for ; Mon, 13 Feb 2023 20:42:22 -0800 (PST) Received: by mail-pf1-x42e.google.com with SMTP id 16so9383737pfo.8 for ; Mon, 13 Feb 2023 20:42:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ventanamicro.com; s=google; h=in-reply-to:content-transfer-encoding:content-disposition :mime-version:references:message-id:subject:cc:to:from:date:from:to :cc:subject:date:message-id:reply-to; bh=IytFRD13wyHkORVwldfX0cj+olMfAcIjoNBkr5UdNv4=; b=CpaV4dVNUa0pCGK5PDzg426zSTmY7CxCQXGkQc/due8N9WbSNf6YnYNaaZJlzPQzRU 4s0iVdibYJ1vax2anrQWNpvuZAStqApzDgYGWguJpL56MKYEoQgZaI+vmNIiamU8lFDV tyzEA6plQxp7DGNo3rrpCE6kEmRoWISwepZNgWnkKgHTSGrSSjYfZw8BEh9uYnOmnu1y 3zFRl0bQ3jXcROaXtBLT4UglIskyT4lWVFuYiMxAiHOSaik7J+HXrvgqyyWxXOa5eCoY Ns5YOAcrrMGyhU6lBeuM1ckz+k2ZSKU+hls5ed89+Q3rPD5x9fgKjshULNq9RO13E66x s13A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:content-transfer-encoding:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=IytFRD13wyHkORVwldfX0cj+olMfAcIjoNBkr5UdNv4=; b=ek8VIz5EJvuOsBOjbHTrCJkCM9YiRP05n4GKXo3vtlilNieLfQUpv/oKjzICAv6kFD xgqn82Fz5JxLt8ruuOLuLS0zbBBiY95tTJir5gdtvJuk25MN8Jih5tfuDnvTKzoy76Cj A+GcGhm8IQaGK2hwC3mmOPF0cVq0e+9+vFqx4XaBAJPQdBh9FLpFzBcsWJOcqVeBEM2x T3Qs8DYzbx6fG4HulxXo7L3dqtwXayOGpAnm+nILgB60PfKZuG3lp9DmxybMFZyaiooH oCu3bW5Jf2dwj10Hf+aIb7QlT5ASkle0iWFh85uJIpATF/jtypadED4n/5+3LwX+DAq5 XYLQ== X-Gm-Message-State: AO0yUKVPy8IaghV6DvDWcL9S6aLk/UayZmBC0vL448I6/rFZduXo6IE8 1H0bhJbLb9NS4n+DbP1HOGTpqw== X-Google-Smtp-Source: AK7set/4s/cLnv837AHxP+fni/9CnhX3OJuvf1GQstOD0qP6CHuBqukJFcvLiwos3jjiUZAL1jHLxQ== X-Received: by 2002:aa7:973d:0:b0:5a8:be36:65a8 with SMTP id k29-20020aa7973d000000b005a8be3665a8mr750675pfg.27.1676349742500; Mon, 13 Feb 2023 20:42:22 -0800 (PST) Received: from sunil-laptop ([49.206.14.226]) by smtp.gmail.com with ESMTPSA id i9-20020aa79089000000b0058173c4b3d1sm8285835pfa.80.2023.02.13.20.42.16 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 13 Feb 2023 20:42:22 -0800 (PST) Date: Tue, 14 Feb 2023 10:12:13 +0530 From: Sunil V L To: Jessica Clarke Cc: Palmer Dabbelt , Albert Ou , "Rafael J . Wysocki" , Len Brown , Thomas Gleixner , Marc Zyngier , Daniel Lezcano , Jonathan Corbet , Anup Patel , linux-doc@vger.kernel.org, Atish Patra , linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org, linux-riscv@lists.infradead.org, Andrew Jones Subject: Re: [PATCH 06/24] RISC-V: ACPI: Add PCI functions to build ACPI core Message-ID: References: <20230130182225.2471414-1-sunilvl@ventanamicro.com> <20230130182225.2471414-7-sunilvl@ventanamicro.com> <33DF2416-0629-414D-B50E-D99CB55A83AA@jrtc27.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <33DF2416-0629-414D-B50E-D99CB55A83AA@jrtc27.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Feb 13, 2023 at 05:26:13PM +0000, Jessica Clarke wrote: > On 30 Jan 2023, at 18:22, Sunil V L wrote: > > > > When CONFIG_PCI is enabled, ACPI core expects few arch > > functions related to PCI. Add those functions so that > > ACPI core gets build. These are levraged from arm64. > > Presumably this is pretty generic and applies to anything without x86 > weirdness. Copying all this supposedly architecture specific code > that’s really generic seems like bad practice to me as an outsider. > Should this not be unifying the two in a shared location as has been > done for other subsystems? Make sense. Let me add these functions in a common location pci-acpi.c for RISC-V. Other architectures can migrate to this in future. Thanks, Sunil