From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jon Hunter Subject: Re: [PATCH V3 1/2] arm64: tegra: Re-order PCIe aperture mappings to support ACPI boot Date: Mon, 29 Jun 2020 14:31:38 +0100 Message-ID: References: <20200106082709.14370-1-vidyas@nvidia.com> <20200110191500.9538-1-vidyas@nvidia.com> <20200110191500.9538-2-vidyas@nvidia.com> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20200110191500.9538-2-vidyas@nvidia.com> Content-Language: en-US Sender: linux-acpi-owner@vger.kernel.org To: Vidya Sagar , bhelgaas@google.com, lorenzo.pieralisi@arm.com, rjw@rjwysocki.net, lenb@kernel.org, andrew.murray@arm.com, treding@nvidia.com Cc: linux-tegra@vger.kernel.org, linux-pci@vger.kernel.org, linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org, kthota@nvidia.com, mmaddireddy@nvidia.com, sagar.tv@gmail.com List-Id: linux-tegra@vger.kernel.org Hi Sagar, On 10/01/2020 19:14, Vidya Sagar wrote: > Re-order Tegra194's PCIe aperture mappings to have IO window moved to > 64-bit aperture and have the entire 32-bit aperture used for accessing > the configuration space. This makes it to use the entire 32MB of the 32-bit > aperture for ECAM purpose while booting through ACPI. > > Signed-off-by: Vidya Sagar Any reason why we should not merge this change, even if patch 2/2 is not accepted? If there is no harm in us merging this, this would be one less change for us to carry out-of-tree. If so, can you update and re-post for 5.9? Cheers Jon -- nvpublic 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 X-Spam-Level: X-Spam-Status: No, score=-5.6 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 19BAAC433E1 for ; Mon, 29 Jun 2020 18:52:01 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id EE06F20656 for ; Mon, 29 Jun 2020 18:52:00 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=nvidia.com header.i=@nvidia.com header.b="SHCJ5JM/" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728319AbgF2Sv6 (ORCPT ); Mon, 29 Jun 2020 14:51:58 -0400 Received: from hqnvemgate26.nvidia.com ([216.228.121.65]:18046 "EHLO hqnvemgate26.nvidia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729702AbgF2Svx (ORCPT ); Mon, 29 Jun 2020 14:51:53 -0400 Received: from hqpgpgate102.nvidia.com (Not Verified[216.228.121.13]) by hqnvemgate26.nvidia.com (using TLS: TLSv1.2, DES-CBC3-SHA) id ; Mon, 29 Jun 2020 06:31:34 -0700 Received: from hqmail.nvidia.com ([172.20.161.6]) by hqpgpgate102.nvidia.com (PGP Universal service); Mon, 29 Jun 2020 06:31:47 -0700 X-PGP-Universal: processed; by hqpgpgate102.nvidia.com on Mon, 29 Jun 2020 06:31:47 -0700 Received: from [10.26.75.188] (10.124.1.5) by HQMAIL107.nvidia.com (172.20.187.13) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 29 Jun 2020 13:31:40 +0000 Subject: Re: [PATCH V3 1/2] arm64: tegra: Re-order PCIe aperture mappings to support ACPI boot To: Vidya Sagar , , , , , , CC: , , , , , , References: <20200106082709.14370-1-vidyas@nvidia.com> <20200110191500.9538-1-vidyas@nvidia.com> <20200110191500.9538-2-vidyas@nvidia.com> From: Jon Hunter Message-ID: Date: Mon, 29 Jun 2020 14:31:38 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.8.0 MIME-Version: 1.0 In-Reply-To: <20200110191500.9538-2-vidyas@nvidia.com> X-Originating-IP: [10.124.1.5] X-ClientProxiedBy: HQMAIL101.nvidia.com (172.20.187.10) To HQMAIL107.nvidia.com (172.20.187.13) Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: 7bit DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nvidia.com; s=n1; t=1593437494; bh=Y32CfHcMUWKKF9wD0CLFw8La6QEVGFVAMOsFhmKdfEU=; h=X-PGP-Universal:Subject:To:CC:References:From:Message-ID:Date: User-Agent:MIME-Version:In-Reply-To:X-Originating-IP: X-ClientProxiedBy:Content-Type:Content-Language: Content-Transfer-Encoding; b=SHCJ5JM/tbcA1imuBapYWSJr6z+o4OojHikk4j61y7FE/MkNF54FhwyT08IMnjadW lHTOBpjK6/7Fj289JNT9INlUuWwXTI4Y+81NRoDs7DLuDK5EPg/dW/qU4MZ9DmvAVM gfivYDmVRoUITMwz4H+8CmISt8nEBI9bJSy48Vxzfqo6sixPDGCsAOi0qEeAM2wAAc PkYY7LbPQa7d8ZiPLf6HDYMfg4wYlUEIkOribMuqvsIMFnRfI2n1mCzvkn1F1e8VIj lMpP0hNtbkeybDwNSPr8ubqADxgY+pBCDAy5o4lvgK4vnUiAVenSFo2B9sXKEgYsJ3 Z2KSQjp2XTjsg== Sender: linux-acpi-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-acpi@vger.kernel.org Hi Sagar, On 10/01/2020 19:14, Vidya Sagar wrote: > Re-order Tegra194's PCIe aperture mappings to have IO window moved to > 64-bit aperture and have the entire 32-bit aperture used for accessing > the configuration space. This makes it to use the entire 32MB of the 32-bit > aperture for ECAM purpose while booting through ACPI. > > Signed-off-by: Vidya Sagar Any reason why we should not merge this change, even if patch 2/2 is not accepted? If there is no harm in us merging this, this would be one less change for us to carry out-of-tree. If so, can you update and re-post for 5.9? Cheers Jon -- nvpublic