From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id B3D34A0524; Tue, 13 Apr 2021 10:49:57 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 7470B160CA8; Tue, 13 Apr 2021 10:49:57 +0200 (CEST) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by mails.dpdk.org (Postfix) with ESMTP id 83776160C9F for ; Tue, 13 Apr 2021 10:49:55 +0200 (CEST) Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id F1B995C00FF; Tue, 13 Apr 2021 04:49:54 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Tue, 13 Apr 2021 04:49:55 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=fm3; bh= SN/67yUGeV7JzEok0SMT63KqXnfCBjrAMd+fYJHfqSs=; b=htfHAhVNqxxQnNMp QbjRrMUrsl8wS88UGIVq8JeCqrnt5pZvyTRBdtngAd9LItB7SY9HdGNUEBOagT5q cTFvrY2syP+izAOiuIwVU2UxODCRon6VEq9yP5opHWKy2yc1p/gwDVzT6nNoGrI5 V9zNP4tWeJB2Wxcg8nLUWWf3SmRgRf7n2D+r6KPGLJhQ+p942otFYmeb9EhPkpzJ Ze4jgFFGHvyr6wBxIyjAxRacfyqlYYe5dsSeM6JFKOjEuGD5MHSw6ta9jutPNPWr Gh4Zq9tMDTZORcQlQxrAPtOeVWbG9x0NDvgyDooOGgo/KCepnMHhGc3noiIzpY2U XUdDeQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=SN/67yUGeV7JzEok0SMT63KqXnfCBjrAMd+fYJHfq Ss=; b=uI+EroC8ookDPm4oSTRVL3L8D/R8Uqe2Z+bbBx+5D5nlbBM76VllWnMJk rgCrLOrc7ecnm0b/lNWbVy1ktvDCZQmuM+NIeBXyekqiw6I22394KjR+nFrfs4ga oqGcpWOqUMSXEw5/zeKtOT37EsipOBEuD7CsxUv5CTCIsGlivH1cBqAg8QQOvilt 7NU+MfUI5t2jPSKPMhoDwSw6GJIagnCuK4u0sYyPWEz09um9GcHJaOULMs1qW/no ePFtpIKKnrBx59XosLOhmvPbgq3EosP9RUDYc2Yxp5sqrSj7Hsr/KhZw207kKkj4 vUWX8ttTbWbveuGFMNuIuiWj9Aelg== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrudekledgtdelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecugg ftrfgrthhtvghrnhepjeduteevueejteehieeggfeiueeikefffefhjeetueeihefhhfdv udfhheehfeehnecuffhomhgrihhnpehkvghrnhgvlhdrohhrghenucfkphepjeejrddufe egrddvtdefrddukeegnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghi lhhfrhhomhepthhhohhmrghssehmohhnjhgrlhhonhdrnhgvth X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id E45851080054; Tue, 13 Apr 2021 04:49:52 -0400 (EDT) From: Thomas Monjalon To: dev@dpdk.org Cc: Xueming Li , Asaf Penso , Parav Pandit , Neil Horman , ferruh.yigit@intel.com, andrew.rybchenko@oktetlabs.ru, jerinj@marvell.com, ajit.khaparde@broadcom.com, haiyue.wang@intel.com Date: Tue, 13 Apr 2021 10:49:51 +0200 Message-ID: <1799307.127gSvGnlP@thomas> In-Reply-To: <20210413032329.25551-1-xuemingl@nvidia.com> References: <20210311130113.31382-1-xuemingl@nvidia.com> <20210413032329.25551-1-xuemingl@nvidia.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v1] bus/auxiliary: introduce auxiliary bus X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" I would like to Cc those who are interested in the auxiliary bus, but it's difficult to know who will implement it. Can we expect some reviews? 13/04/2021 05:23, Xueming Li: > Auxiliary [1] provides a way to split function into child-devices > representing sub-domains of functionality. Each auxiliary_device > represents a part of its parent functionality. > > Auxiliary device is identified by unique device name, sysfs path: > /sys/bus/auxiliary/devices/ > > [1] kernel auxiliary bus document: > https://www.kernel.org/doc/html/latest/driver-api/auxiliary_bus.html > > Signed-off-by: Xueming Li