From mboxrd@z Thu Jan 1 00:00:00 1970 From: vitor Subject: Re: [PATCH v10 0/9] Add the I3C subsystem Date: Thu, 15 Nov 2018 12:14:37 +0000 Message-ID: <76b1d15d-232c-d8ba-5eba-8394e71be725@synopsys.com> References: <20181026144333.12276-1-boris.brezillon@bootlin.com> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20181026144333.12276-1-boris.brezillon@bootlin.com> Content-Language: en-US Sender: linux-kernel-owner@vger.kernel.org To: Boris Brezillon , Wolfram Sang , linux-i2c@vger.kernel.org, Jonathan Corbet , linux-doc@vger.kernel.org, Greg Kroah-Hartman , Arnd Bergmann Cc: 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 , devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, Vitor Soares , Geert Uytterhoeven List-Id: devicetree@vger.kernel.org Hi Boris, Given the current state of the subsystem I think it might worth start to think how to expose the devices under /dev. My initial thoughts are to do the same think as for i2c, expose the buses or the i3c_devices and use ioctl for private transfers. Some direct CCC commands can be sent through the /sys as you plan for SETNEWDA . What do you think about this? Best regards, Vitor Soares