Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp4046300ybi; Mon, 3 Jun 2019 04:56:52 -0700 (PDT) X-Google-Smtp-Source: APXvYqzvsIFSm3cpYOS+OKdhROOodg7czhw2f3lHQYAqr+4tTPylEN8JRpCFohth5XinaXngSyJa X-Received: by 2002:a65:520b:: with SMTP id o11mr28069860pgp.184.1559563012370; Mon, 03 Jun 2019 04:56:52 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1559563012; cv=none; d=google.com; s=arc-20160816; b=eT1cV/bfgn+hA67JX0pjTYKoDf+S90r9nT8qOwdepyrDZxei2PZOcxz1mEjltkdmtf 1xxSabIDhjCuCcs7AiKafFkC5UUK8V84KOvUoX09stbsZqRKQn95drLYDEcsrzoAZSQ9 ieyJ1VGJ5rGIHSeMc35HgDNa+0feCawYFmyJl4H70PyYoSeh/F+HLjEFO3GzVV+DVUUF lsvqXCoiYrR3DzU1FJqDVdaCEELg7+Ad1DOxGdtkZmWjO4l0s/88Qp6OG9in1aYWDOq9 xJqw2xi5bAFpeMkQ5P3fa27LoKWYgIKPLMKNWjOKQ4nKrmrJ/M+/fO2Xfi46/00CJB9u ubZA== 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=1fXvUTzg7+czicqP2Tw8YjHUrA829mxLDCl0DQHPwI0=; b=GzWrHKvKH18EvSNid30jnziOoAsfqZj96B5DVIUV9Pct5EJFFKAhIS+xm83n2iyuaL 8OBU0DhT9FJMYqNZD3tVlRBsGVG1WfeKX3uPuEmX298QhG5Wca7ozr4n4R7FSUlHc0ZC Bv+FsbcjgMnlr3i1f8ehUvsnZeKtXf+UTq5v7jrFCa/hCOgQrZeECCfxsCVs7b4ZBlz+ ZyPKFu+uGFeGQfaNBlXj+TzBYwRGFSSpwxJg2uSBlVflg7VDfJ9cxPcG/Fcv3dwGUDqj AXIGz+Wd8nk2Y+/40EJD2H1hFVjn1buFekAcS3xd7TObF18JEDHhB5o1UUKPkj7Cssep gaOA== 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 g8si17985481pgd.64.2019.06.03.04.56.34; Mon, 03 Jun 2019 04:56:52 -0700 (PDT) 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 S1727598AbfFCKHK (ORCPT + 99 others); Mon, 3 Jun 2019 06:07:10 -0400 Received: from bmailout1.hostsharing.net ([83.223.95.100]:44607 "EHLO bmailout1.hostsharing.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726369AbfFCKHK (ORCPT ); Mon, 3 Jun 2019 06:07:10 -0400 Received: from h08.hostsharing.net (h08.hostsharing.net [IPv6:2a01:37:1000::53df:5f1c:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.hostsharing.net", Issuer "COMODO RSA Domain Validation Secure Server CA" (not verified)) by bmailout1.hostsharing.net (Postfix) with ESMTPS id DF79B30001EA2; Mon, 3 Jun 2019 12:07:07 +0200 (CEST) Received: by h08.hostsharing.net (Postfix, from userid 100393) id B1DDD31CF9; Mon, 3 Jun 2019 12:07:07 +0200 (CEST) Date: Mon, 3 Jun 2019 12:07:07 +0200 From: Lukas Wunner To: Abhishek Sahu Cc: Bjorn Helgaas , linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org Subject: Re: [PATCH 2/2] PCI: Create device link for NVIDIA GPU Message-ID: <20190603100707.yhw4fu54vt3ykvd5@wunner.de> References: <20190531050109.16211-1-abhsahu@nvidia.com> <20190531050109.16211-3-abhsahu@nvidia.com> <20190531203908.GA58810@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20170113 (1.7.2) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jun 03, 2019 at 01:30:51PM +0530, Abhishek Sahu wrote: > On 6/1/2019 2:09 AM, Bjorn Helgaas wrote: > > > If there *is* spec language that allows dependencies like this, please > > include the citation in your commit log. > > The PCIe specification treats each function separately but GPU case is > different. So, it won't be part of PCIe spec. in GPU, the different > kind of devices are internally coupled in HW but still needs to be > managed by different driver. GPUs aren't the only devices which have these implicit dependencies. E.g. Broadcom BCM57765 combines a Gigabit Ethernet chip in function 0 (14e4:16b4) with an SD card reader in function 1 (14e4:16bc) and AFAIK for the latter to work, the former needs to be in D0. I think we're incorrectly not enforcing this dependency in the kernel yet. That chip was built into many MacBooks. Indeed the inability to specify such inter-function power dependencies in config space seems to be a gaping hole in the PCI spec. Maybe we should always assume that function 0 needs to be in D0 for any other function to work? Not sure if that would be safe. Thanks, Lukas