Received: by 2002:a05:6a10:5bc5:0:0:0:0 with SMTP id os5csp4180278pxb; Tue, 2 Nov 2021 05:37:59 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwNFg33Fm6iWB5MokJPpSHh28vpinjDIUsUQcnMWYYw+/+9NH1mNpnMcxs9TZc3t5fb2nlt X-Received: by 2002:a17:906:69c7:: with SMTP id g7mr43426892ejs.365.1635856678847; Tue, 02 Nov 2021 05:37:58 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1635856678; cv=none; d=google.com; s=arc-20160816; b=0pIZcoiwNsexlVUMxYDWeZk+sLU7xWXuMNznsBjN/kXhFuTVticQCMODVhtmSGPFSy cVxmRo3LtT7VriVocR5Z7CmWcuSsa5xQ0Vv/b9h9T2xfBGAbhooaA6CxP5UytFnJ8Az0 8aoPbUWdhI6QyLytfs+yZKehIxBahtOIyAtpOV3kMrfdUjpR6pt+hbmaJpRYOanSyzTD fdd6a+yEcXLCnPw7KmtX168E4RNmRDlomqReV6g+AoC3zgNrgnL3nfhnKWm6EH6LomdC mB281CGtCaXCWi0T+UG8icxzCL6POCbSCUZwjnVtRHA0f+DJyWojf9IiYmReuoQ15cS9 J49g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :user-agent:references:message-id:in-reply-to:subject:cc:to:from :date; bh=2kDPvDQcL0d7+gpn8p1fRQwx+Kf+z72k7e6L6Mv3ENs=; b=ybenSdXiGsm8SNuhUvesOw5ayxnuAEn1ljr553uz+Z57MUe5phoFIQ20baXtsObCZT mf2DKM6gDehk1NocO9MAtWYlDPTv9TV+z8c3CcccnTDU68xYF+wjez2bmQSBJ6w2nJDj 8l2vvw36uM4qNMckjdt7N0NEIjle9/G+IxoKWVPCxgi9ojgr4+nqmAkCOoGEpvHMEUpF 4UKAMnZAUNPiXZffXIgJQr7r1MuaVqznFpDPif9+Qy50I/cZ2jQ3Yh6e6lx5HMm7k2B5 ImLOSBzCz+hdpRM6eom7kKa+7nNFYyc+IFLhqi32r4trUQ1DnDz/uo7mkWe4H/NXI0Yi e9Ew== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id ne20si34891226ejc.429.2021.11.02.05.37.33; Tue, 02 Nov 2021 05:37:58 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230100AbhKBMiS (ORCPT + 99 others); Tue, 2 Nov 2021 08:38:18 -0400 Received: from angie.orcam.me.uk ([78.133.224.34]:36538 "EHLO angie.orcam.me.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229530AbhKBMiR (ORCPT ); Tue, 2 Nov 2021 08:38:17 -0400 Received: by angie.orcam.me.uk (Postfix, from userid 500) id 3024692009D; Tue, 2 Nov 2021 13:35:41 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by angie.orcam.me.uk (Postfix) with ESMTP id 29DCA92009B; Tue, 2 Nov 2021 12:35:41 +0000 (GMT) Date: Tue, 2 Nov 2021 12:35:41 +0000 (GMT) From: "Maciej W. Rozycki" To: =?UTF-8?Q?Pali_Roh=C3=A1r?= cc: Thomas Bogendoerfer , Russell King , Andrew Lunn , Sebastian Hesselbarth , Gregory Clement , Jason Gunthorpe , linux-arm-kernel@lists.infradead.org, linux-mips@vger.kernel.org, linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] PCI: Marvell: Update PCIe fixup In-Reply-To: <20211102100034.rhcb3k2jvr6alm6y@pali> Message-ID: References: <20211101150405.14618-1-pali@kernel.org> <20211102084241.GA6134@alpha.franken.de> <20211102090246.unmbruykfdjabfga@pali> <20211102094700.GA7376@alpha.franken.de> <20211102100034.rhcb3k2jvr6alm6y@pali> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 2 Nov 2021, Pali Rohár wrote: > > > >From all what I saw, I'm sure that this device with this specific > > > characteristics is really (non-compliant) Marvell PCIe controller. > > > > just nitpicking, it's a Galileo PCI bridge and not PCIe. > > Marvell acquired Galileo Technology in the past, so it is possible that > this bad design is originated in Galileo. And maybe same for PCIe from > PCI. At least PCI vendor id for all (new) PCIe controllers is this one. Umm, PCIe is so different hardware-wise from PCI I doubt there's any chance for errata to be carried across. Plus the MIPS SysAD bus is so different from other CPU buses. And we're talking 20+ years old Galileo devices here. None of the Galileo system controllers I came across had the class code set incorrectly. > > > But I do not have this hardware to verify it. > > > > I still have a few Cobalt systems here. > > Perfect! It would help if you could provide 'lspci -nn -vv' output from > that system. In case you have very old version of lspci on that system > you could try to run it with '-xxxx' (or '-xxx') which prints hexdump > and I can parse it with local lspci. For the record here's one from a core card used with a Malta (as with arch/mips/pci/fixup-malta.c); it has a newer 64120A chip (marked as an engineering sample BTW): 00:00.0 Host bridge: Marvell Technology Group Ltd. GT-64120/64120A/64121A System Controller (rev 11) 00: ab 11 20 46 47 01 80 22 11 00 00 06 00 20 00 00 10: 00 00 00 00 00 00 00 08 00 00 00 00 00 00 00 00 20: 00 00 e0 1b 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 ff 01 00 00 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 The lack of a quirk with a platform does not mean it cannot have a certain PCI/e device. As I recall various Atlas/Malta core cards had any of the three device variants covered by this vendor:device ID and later batches were actually indeed marked Marvell rather than Galileo. Maciej