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 Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 69F51EE57C0 for ; Wed, 11 Sep 2024 15:21:49 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:List-Subscribe:List-Help :List-Post:List-Archive:List-Unsubscribe:List-Id:In-Reply-To:Content-Type: MIME-Version:References:Message-ID:Subject:Cc:To:From:Date:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=KDcfaRFvdX2JPDsWjTpQehTNsjsTwM6aYSJ781MewCk=; b=qId0i+Cijg4+j4Ix9vy/7YiUN1 EvE0xXQwCLC1rKfWsP6yQ3q9Es+YqDGo+DSTXO7idNRH3fPCgg34Hn8ZnWQ0lxx5k6sSlXuOJdN4j 1O3HGn5SiaLUgWIpROn7UhhBJK89fU7OCNJay9m07dnVRLj5n72nyg/B134UxK9UFqBd2JCXLeLBg TeFr+h4vQxCPW80vr7Ht5dMaAbXQespgunKrSicSL/helJ/nhmbNKe0LVcwS/EcT6x3L+87eNuFXJ RBryWgxZYrP+YTnqdPC1cxNWmqwBDrAm1Ym433UkvSW0eeUob1gIvHUyaIxVa55LHj/08lEDcRLLa fGF3TChw==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.97.1 #2 (Red Hat Linux)) id 1soPA2-0000000A7KA-2LZD; Wed, 11 Sep 2024 15:21:38 +0000 Received: from nyc.source.kernel.org ([147.75.193.91]) by bombadil.infradead.org with esmtps (Exim 4.97.1 #2 (Red Hat Linux)) id 1soOmt-0000000A2cP-3ovA for linux-arm-kernel@lists.infradead.org; Wed, 11 Sep 2024 14:57:45 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by nyc.source.kernel.org (Postfix) with ESMTP id 5C5C2A44F29; Wed, 11 Sep 2024 14:57:35 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 10399C4CEC5; Wed, 11 Sep 2024 14:57:42 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1726066662; bh=IqUX2V7EiXOEzNuwkkw8pyGCRs0LMUPt/GHdSfxXN30=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=diiAG7ROWhoSuhEFjMWBZU1zby3fBsWNni50e+cMgGhI/iys1CC+6LAYjIVJ7rxgy AMmz3+IACpEeO+x7SNpG99GwgNrU4xjEg613BgqmpyzEUxuvnA0Nem+/V+aWY7GQXR aBk91V0VRE2U9+3eLHVU1kxHqIkU1Ple/bf09c60= Date: Wed, 11 Sep 2024 16:57:39 +0200 From: Greg Kroah-Hartman To: Ayush Singh Cc: fabien.parent@linaro.org, d-gole@ti.com, lorforlinux@beagleboard.org, jkridner@beagleboard.org, robertcnelson@beagleboard.org, Andrew Davis , Miguel Ojeda , Alex Gaynor , Boqun Feng , Gary Guo , =?iso-8859-1?Q?Bj=F6rn?= Roy Baron , Benno Lossin , Andreas Hindborg , Alice Ryhl , Trevor Gross , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Derek Kiernan , Dragan Cvetic , Arnd Bergmann , Nishanth Menon , Vignesh Raghavendra , Tero Kristo , linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH 3/8] mikrobus: Add mikrobus driver Message-ID: <2024091144-glitzy-kindly-fa74@gregkh> References: <20240911-mikrobus-dt-v1-0-3ded4dc879e7@beagleboard.org> <20240911-mikrobus-dt-v1-3-3ded4dc879e7@beagleboard.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20240911-mikrobus-dt-v1-3-3ded4dc879e7@beagleboard.org> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20240911_075744_108633_D4A0764D X-CRM114-Status: GOOD ( 22.13 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Wed, Sep 11, 2024 at 07:57:20PM +0530, Ayush Singh wrote: > A simple platform driver for now that does nothing. This is required > because without a platform driver, the mikrobus_gpio0 nexus node cannot > be used. > > In future, this driver will also allow for dynamic board detection using > 1-wire eeprom in new mikrobus boards. > > Signed-off-by: Ayush Singh > --- > MAINTAINERS | 1 + > drivers/misc/Kconfig | 17 +++++++++++++++++ > drivers/misc/Makefile | 1 + > drivers/misc/mikrobus.rs | 32 ++++++++++++++++++++++++++++++++ > 4 files changed, 51 insertions(+) > > diff --git a/MAINTAINERS b/MAINTAINERS > index 0cc27446b18a..d0c18bd7b558 100644 > --- a/MAINTAINERS > +++ b/MAINTAINERS > @@ -15433,6 +15433,7 @@ MIKROBUS CONNECTOR > M: Ayush Singh > S: Maintained > F: Documentation/devicetree/bindings/connector/mikrobus-connector.yaml > +F: drivers/misc/mikrobus.rs > > MIKROTIK CRS3XX 98DX3236 BOARD SUPPORT > M: Luka Kovacic > diff --git a/drivers/misc/Kconfig b/drivers/misc/Kconfig > index 3fe7e2a9bd29..30defb522e98 100644 > --- a/drivers/misc/Kconfig > +++ b/drivers/misc/Kconfig > @@ -610,6 +610,23 @@ config MARVELL_CN10K_DPI > To compile this driver as a module, choose M here: the module > will be called mrvl_cn10k_dpi. > > +menuconfig MIKROBUS > + tristate "Module for instantiating devices on mikroBUS ports" > + help > + This option enables the mikroBUS driver. mikroBUS is an add-on > + board socket standard that offers maximum expandability with > + the smallest number of pins. The mikroBUS driver instantiates > + devices on a mikroBUS port described by identifying data present > + in an add-on board resident EEPROM, more details on the mikroBUS > + driver support and discussion can be found in this eLinux wiki : > + elinux.org/Mikrobus So you want to be a bus? Or just a single driver? I'm confused, what exactly is this supposed to do? If a bus, great, let's tie into the proper driver core bus code, don't "open code" all of that, as that's just going to make things messier and harder to work overall in the end. If a single driver, why is it called "bus"? :) thanks, greg k-h