Received: by 2002:ac0:946b:0:0:0:0:0 with SMTP id j40csp3029292imj; Mon, 11 Feb 2019 12:34:58 -0800 (PST) X-Google-Smtp-Source: AHgI3IZ0f/f2+Y0yNLLyrVfBujpKe1GfkaWby6dW8qla0gL8Ru1jgS9vqrcIjTXVRxOsQ7oNo0K4 X-Received: by 2002:a63:ce0e:: with SMTP id y14mr65639pgf.145.1549917298771; Mon, 11 Feb 2019 12:34:58 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1549917298; cv=none; d=google.com; s=arc-20160816; b=M0EjvlZDBNuGPEbMAPNG7qnsPkbTm/3wFDmus1HvXefcif9SJBwfTTup2adMARVRZw YagrwY84tBdhLDM7TI/sl7sGqqLOPaeBnK77sQN9oOtkXbjY7JdtQQkwJ1G2D8/PObEW OZUHog4viFphcqLNhM5ftB6ALhWeqENeQUcjM55NChSV0NCHai4TmmGK5Mh05ZVLQFZ0 i9jFoefjFJadWwtzG9ma4dlE42DeBCl7/jT3U4+arNbQUcfa1v/8VN59Kd9bTXgTaLE9 8HaM1N1wz4wa2lVJO58MXkMj5mEOhD000OrPXtUxiPQ1FZIyiveOlEXQ8SlHuBYa+wgk NPjA== 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=DAvGEKY/tSc3rlyWcihQrEgm4c/CdS4an6J37iPZKPE=; b=gaAbqs7GapIvzCp8zAEFFLAtBJpteXWCZuqawfxVeu81dWb+c/xuE4XgvfwLTRdebU zU2ROTjyUykkbrdCymtFSodDgiC+Ju3Y+cY5dZ+uRyKjPey72qxWr+q+PYhddoEQj2QH EEgJvh2NMV6NOCzv3UAtLwcdjXbDa6canqVrkCMHKgTMX9eTtyJ+XKSaQ/pPt5z6oZu9 1FtKoHKr1jv72A9P6SrZ+rjx3//Uz2r4O2BuxG3JPn4q9xDSzd42uowUpQvw+hCXmTeT pOmO7caHWimQtcm1bpJ039u5A/UopCOa6LVSQBAIKwaLGU42EzKhmEvhjQeloKmX7MW+ UXzg== 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 d31si4631505pgl.515.2019.02.11.12.34.42; Mon, 11 Feb 2019 12:34:58 -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 S1732158AbfBKRho (ORCPT + 99 others); Mon, 11 Feb 2019 12:37:44 -0500 Received: from foss.arm.com ([217.140.101.70]:54772 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731376AbfBKRhn (ORCPT ); Mon, 11 Feb 2019 12:37:43 -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 3C326EBD; Mon, 11 Feb 2019 09:37:43 -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 287643F675; Mon, 11 Feb 2019 09:37:41 -0800 (PST) Date: Mon, 11 Feb 2019 17:37:32 +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: <20190211173723.GA31035@e107981-ln.cambridge.arm.com> References: <20190114111513.21618-1-kishon@ti.com> <20190114111513.21618-9-kishon@ti.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190114111513.21618-9-kishon@ti.com> 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 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 ? Lorenzo > diff --git a/drivers/pci/endpoint/pci-epf-core.c b/drivers/pci/endpoint/pci-epf-core.c > index 825fa24427a3..8bfdcd291196 100644 > --- a/drivers/pci/endpoint/pci-epf-core.c > +++ b/drivers/pci/endpoint/pci-epf-core.c > @@ -131,7 +131,9 @@ void *pci_epf_alloc_space(struct pci_epf *epf, size_t size, enum pci_barno bar) > epf->bar[bar].phys_addr = phys_addr; > epf->bar[bar].size = size; > epf->bar[bar].barno = bar; > - epf->bar[bar].flags = PCI_BASE_ADDRESS_SPACE_MEMORY; > + epf->bar[bar].flags |= upper_32_bits(size) ? > + PCI_BASE_ADDRESS_MEM_TYPE_64 : > + PCI_BASE_ADDRESS_MEM_TYPE_32; > > return space; > } > -- > 2.17.1 >