From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.2 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 6C0FAC4360C for ; Thu, 26 Sep 2019 18:06:00 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 3A1BD222C9 for ; Thu, 26 Sep 2019 18:06:00 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1569521160; bh=WS6JHm5RIAeOO5mY0UJvuqR3lEGtZztvNEcr2ZMIGWA=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=GVZEVSooBrqEXWumNwZrNoC0Mj/JjXxufBgxOlrMmTpmzZ0TGc+r+mxz/m6NW7sfJ f2N8wPoWcQzKr53VD5P01HRhLr+FtLAu7x4yWFDw3LnE3uzr7vufZ/y9HyE9f/CP54 7C/Gsid9zBwvzQ/u3Zn7O677KF2iP0y86C1ewqJg= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727940AbfIZSF7 (ORCPT ); Thu, 26 Sep 2019 14:05:59 -0400 Received: from mail.kernel.org ([198.145.29.99]:57620 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727934AbfIZSF7 (ORCPT ); Thu, 26 Sep 2019 14:05:59 -0400 Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 7131A21A4A; Thu, 26 Sep 2019 18:05:58 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1569521158; bh=WS6JHm5RIAeOO5mY0UJvuqR3lEGtZztvNEcr2ZMIGWA=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=UYM4RVuO3n/Fi5I4/H5Fd++R/MA6CwCbTtiicHd3yqLWLoxgGdlI+FgiW1HLzYh48 M/S2vYk6DLpntPpZfCp0zQX3DPxGvXQ8t2vKsOuPKKWziG3O1fGD9IsDWKyFl7fXJW u1gnMjBySCSBBCiInQoZoOPWnjjENzcLIj1t1ZSc= Date: Thu, 26 Sep 2019 20:05:56 +0200 From: Greg KH To: Jeff Kirsher Cc: dledford@redhat.com, jgg@mellanox.com, Tony Nguyen , netdev@vger.kernel.org, linux-rdma@vger.kernel.org, Dave Ertman Subject: Re: [RFC 01/20] ice: Initialize and register multi-function device to provide RDMA Message-ID: <20190926180556.GB1733924@kroah.com> References: <20190926164519.10471-1-jeffrey.t.kirsher@intel.com> <20190926164519.10471-2-jeffrey.t.kirsher@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190926164519.10471-2-jeffrey.t.kirsher@intel.com> User-Agent: Mutt/1.12.2 (2019-09-21) Sender: linux-rdma-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-rdma@vger.kernel.org On Thu, Sep 26, 2019 at 09:45:00AM -0700, Jeff Kirsher wrote: > From: Tony Nguyen > > The RDMA block does not advertise on the PCI bus or any other bus. Huh? How do you "know" where it is then? Isn't is usually assigned to a PCI device? > Thus the ice driver needs to provide access to the RDMA hardware block > via a virtual bus; utilize a multi-function device to provide this access. > > This patch initializes the driver to support RDMA as well as creates > and registers a multi-function device for the RDMA driver to register to. > At this point the driver is fully initialized to register a platform > driver, however, can not yet register as the ops have not been > implemented. > > We refer to the interaction of this platform device as Inter-Driver > Communication (IDC); where the platform device is referred to as the peer > device and the platform driver is referred to as the peer driver. Again, no platform devices, unless it REALLY IS a platform device (i.e. you are using device tree or platform data to find it.) Is that what you are doing here? confused, greg k-h