Received: by 2002:ac0:a5a6:0:0:0:0:0 with SMTP id m35-v6csp250369imm; Wed, 29 Aug 2018 20:12:34 -0700 (PDT) X-Google-Smtp-Source: ANB0VdZ6FcTVsqiWG0Vv7ZD8Xtpzlk8GAn2ST/UkLmo+eTz51v4RNB95IEXBvgIx/qnMEGY8L/QD X-Received: by 2002:a65:6398:: with SMTP id h24-v6mr8076828pgv.245.1535598754305; Wed, 29 Aug 2018 20:12:34 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1535598754; cv=none; d=google.com; s=arc-20160816; b=frfOaKRJVK/Gkrey3Ypj8X+5E8AeQ5fL6uks3lF2lOyhkTtBvS5t7Fuq18XS7YAVcW oXvwp3kQ+1FEl2QBVG9YqcNnPXitsiUsjAmmNjSFAgXyfx78yWIWbvh9ToDRFVQH/6ud JuOKbE82AQs3tJmOBJ3OeVNLbx1+23xwFpgXmm9HxrpRqxn6PATqn33MESNb+PjUcu6f BkLPn2D69xOEtlGDpFhzhDdf9i1QQDSNAPFWSk0l6qfBwyNnmNhqM89nIhYnYKI4O6yR YFD1IwXjljC0I/EsGk81wUfs6eLOVG/63J/aUfeaX26dL+/5kbuwXwKt3PH3/3tdEa2l afmw== 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:dkim-signature:arc-authentication-results; bh=TLjna5aAksDlVHfZD4DWmmJFtxT58JUG7x746DUvTiQ=; b=CEscd131CaB4ifAPQEuy+8btfxsTtt2oFO0ZJkIONli2jKVTTMKAmAFall5P0Lwqol o57owCIgSy9O1jDpwqUzWbBqKtnolMEvyPvhADX5pL+UIjw4EEUX2DBNu9yUsrqi+/yH fMC26Mk2c3pRNt5xTFHWF8ufy1EUf6GgSgghVfpQEsKwARyqUp/lY+1mmXJI60Ah1590 MFMOYGffHvbeaS8y/bhIAiWP39nzaoRdjiopRfgwrcma4Ogxf4DEOxm663v4mlVKIzdW OW/YC5epT35OHU7ZuvzBbC2tV/c99boaE/x0xmsZz5M12JdVutQBzR087k/5tp1Upt9S oveg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@lunn.ch header.s=20171124 header.b=CY6Jxtln; 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 v11-v6si5493900pgg.303.2018.08.29.20.12.19; Wed, 29 Aug 2018 20:12:34 -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; dkim=pass header.i=@lunn.ch header.s=20171124 header.b=CY6Jxtln; 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 S1727394AbeH3HLN (ORCPT + 99 others); Thu, 30 Aug 2018 03:11:13 -0400 Received: from vps0.lunn.ch ([185.16.172.187]:47116 "EHLO vps0.lunn.ch" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727233AbeH3HLN (ORCPT ); Thu, 30 Aug 2018 03:11:13 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lunn.ch; s=20171124; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID:Subject:Cc:To:From:Date; bh=TLjna5aAksDlVHfZD4DWmmJFtxT58JUG7x746DUvTiQ=; b=CY6JxtlnmMQ+lYyz2WEXMDZPr61wD1MxgpXhVRmCuNpsUg2K0MuSxizxIAza/8v6F8OTApGO8f2sCciZ5cFk27EbZUheZyEbhnI62OAjWsIa8iuxKy9ydE3gEjh8Q9ZO5mNaxRQUafI/0/TzGi50/Gm57WsZMn4qBaBGVwn7nSc=; Received: from andrew by vps0.lunn.ch with local (Exim 4.84_2) (envelope-from ) id 1fvDMU-0004rG-Px; Thu, 30 Aug 2018 05:11:10 +0200 Date: Thu, 30 Aug 2018 05:11:10 +0200 From: Andrew Lunn To: Moritz Fischer Cc: davem@davemloft.net, keescook@chromium.org, f.fainelli@gmail.com, linux-kernel@vger.kernel.org, netdev@vger.kernel.org, alex.williams@ni.com Subject: Re: [PATCH net-next 2/3] net: nixge: Add support for having nixge as subdevice Message-ID: <20180830031110.GC16896@lunn.ch> References: <20180830004046.9417-1-mdf@kernel.org> <20180830004046.9417-3-mdf@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180830004046.9417-3-mdf@kernel.org> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Aug 29, 2018 at 05:40:45PM -0700, Moritz Fischer wrote: > Add support for instantiating nixge as subdevice using > fixed-link and platform data to configure it. > > Signed-off-by: Moritz Fischer > --- > > Hi, > > not this patch is still in the early stages, > and as the rest of this series goes on top of [1]. > > The actual platform data might still change since > the parent device driver is still under development. Hi Moritz Could you tell us more about the parent device. I'm guessing PCIe. Is it x86 so no device tree? Are there cases where it does not have a PHY connected? What is connected instead? SFP? A switch? Can there be multiple PHYs on the MDIO bus? Answering these questions will help decide how best to structure this. Andrew