From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752982AbeB0L7Q (ORCPT ); Tue, 27 Feb 2018 06:59:16 -0500 Received: from bastet.se.axis.com ([195.60.68.11]:58788 "EHLO bastet.se.axis.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752925AbeB0L7O (ORCPT ); Tue, 27 Feb 2018 06:59:14 -0500 From: Niklas Cassel To: kishon@ti.com, linux-pci@vger.kernel.org Cc: Niklas Cassel , linux-kernel@vger.kernel.org Subject: [PATCH v3 0/3] PCI endpoint 64-bit BAR fixes Date: Tue, 27 Feb 2018 12:59:04 +0100 Message-Id: <20180227115908.14593-1-niklas.cassel@axis.com> X-Mailer: git-send-email 2.14.2 X-TM-AS-GCONF: 00 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org PCI endpoint fixes to improve the way 64-bit BARs are handled. There are still future improvements that could be made: pci-epf-test.c always allocates space for 6 BARs, even when using 64-bit BARs (which really only requires us to allocate 3 BARs). pcitest.sh will print "NOT OKAY" for BAR1, BAR3, and BAR5 when using 64-bit BARs. This could probably be improved to say something like "N/A (64-bit BAR)". Niklas Cassel (3): PCI: endpoint: Handle 64-bit BARs properly misc: pci_endpoint_test: Handle 64-bit BARs properly PCI: designware-ep: Return an error when requesting a too large BAR size drivers/misc/pci_endpoint_test.c | 12 +++++++----- drivers/pci/dwc/pcie-designware-ep.c | 5 +++++ drivers/pci/endpoint/functions/pci-epf-test.c | 2 ++ 3 files changed, 14 insertions(+), 5 deletions(-) -- 2.14.2