Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp8347202imu; Thu, 15 Nov 2018 10:05:25 -0800 (PST) X-Google-Smtp-Source: AJdET5crTfXA6NgR/k38N8s3bpQoD9kNDw/WnIWL/tUpyGX2idipRN1SpeoxAX7RiOqbvy2/xbt4 X-Received: by 2002:a63:f30d:: with SMTP id l13mr6804248pgh.399.1542305125628; Thu, 15 Nov 2018 10:05:25 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1542305125; cv=none; d=google.com; s=arc-20160816; b=OYedmTmSlbLAbpPO89ekSyb5CU7KjS9aKqSiss4WXdbBRw7rE5J/3BLQqE5TReESlj yRjjIyodDrTYh92GGLJIbAthUZVynZYKmd1bN5lOSl1LP9cMlyVom99xYIU/5mdsAssS sej5lK+g8YkzDpc5b8/KcwvxnVwG19Lwb/BhRAh+MiiawUh01bOVFwwNedBUCqdz0VRd 6lMno7QEIHx/hc3hsHdmBP4ssU6zorUFhfI6IqOcgqm7YTFGML6PhHWv1rqraXHXobtC 01AkBSSIjsL2F/OUQbqXsSMMXe/b+ZUOfLWKqMWjq2d7tdEVnL2AbNjw6DN1AvVc0LRa qEcQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-language :content-transfer-encoding:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature; bh=ZYptxXtdNjIDa5wRn/DwSx1DMT9sN1CdX6XApa6biPE=; b=wnuD2yOWXLMSiZAEhwOIackKaeynDVV2ywbJvbkfjehpp4h/8Kc8sX0K+p7HcaUN5Y yZJ5fVlpYUsXYc2CHAHuvTIgXGnnrMEMHqVlXgRPxCicAJ9puHD3OQ4nmtzLiWTn3hew K54d3ofhEEpqYeiS5ccJhCOe6dSDtJ2wfwaMcFv11erUbeuUTCH557iqG03TNAJ11rrR CfA1qe64Wf/6hfOb48heZR9IopKhZTg9Qy3KrmTm4pTVSTcp5kbkFnrE+y022kHzpBkS qGvojQKmmc8myTDJ2gfj89SzL3GduPndgWnmIACqJOhyIY880mVnxjbu1MiUSXkPDQE3 dX2Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@synopsys.com header.s=mail header.b=bg0eIUcj; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=synopsys.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id e1-v6si29970125plk.4.2018.11.15.10.05.01; Thu, 15 Nov 2018 10:05:25 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@synopsys.com header.s=mail header.b=bg0eIUcj; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=synopsys.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2388790AbeKPEM7 (ORCPT + 99 others); Thu, 15 Nov 2018 23:12:59 -0500 Received: from smtprelay.synopsys.com ([198.182.47.9]:44120 "EHLO smtprelay.synopsys.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2387839AbeKPEM6 (ORCPT ); Thu, 15 Nov 2018 23:12:58 -0500 Received: from mailhost.synopsys.com (mailhost1.synopsys.com [10.12.238.239]) by smtprelay.synopsys.com (Postfix) with ESMTP id 8800C24E065F; Thu, 15 Nov 2018 10:04:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=synopsys.com; s=mail; t=1542305047; bh=MJFRcvH70hjfvSOKoKb3IQsQfE5KxYHe8kEvub3IcaI=; h=Subject:To:CC:References:From:Date:In-Reply-To:From; b=bg0eIUcjsvMRluzi3h5JV6AD4b+QBjDrsuuDP1AWx9V6zEsH/PkWlJT2osvoM5HbZ j2uKjsMiz6YrgGGSubYCSOUPzJoU2fI1IrAVGyS5dDyhyaBbBDFscXR7cQIA1d8j4s /psy0e4ArtIJTi/mlG7R4aRcPb+2OzBfbsbkH4lvwkX+cJ45b8G+e1ksLIslotlfdg qc95zoe3vf16ePcsZpIHfhHL8HFqt5+W+XiTrm/rdaYfNZXKyibSIJCCoJ4o1eAKFe BqmjMKEGxk+lGKenN88lm0inqYayPuuauKL0r9pUnfpRiHbWT5pIaESgn/8aP7fXJT WDtV/6aGR80sg== Received: from US01WXQAHTC1.internal.synopsys.com (us01wxqahtc1.internal.synopsys.com [10.12.238.230]) by mailhost.synopsys.com (Postfix) with ESMTP id E4EF76CC4; Thu, 15 Nov 2018 10:04:03 -0800 (PST) Received: from DE02WEHTCA.internal.synopsys.com (10.225.19.92) by US01WXQAHTC1.internal.synopsys.com (10.12.238.230) with Microsoft SMTP Server (TLS) id 14.3.408.0; Thu, 15 Nov 2018 10:04:03 -0800 Received: from DE02WEHTCB.internal.synopsys.com (10.225.19.94) by DE02WEHTCA.internal.synopsys.com (10.225.19.92) with Microsoft SMTP Server (TLS) id 14.3.408.0; Thu, 15 Nov 2018 19:04:01 +0100 Received: from [10.0.2.15] (10.107.19.116) by DE02WEHTCB.internal.synopsys.com (10.225.19.80) with Microsoft SMTP Server (TLS) id 14.3.408.0; Thu, 15 Nov 2018 19:04:01 +0100 Subject: Re: [PATCH v10 0/9] Add the I3C subsystem To: Boris Brezillon , Wolfram Sang CC: vitor , , "Jonathan Corbet" , , Greg Kroah-Hartman , Arnd Bergmann , Przemyslaw Sroka , Arkadiusz Golec , Alan Douglas , Bartosz Folta , Damian Kos , Alicja Jurasik-Urbaniak , "Cyprian Wronka" , Suresh Punnoose , "Rafal Ciepiela" , Thomas Petazzoni , Nishanth Menon , Rob Herring , Pawel Moll , Mark Rutland , Ian Campbell , "Kumar Gala" , , , Geert Uytterhoeven , Linus Walleij , Xiang Lin , , Sekhar Nori , Przemyslaw Gaj , Peter Rosin , Mike Shettel , Stephen Boyd , Mark Brown References: <20181026144333.12276-1-boris.brezillon@bootlin.com> <76b1d15d-232c-d8ba-5eba-8394e71be725@synopsys.com> <20181115135731.25f60990@bbrezillon> <20181115150137.GB4169@kunai> <20181115162826.42b54776@bbrezillon> From: vitor Message-ID: <1d64f21a-ad24-94e0-2c17-25729ef59a31@synopsys.com> Date: Thu, 15 Nov 2018 18:03:47 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 In-Reply-To: <20181115162826.42b54776@bbrezillon> Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-Originating-IP: [10.107.19.116] Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Boris, On 15/11/18 15:28, Boris Brezillon wrote: > On Thu, 15 Nov 2018 16:01:37 +0100 > Wolfram Sang wrote: > >> Hi Boris, >> >>> What we could do though, is expose I3C devices that do not have a >>> driver in kernel space, like spidev does. >> ... >> >>> Mark, Wolfram, Arnd, Greg, any opinion? >> Is there a benefit for having drivers in userspace? My gut feeling is to >> encourage people to write kernel drivers. If this is, for some reason, >> not possible for some driver, then we have a use case at hand to test >> the then-to-be-developed userspace interface against. Until then, I >> personally wouldn't waste effort on designing it without a user in >> sight. > I kind of agree with that. Vitor, do you have a use case in mind for > such userspace drivers? I don't think it's worth designing an API for > something we don't need (yet). My use case is a tool for tests, lets say like the i2c tools. There is other subsystems, some of them mentioned on this thread, that have and ioctl system call or other method to change parameters or send data. I rise this topic because I really think it worth to define now how this should be design (and for me how to do the things right) to avoid future issues. Best regards, Vitor Soares