linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Boris Brezillon <boris.brezillon@bootlin.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Arnd Bergmann <arnd@arndb.de>, Wolfram Sang <wsa@the-dreams.de>,
	Vitor Soares <Vitor.Soares@synopsys.com>,
	Przemyslaw Gaj <pgaj@cadence.com>,
	Rafal Ciepiela <rafalc@cadence.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] Addition of the I3C subsystem in 4.20 (5.0)?
Date: Thu, 1 Nov 2018 06:35:23 +0100	[thread overview]
Message-ID: <20181101063523.26bdbe28@bbrezillon> (raw)

Hello Greg, Linus,

Greg, I didn't get your feedback on v10 of the i3c patchset [1] where I
was asking if you'd agree to have this framework merged in 4.20 (I know
you were busy with the 4.19 release and after that the Kernel Summit, so
that's not a surprise), so I'm sending this PR. It's really not an attempt
to bypass you, more like a ping that, if positively acknowledged, might
lead to inclusion of the I3C framework in 4.20 (5.0?) :-).

Please let me know if you're opposed to the idea.

Regards,

Boris

[1]https://lkml.org/lkml/2018/10/26/552 

The following changes since commit 5b394b2ddf0347bef56e50c69a58773c94343ff3:

  Linux 4.19-rc1 (2018-08-26 14:11:59 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/i3c/linux.git tags/i3c/for-4.20

for you to fetch changes up to 71e60757e1eab6f7b821585948317961ccdc61d1:

  dt-bindings: i3c: Document Cadence I3C master bindings (2018-11-01 06:12:05 +0100)

----------------------------------------------------------------
Add the I3C framework + an I3C controller driver for Cadence IP

----------------------------------------------------------------
Boris Brezillon (7):
      i3c: Add core I3C infrastructure
      docs: driver-api: Add I3C documentation
      i3c: Add sysfs ABI spec
      dt-bindings: i3c: Document core bindings
      MAINTAINERS: Add myself as the I3C subsystem maintainer
      i3c: master: Add driver for Cadence IP
      dt-bindings: i3c: Document Cadence I3C master bindings

 Documentation/ABI/testing/sysfs-bus-i3c                   |  146 ++
 Documentation/devicetree/bindings/i3c/cdns,i3c-master.txt |   44 +
 Documentation/devicetree/bindings/i3c/i3c.txt             |  139 ++
 Documentation/driver-api/i3c/device-driver-api.rst        |    9 +
 Documentation/driver-api/i3c/index.rst                    |   11 +
 Documentation/driver-api/i3c/master-driver-api.rst        |   10 +
 Documentation/driver-api/i3c/protocol.rst                 |  203 +++
 Documentation/driver-api/index.rst                        |    1 +
 MAINTAINERS                                               |   12 +
 drivers/Kconfig                                           |    2 +
 drivers/Makefile                                          |    2 +-
 drivers/i3c/Kconfig                                       |   24 +
 drivers/i3c/Makefile                                      |    4 +
 drivers/i3c/device.c                                      |  233 ++++
 drivers/i3c/internals.h                                   |   26 +
 drivers/i3c/master.c                                      | 2661 +++++++++++++++++++++++++++++++++++++
 drivers/i3c/master/Kconfig                                |    6 +
 drivers/i3c/master/Makefile                               |    1 +
 drivers/i3c/master/i3c-master-cdns.c                      | 1671 +++++++++++++++++++++++
 include/linux/i3c/ccc.h                                   |  385 ++++++
 include/linux/i3c/device.h                                |  331 +++++
 include/linux/i3c/master.h                                |  648 +++++++++
 include/linux/mod_devicetable.h                           |   17 +
 23 files changed, 6585 insertions(+), 1 deletion(-)
 create mode 100644 Documentation/ABI/testing/sysfs-bus-i3c
 create mode 100644 Documentation/devicetree/bindings/i3c/cdns,i3c-master.txt
 create mode 100644 Documentation/devicetree/bindings/i3c/i3c.txt
 create mode 100644 Documentation/driver-api/i3c/device-driver-api.rst
 create mode 100644 Documentation/driver-api/i3c/index.rst
 create mode 100644 Documentation/driver-api/i3c/master-driver-api.rst
 create mode 100644 Documentation/driver-api/i3c/protocol.rst
 create mode 100644 drivers/i3c/Kconfig
 create mode 100644 drivers/i3c/Makefile
 create mode 100644 drivers/i3c/device.c
 create mode 100644 drivers/i3c/internals.h
 create mode 100644 drivers/i3c/master.c
 create mode 100644 drivers/i3c/master/Kconfig
 create mode 100644 drivers/i3c/master/Makefile
 create mode 100644 drivers/i3c/master/i3c-master-cdns.c
 create mode 100644 include/linux/i3c/ccc.h
 create mode 100644 include/linux/i3c/device.h
 create mode 100644 include/linux/i3c/master.h

             reply	other threads:[~2018-11-01  5:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-01  5:35 Boris Brezillon [this message]
2018-11-01 11:33 ` [GIT PULL] Addition of the I3C subsystem in 4.20 (5.0)? Greg Kroah-Hartman
2018-11-01 12:29   ` Boris Brezillon
2018-11-01 16:27 ` Linus Torvalds
2018-11-02 17:45   ` Boris Brezillon

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=20181101063523.26bdbe28@bbrezillon \
    --to=boris.brezillon@bootlin.com \
    --cc=Vitor.Soares@synopsys.com \
    --cc=arnd@arndb.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pgaj@cadence.com \
    --cc=rafalc@cadence.com \
    --cc=torvalds@linux-foundation.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).