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=-2.3 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_2 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 32D51C34026 for ; Mon, 17 Feb 2020 16:45:45 +0000 (UTC) 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 mail.kernel.org (Postfix) with ESMTPS id EC199222D9 for ; Mon, 17 Feb 2020 16:45:44 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="TOJYvFJH" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org EC199222D9 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=collabora.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-i3c-bounces+linux-i3c=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender: Content-Transfer-Encoding:Content-Type:Cc:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:MIME-Version:References:In-Reply-To: Message-ID:Subject:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=P2IqNisrOY9lWoMqO2AgwFwRYWJL8m+p0Mc2DKEY56w=; b=TOJYvFJHxfW7s8 jm3hMeUOTMBZjAbLR5GABZJyRz1/XkGaFZO5n7aUrJLUPjTrBf4DRBc6qHDtfsSACUdJOuAMdbemX NBcCUVjXzxIFJTAkjExTVEDRtcHWK7Ksptw4SjhpNiD5jYS+PLPLFJn8zxdrilaP3z/J8Ui2MnEmw Tb1MoT03pCZ+dOt/YDAlTy8Q9yHKmtGsIO8/JuGn5N7uo/DPyuSyzssyVJGWM06cOxazMZ5HDidn5 S+b7g31fs5Kt7gzcW4lnjOpQiUU7A8qP6YQC2U8aKR+mRUXFngemFpy8Ti5qaF2fFjc2RaNCTpBym XlsXD2SUJq5vcCrZCN1A==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1j3jWh-0005FL-Un; Mon, 17 Feb 2020 16:45:43 +0000 Received: from bhuna.collabora.co.uk ([2a00:1098:0:82:1000:25:2eeb:e3e3]) by bombadil.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1j3hkQ-00034M-U7 for linux-i3c@lists.infradead.org; Mon, 17 Feb 2020 14:51:48 +0000 Received: from localhost (unknown [IPv6:2a01:e0a:2c:6930:5cf4:84a1:2763:fe0d]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: bbrezillon) by bhuna.collabora.co.uk (Postfix) with ESMTPSA id 5B6EF293C87; Mon, 17 Feb 2020 14:51:45 +0000 (GMT) Date: Mon, 17 Feb 2020 15:51:41 +0100 From: Boris Brezillon To: Vitor Soares Subject: Re: [RFC v2 0/4] Introduce i3c device userspace interface Message-ID: <20200217155141.08e87b3f@collabora.com> In-Reply-To: References: Organization: Collabora X-Mailer: Claws Mail 3.17.4 (GTK+ 2.24.32; x86_64-redhat-linux-gnu) MIME-Version: 1.0 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20200217_065147_102345_2114F822 X-CRM114-Status: GOOD ( 12.32 ) X-Mailman-Approved-At: Mon, 17 Feb 2020 08:45:42 -0800 X-BeenThere: linux-i3c@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Linux I3C List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Jose.Abreu@synopsys.com, Joao.Pinto@synopsys.com, arnd@arndb.de, wsa@the-dreams.de, gregkh@linuxfoundation.org, bbrezillon@kernel.org, linux-kernel@vger.kernel.org, broonie@kernel.org, linux-i3c@lists.infradead.org Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-i3c" Errors-To: linux-i3c-bounces+linux-i3c=archiver.kernel.org@lists.infradead.org Hello Vitor, Sorry for taking so long to reply, and thanks for working on that topic. On Wed, 29 Jan 2020 13:17:31 +0100 Vitor Soares wrote: > For today there is no way to use i3c devices from user space and > the introduction of such API will help developers during the i3c device > or i3c host controllers development. > > The i3cdev module is highly based on i2c-dev and yet I tried to address > the concerns raised in [1]. > > NOTES: > - The i3cdev dynamically request an unused major number. > > - The i3c devices are dynamically exposed/removed from dev/ folder based > on if they have a device driver bound to it. May I ask why you need to automatically bind devices to the i3cdev driver when they don't have a driver matching the device id loaded/compiled-in? If we get the i3c subsystem to generate proper uevents we should be able to load the i3cdev module and bind the device to this driver using a udev rule. Regards, Boris _______________________________________________ linux-i3c mailing list linux-i3c@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-i3c