From: Boris Brezillon <boris.brezillon@bootlin.com>
To: vitor <vitor.soares@synopsys.com>
Cc: Arnd Bergmann <arnd@arndb.de>, Wolfram Sang <wsa@the-dreams.de>,
Linux I2C <linux-i2c@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
gregkh <gregkh@linuxfoundation.org>,
Przemyslaw Sroka <psroka@cadence.com>,
Arkadiusz Golec <agolec@cadence.com>,
Alan Douglas <adouglas@cadence.com>,
Bartosz Folta <bfolta@cadence.com>, Damian Kos <dkos@cadence.com>,
"Alicja Jurasik-Urbaniak" <alicja@cadence.com>,
Cyprian Wronka <cwronka@cadence.com>,
Suresh Punnoose <sureshp@cadence.com>,
Rafal Ciepiela <rafalc@cadence.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Nishanth Menon <nm@ti.com>, Rob Herring <robh+dt@kernel.org>,
Pawel Moll <pawel.moll@arm.com>,
"Mark Rutland" <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
DTML <devicetree@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Linus Walleij <linus.walleij@linaro.org>,
Xiang Lin <Xiang.Lin@synaptics.com>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
Sekhar Nori <nsekhar@ti.com>, Przemyslaw Gaj <pgaj@cadence.com>,
Peter Rosin <peda@axentia.se>,
Mike Shettel <mshettel@codeaurora.org>,
Stephen Boyd <swboyd@chromium.org>,
Mark Brown <broonie@kernel.org>
Subject: Re: [PATCH v10 0/9] Add the I3C subsystem
Date: Thu, 15 Nov 2018 20:07:39 +0100 [thread overview]
Message-ID: <20181115200739.20b22d52@bbrezillon> (raw)
In-Reply-To: <08a591ae-c75b-80b4-b608-ca92f6d932f9@synopsys.com>
On Thu, 15 Nov 2018 15:25:11 +0000
vitor <vitor.soares@synopsys.com> wrote:
> Hi Arnd,
>
> On 15/11/18 14:25, Arnd Bergmann wrote:
> > I agree about better not exposing the bus as a /dev/i3c* node, and that we
> > probably do need to expose individual devices in some form to allow
> > writing complete user space drivers that can do everything a kernel driver
> > can do.
> >
> > Can you describe what a low-level interface to the device looks like
> > in the kernel? Can this be abstracted as simply pread()/pwrite() plus
> > an interrupt mechanism, or do we need a set of ioctl() operations as
> > well?
>
> Like in i2c is likely to need the ioctl() too.
Yep, I think we'll need an ioctl given the various type of transfers
one case use to interact with a device.
WARNING: multiple messages have this Message-ID (diff)
From: Boris Brezillon <boris.brezillon@bootlin.com>
To: vitor <vitor.soares@synopsys.com>
Cc: Arnd Bergmann <arnd@arndb.de>, Wolfram Sang <wsa@the-dreams.de>,
Linux I2C <linux-i2c@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
gregkh <gregkh@linuxfoundation.org>,
Przemyslaw Sroka <psroka@cadence.com>,
Arkadiusz Golec <agolec@cadence.com>,
Alan Douglas <adouglas@cadence.com>,
Bartosz Folta <bfolta@cadence.com>, Damian Kos <dkos@cadence.com>,
Alicja Jurasik-Urbaniak <alicja@cadence.com>,
Cyprian Wronka <cwronka@cadence.com>,
Suresh Punnoose <sureshp@cadence.com>,
Rafal Ciepiela <rafalc@cadence.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Nishanth Menon <nm@ti.com>, Rob Herring <robh+dt@kernel.org>,
Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH v10 0/9] Add the I3C subsystem
Date: Thu, 15 Nov 2018 20:07:39 +0100 [thread overview]
Message-ID: <20181115200739.20b22d52@bbrezillon> (raw)
In-Reply-To: <08a591ae-c75b-80b4-b608-ca92f6d932f9@synopsys.com>
On Thu, 15 Nov 2018 15:25:11 +0000
vitor <vitor.soares@synopsys.com> wrote:
> Hi Arnd,
>
> On 15/11/18 14:25, Arnd Bergmann wrote:
> > I agree about better not exposing the bus as a /dev/i3c* node, and that we
> > probably do need to expose individual devices in some form to allow
> > writing complete user space drivers that can do everything a kernel driver
> > can do.
> >
> > Can you describe what a low-level interface to the device looks like
> > in the kernel? Can this be abstracted as simply pread()/pwrite() plus
> > an interrupt mechanism, or do we need a set of ioctl() operations as
> > well?
>
> Like in i2c is likely to need the ioctl() too.
Yep, I think we'll need an ioctl given the various type of transfers
one case use to interact with a device.
next prev parent reply other threads:[~2018-11-15 19:07 UTC|newest]
Thread overview: 79+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-26 14:43 [PATCH v10 0/9] Add the I3C subsystem Boris Brezillon
2018-10-26 14:43 ` Boris Brezillon
2018-10-26 14:43 ` [PATCH v10 1/9] i3c: Add core I3C infrastructure Boris Brezillon
2018-10-26 14:43 ` Boris Brezillon
2018-10-26 14:43 ` [PATCH v10 2/9] docs: driver-api: Add I3C documentation Boris Brezillon
2018-10-26 14:43 ` Boris Brezillon
2018-10-26 14:43 ` [PATCH v10 3/9] i3c: Add sysfs ABI spec Boris Brezillon
2018-10-26 14:43 ` Boris Brezillon
2018-10-26 14:43 ` [PATCH v10 4/9] dt-bindings: i3c: Document core bindings Boris Brezillon
2018-10-26 14:43 ` Boris Brezillon
2018-10-30 19:26 ` Rob Herring
2018-10-26 14:43 ` [PATCH v10 5/9] MAINTAINERS: Add myself as the I3C subsystem maintainer Boris Brezillon
2018-10-26 14:43 ` Boris Brezillon
2018-10-26 14:43 ` [PATCH v10 6/9] i3c: master: Add driver for Cadence IP Boris Brezillon
2018-10-26 14:43 ` Boris Brezillon
2018-10-26 14:43 ` [PATCH v10 7/9] dt-bindings: i3c: Document Cadence I3C master bindings Boris Brezillon
2018-10-26 14:43 ` Boris Brezillon
2018-10-26 14:43 ` [PATCH v10 8/9] gpio: Add a driver for Cadence I3C GPIO expander Boris Brezillon
2018-10-26 14:43 ` Boris Brezillon
2018-10-26 14:43 ` [PATCH v10 9/9] dt-bindings: gpio: Add bindings for Cadence I3C gpio expander Boris Brezillon
2018-10-26 14:43 ` Boris Brezillon
2018-10-26 15:22 ` [PATCH v10 0/9] Add the I3C subsystem vitor
2018-10-26 15:22 ` vitor
2018-10-26 16:15 ` Boris Brezillon
2018-10-26 16:15 ` Boris Brezillon
2018-10-26 16:20 ` vitor
2018-10-26 16:20 ` vitor
2018-10-26 16:30 ` Boris Brezillon
2018-10-26 16:30 ` Boris Brezillon
2018-10-26 16:18 ` Boris Brezillon
2018-10-26 16:18 ` Boris Brezillon
2018-11-11 17:39 ` Greg Kroah-Hartman
2018-11-11 17:39 ` Greg Kroah-Hartman
2018-11-11 18:10 ` Boris Brezillon
2018-11-11 18:10 ` Boris Brezillon
2018-11-11 19:10 ` Greg Kroah-Hartman
2018-11-11 19:10 ` Greg Kroah-Hartman
2018-11-11 20:08 ` Boris Brezillon
2018-11-11 20:08 ` Boris Brezillon
2018-11-11 20:57 ` Greg Kroah-Hartman
2018-11-11 20:57 ` Greg Kroah-Hartman
2018-11-11 20:59 ` Greg Kroah-Hartman
2018-11-11 20:59 ` Greg Kroah-Hartman
2018-11-15 12:14 ` vitor
2018-11-15 12:14 ` vitor
2018-11-15 12:57 ` Boris Brezillon
2018-11-15 12:57 ` Boris Brezillon
2018-11-15 14:25 ` Arnd Bergmann
2018-11-15 14:25 ` Arnd Bergmann
2018-11-15 15:25 ` vitor
2018-11-15 15:25 ` vitor
2018-11-15 19:07 ` Boris Brezillon [this message]
2018-11-15 19:07 ` Boris Brezillon
2018-11-15 15:01 ` Wolfram Sang
2018-11-15 15:01 ` Wolfram Sang
2018-11-15 15:11 ` Arnd Bergmann
2018-11-15 15:11 ` Arnd Bergmann
2018-11-15 15:28 ` Boris Brezillon
2018-11-15 15:28 ` Boris Brezillon
2018-11-15 18:03 ` vitor
2018-11-15 18:03 ` vitor
2018-11-15 19:00 ` Boris Brezillon
2018-11-15 19:00 ` Boris Brezillon
2018-11-16 12:31 ` vitor
2018-11-16 12:31 ` vitor
2018-11-16 12:50 ` Przemyslaw Gaj
2018-11-16 12:50 ` Przemyslaw Gaj
2018-11-16 13:16 ` Boris Brezillon
2018-11-16 13:16 ` Boris Brezillon
2018-11-19 12:35 ` vitor
2018-11-19 12:35 ` vitor
2018-11-19 12:43 ` Boris Brezillon
2018-11-19 12:43 ` Boris Brezillon
2018-11-19 12:46 ` vitor
2018-11-19 12:46 ` vitor
2018-11-15 15:18 ` vitor
2018-11-15 15:18 ` vitor
2018-11-15 19:08 ` Mark Brown
2018-11-15 19:08 ` Mark Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181115200739.20b22d52@bbrezillon \
--to=boris.brezillon@bootlin.com \
--cc=Xiang.Lin@synaptics.com \
--cc=adouglas@cadence.com \
--cc=agolec@cadence.com \
--cc=alicja@cadence.com \
--cc=arnd@arndb.de \
--cc=bfolta@cadence.com \
--cc=broonie@kernel.org \
--cc=corbet@lwn.net \
--cc=cwronka@cadence.com \
--cc=devicetree@vger.kernel.org \
--cc=dkos@cadence.com \
--cc=galak@codeaurora.org \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linus.walleij@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mshettel@codeaurora.org \
--cc=nm@ti.com \
--cc=nsekhar@ti.com \
--cc=pawel.moll@arm.com \
--cc=peda@axentia.se \
--cc=pgaj@cadence.com \
--cc=psroka@cadence.com \
--cc=rafalc@cadence.com \
--cc=robh+dt@kernel.org \
--cc=sureshp@cadence.com \
--cc=swboyd@chromium.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=vitor.soares@synopsys.com \
--cc=wsa@the-dreams.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.