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=-3.8 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS 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 28FCFC433DB for ; Fri, 22 Jan 2021 19:54:52 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id EA94723B01 for ; Fri, 22 Jan 2021 19:54:51 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729582AbhAVTws (ORCPT ); Fri, 22 Jan 2021 14:52:48 -0500 Received: from vps0.lunn.ch ([185.16.172.187]:54446 "EHLO vps0.lunn.ch" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728416AbhAVOOC (ORCPT ); Fri, 22 Jan 2021 09:14:02 -0500 Received: from andrew by vps0.lunn.ch with local (Exim 4.94) (envelope-from ) id 1l2xBY-0024hi-Cl; Fri, 22 Jan 2021 15:13:12 +0100 Date: Fri, 22 Jan 2021 15:13:12 +0100 From: Andrew Lunn To: Jiri Pirko Cc: David Ahern , Jakub Kicinski , netdev@vger.kernel.org, davem@davemloft.net, jacob.e.keller@intel.com, roopa@nvidia.com, mlxsw@nvidia.com Subject: Re: [patch net-next RFC 00/10] introduce line card support for modular switch Message-ID: References: <20210113121222.733517-1-jiri@resnulli.us> <20210119115610.GZ3565223@nanopsycho.orion> <20210120083605.GB3565223@nanopsycho.orion> <20210120154158.206b8752@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> <20210121153224.GE3565223@nanopsycho.orion> <971e9eff-0b71-8ff9-d72c-aebe73cab599@gmail.com> <20210122072814.GG3565223@nanopsycho.orion> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210122072814.GG3565223@nanopsycho.orion> Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org > I don't see any way. The userspace is the one who can get the info, from > the i2c driver. The mlxsw driver has no means to get that info itself. Hi Jiri Please can you tell us more about this i2c driver. Do you have any architecture pictures? It is not unknown for one driver to embed another driver inside it. So the i2c driver could be inside the mlxsw. It is also possible to link drivers together, the mlxsw could go find the i2c driver and make use of its services. Andrew