Received: by 2002:ac0:946b:0:0:0:0:0 with SMTP id j40csp126796imj; Thu, 14 Feb 2019 16:53:50 -0800 (PST) X-Google-Smtp-Source: AHgI3IZcF25y6y7WLjczeI4Us3TVhQngAXmM7ob46EEYUFgv6AvXKrIVLhiHmsjpzbsu+AeSznDI X-Received: by 2002:a17:902:f01:: with SMTP id 1mr7111952ply.41.1550192030403; Thu, 14 Feb 2019 16:53:50 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1550192030; cv=none; d=google.com; s=arc-20160816; b=NsofFIBgxH7qarHL097LkB7qip93Sz7FjN9ENJYe2D/8dNV48AUnfBE1QoP0fExEmm eee0Tl6w0/BNouSfBCKegql0E0kcGKSpKz+UkoEsePZa50EFvsX2nlBpFOAdN1TjspVa y8wXF0yk5lTB2S7qfEbiGYAHTPJxucE6J8jlf55jx+OS8aGba79Lb5er5R5ReD1TdCim 0qQUFTuUXeSO7yj4q3qNjSEaQPgAIZtSypeUPNLtLIxd5WXKUsBeF+Nd98LiYhIUq8Ge v/H5qiMq5zxO57Pnb94Py1lw4jnqegXwDKeJB5Z3sPNjmUdvmE9RbRN0SBwLuB+Y62Bt o0PA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=F8PM1pWE63rISTtBzLB/h/fxuf6LaecjwSPDPVcq/RU=; b=fbGPp5C083a3RLiuMHtQ3UlnMWNBa6EBu+W+55TRFKliEgtb6g0NGlc5zCu3PofWOI quuV0IZVjgs57uY+02hDVW+f6/9c14hN9X19qxm2SvE/HK1JmVGmxgiQJja5Dt3Xb90K Xk1b+TDayd20f3NEmLoZ07ezs9rX6BDbIdkulUBpKFkWpehNIvx11aPaWroQWndnOFsm YSEGm/jOEhK3U3CEWsrsSjEy0A6acyiinkL7N7fM2QtOpbEso+5dwanFDyGrNkFk/rTM 1OlpdyUNWJiEKqaiz/ka5hRGsxrYllZIlN/je4SPRp34+t3yCvhqw8o9H84L0AS3bfgP ZvHw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id y16si3773198pgh.33.2019.02.14.16.53.34; Thu, 14 Feb 2019 16:53:50 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2391670AbfBNQ3h (ORCPT + 99 others); Thu, 14 Feb 2019 11:29:37 -0500 Received: from foss.arm.com ([217.140.101.70]:46956 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726014AbfBNQ3g (ORCPT ); Thu, 14 Feb 2019 11:29:36 -0500 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.72.51.249]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 72B51EBD; Thu, 14 Feb 2019 08:29:36 -0800 (PST) Received: from e107981-ln.cambridge.arm.com (e107981-ln.cambridge.arm.com [10.1.197.40]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 5ECE73F575; Thu, 14 Feb 2019 08:29:34 -0800 (PST) Date: Thu, 14 Feb 2019 16:29:28 +0000 From: Lorenzo Pieralisi To: Kishon Vijay Abraham I Cc: Gustavo Pimentel , Alan Douglas , Shawn Lin , Heiko Stuebner , Bjorn Helgaas , Jingoo Han , linux-omap@vger.kernel.org, linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH v2 08/15] PCI: endpoint: Fix pci_epf_alloc_space to set correct MEM TYPE flags Message-ID: <20190214162928.GA32523@e107981-ln.cambridge.arm.com> References: <20190114111513.21618-1-kishon@ti.com> <20190114111513.21618-9-kishon@ti.com> <20190211173723.GA31035@e107981-ln.cambridge.arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Feb 13, 2019 at 07:17:14PM +0530, Kishon Vijay Abraham I wrote: > Hi Lorenzo, > > On 11/02/19 11:07 PM, Lorenzo Pieralisi wrote: > > On Mon, Jan 14, 2019 at 04:45:06PM +0530, Kishon Vijay Abraham I wrote: > >> pci_epf_alloc_space() sets the MEM TYPE flags to indicate a 32-bit > >> Base Address Register irrespective of the size. Fix it here to indicate > >> 64-bit BAR if the size is > 2GB. > >> > >> Signed-off-by: Kishon Vijay Abraham I > >> --- > >> drivers/pci/endpoint/pci-epf-core.c | 4 +++- > >> 1 file changed, 3 insertions(+), 1 deletion(-) > > > > This looks like a fix and should me marked as such. Does it work > > as as standalone patch if it gets backported ? > > Yeah, it should work. But the current users doesn't allocate > 2GB and some > EPC drivers configure their registers based on size. So nothing is broken > without this patch as such. I suspect you mean 4GB (here and the commit log), right ? I am checking the commit logs, aiming at merging the patches. Lorenzo