linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Lechner <david@lechnology.com>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: David Lechner <david@lechnology.com>,
	linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] LEGO MINDSTORMS I2C support
Date: Mon,  5 Sep 2016 15:40:11 -0500	[thread overview]
Message-ID: <1473108014-30787-1-git-send-email-david@lechnology.com> (raw)

I'm working on getting LEGO MINDSTORMS[1] support in the Linux kernel.

They have a system of modular sensors that are hot-plugable, some of which use
I2C communications. Unfortunately, these don't necessary follow standard I2C
conventions, but they do have a well-defined register layout, so they are
easy to detect.

This set of patches addresses the hot-plugability of the sensors.

[1]: http://mindstorms.lego.com


David Lechner (3):
  i2c: Add class for LEGO MINDSTORMS sensors
  i2c: Add special case for detecting LEGO devices
  i2c: expose adapter probe and remove probed functions

 drivers/i2c/i2c-core.c | 62 ++++++++++++++++++++++++++++++++++++++------------
 include/linux/i2c.h    |  4 ++++
 2 files changed, 52 insertions(+), 14 deletions(-)

-- 
2.7.4

             reply	other threads:[~2016-09-05 20:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-05 20:40 David Lechner [this message]
2016-09-05 20:40 ` [PATCH 1/3] i2c: Add class for LEGO MINDSTORMS sensors David Lechner
2016-09-06 19:01   ` Uwe Kleine-König
2016-09-05 20:40 ` [PATCH 2/3] i2c: Add special case for detecting LEGO devices David Lechner
2016-09-05 20:40 ` [PATCH 3/3] i2c: expose adapter probe and remove probed functions David Lechner
2016-09-16 21:03   ` Wolfram Sang
2016-09-16 21:09     ` David Lechner
2016-09-15 20:00 ` [PATCH 0/3] LEGO MINDSTORMS I2C support Wolfram Sang
2016-09-16 20:05   ` David Lechner

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=1473108014-30787-1-git-send-email-david@lechnology.com \
    --to=david@lechnology.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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).