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=-6.2 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,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 9A6FDC48BE0 for ; Fri, 11 Jun 2021 11:26:58 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 6A62E613CD for ; Fri, 11 Jun 2021 11:26:58 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231358AbhFKL2y (ORCPT ); Fri, 11 Jun 2021 07:28:54 -0400 Received: from mail.kernel.org ([198.145.29.99]:41814 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230248AbhFKL2x (ORCPT ); Fri, 11 Jun 2021 07:28:53 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 272D0610E9; Fri, 11 Jun 2021 11:26:54 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1623410816; bh=QXbhpoKZRkqCV8d85AMb2D87wCsbusdzmNcunuEV1eo=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=mHNHZtdkpxh+sAIplb3d0tqtmW4gvz992iETR2j7p8QZBoUNBitsS2H7L1nbPOTIH +8CNq1F4ar3EFOsdILg8sQGmuYicMx0LKInecTpzYxnGkdPKMGEALsUWAiled/e5P0 xYB4xE28l65g7gBJcouALiu9EJ/tOlnH95uYMzGOr+e5kquZjTuMhqJ4tJb7lqQqpr 4A+LN/NVEFQSrt2zwQDxp2DiFPxozEdq6ZlAiTYe8RR7JYMF0P3t2bsnnGdRaCa6UE PPNqGgUXxC+KHKLIjc7/KR9uOA3rR5poXVAWQvc9oaijApy/1rBzt6c2vCwG6l7MHa TFsQwECdugKIA== Date: Fri, 11 Jun 2021 16:56:52 +0530 From: Vinod Koul To: Jason Gunthorpe Cc: Pierre-Louis Bossart , alsa-devel@alsa-project.org, Leon Romanovsky , gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org, Ranjani Sridharan , hui.wang@canonical.com, Dave Ertman , sanyog.r.kale@intel.com, Bard Liao , rander.wang@linux.intel.com, bard.liao@intel.com Subject: Re: [PATCH v4] soundwire: intel: move to auxiliary bus Message-ID: References: <20210511052132.28150-1-yung-chuan.liao@linux.intel.com> <21002781-0b78-3b36-952f-683482a925d7@linux.intel.com> <07dbe0a2-0abb-810b-ef39-b83511d3f3e0@linux.intel.com> <20210609151022.GF1002214@nvidia.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210609151022.GF1002214@nvidia.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 09-06-21, 12:10, Jason Gunthorpe wrote: > On Wed, Jun 09, 2021 at 09:44:08AM -0500, Pierre-Louis Bossart wrote: > > > The consensus for the auxiliary_device model was hard to reach, and the > > agreement was to align on a minimal model. If you disagree with the > > directions, you will have to convince Nvidia/Mellanox and Intel networking > > folks who contributed the solution to do something different. > > The purpose of the aux devices was primarily to bind a *software* > interface between two parts of the kernel. Then I dont think this example is valid... This example has a PCI device, which represents a DSP, HDA controller, DMICs, Soundwire links... So at least here it is hardware. > If there is a strong defined HW boundary and no software interface > then the mfd subsytem may be a better choice. More I think that might be better choice for this example, but then MFD is a 'platform device' and Greg already nacked that > For a software layer I expect to see some 'handle' and then a set of > APIs to work within that. It is OK if that 'handle' refers to some HW > resources that the API needs to work, the purpose of this is to > control HW after all. > > You might help Vinod by explaining what the SW API is here. > > Jason -- ~Vinod