Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933616AbbGUVyN (ORCPT ); Tue, 21 Jul 2015 17:54:13 -0400 Received: from arroyo.ext.ti.com ([192.94.94.40]:34575 "EHLO arroyo.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933511AbbGUVyL (ORCPT ); Tue, 21 Jul 2015 17:54:11 -0400 From: Murali Karicheri To: , , , , Subject: [Resend: PATCH] PCI: designware: fix the boot noise for missing *config* reg space Date: Tue, 21 Jul 2015 17:54:11 -0400 Message-ID: <1437515651-20883-1-git-send-email-m-karicheri2@ti.com> X-Mailer: git-send-email 1.9.1 MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1460 Lines: 38 Currently on Keystone SoCs, boot up log shows an unnecessary boot noise as follows:- [ 0.365823] keystone-pcie 21021000.pcie: missing *config* reg space Keystone uses older version of designware h/w that doesn't have ATU support. So va_cfg0_base and va_cfg1_base are already set up in ks_dw_pcie_host_init() before calling dw_pcie_host_init() and they point to the remote config space address va (both same for Keystone). So add a check to avoid this boot noise on Keystone. Signed-off-by: Murali Karicheri --- - Resend with "PCI: designware" prefix in subject drivers/pci/host/pcie-designware.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/pci/host/pcie-designware.c b/drivers/pci/host/pcie-designware.c index 69486be..b48b8a2 100644 --- a/drivers/pci/host/pcie-designware.c +++ b/drivers/pci/host/pcie-designware.c @@ -388,7 +388,7 @@ int dw_pcie_host_init(struct pcie_port *pp) addrp = of_get_address(np, index, NULL, NULL); pp->cfg0_mod_base = of_read_number(addrp, ns); pp->cfg1_mod_base = pp->cfg0_mod_base + pp->cfg0_size; - } else { + } else if (!pp->va_cfg0_base) { dev_err(pp->dev, "missing *config* reg space\n"); } -- 1.9.1 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/