Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751494AbdFGI0S convert rfc822-to-8bit (ORCPT ); Wed, 7 Jun 2017 04:26:18 -0400 Received: from us-smtp-delivery-107.mimecast.com ([216.205.24.107]:25347 "EHLO us-smtp-delivery-107.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751462AbdFGI0Q (ORCPT ); Wed, 7 Jun 2017 04:26:16 -0400 Subject: Re: [PATCH v5 2/3] PCI: Add tango PCIe host bridge support From: Marc Gonzalez To: Bjorn Helgaas CC: Marc Zyngier , Thomas Gleixner , Robin Murphy , Lorenzo Pieralisi , Liviu Dudau , David Laight , linux-pci , Linux ARM , Thibaud Cornic , Phuong Nguyen , LKML , Mason References: <741766e5-cff2-db5f-d40b-6866e08fd966@sigmadesigns.com> <1802aae0-f97b-c437-c00e-5fa7c867286d@sigmadesigns.com> Message-ID: <654acba8-68b9-fb4c-4681-35af94b6bd74@sigmadesigns.com> Date: Wed, 7 Jun 2017 10:19:49 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49 MIME-Version: 1.0 In-Reply-To: <1802aae0-f97b-c437-c00e-5fa7c867286d@sigmadesigns.com> X-Originating-IP: [172.27.0.114] X-MC-Unique: UzLupUWuPzytmsyQ_2uxQQ-1 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 818 Lines: 26 On 31/05/2017 15:33, Marc Gonzalez wrote: > +static int tango_pcie_probe(struct platform_device *pdev) > +{ > + int ret = -EINVAL; > + void __iomem *base; > + struct resource *res; > + struct tango_pcie *pcie; > + struct device *dev = &pdev->dev; > + > + pr_err("MAJOR ISSUE: PCIe config and mem spaces are muxed\n"); > + pr_err("Tainting kernel... Use driver at your own risk\n"); > + add_taint(TAINT_FIRMWARE_WORKAROUND, LOCKDEP_STILL_OK); Hello Bjorn, In v4, your only comment was "[muxing config and mem spaces] is a major issue and possibly even a security problem [which requires at least an error message and a kernel taint]. Were there any other issues with the host bridge support? Or is the HW quirk/bug too severe to mainline the driver? (I would hate having to discard all that work though.) Regards.