linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Octavian Purdila <octavian.purdila@intel.com>
To: wsa@the-dreams.de
Cc: johan@kernel.org, linux-i2c@vger.kernel.org,
	linux-api@vger.kernel.org, linux-kernel@vger.kernel.org,
	Octavian Purdila <octavian.purdila@intel.com>
Subject: [RFC PATCH 0/3] i2c: show and change bus frequency via sysfs
Date: Thu,  9 Oct 2014 23:07:12 +0300	[thread overview]
Message-ID: <1412885235-14026-1-git-send-email-octavian.purdila@intel.com> (raw)

The first two patches are just general cleanup the actual
implementation is in patch 3. If the general direction looks
acceptable, I will send a follow-up series that adds sysfs bus
frequency support to the existing drivers.

Octavian Purdila (3):
  i2c: document the existing i2c sysfs ABI
  i2c: document struct i2c_adapter
  i2c: show and change bus frequency via sysfs

 Documentation/ABI/testing/sysfs-bus-i2c | 69 +++++++++++++++++++++++++++++
 drivers/i2c/i2c-core.c                  | 77 +++++++++++++++++++++++++++++++++
 include/linux/i2c.h                     | 26 +++++++++--
 3 files changed, 169 insertions(+), 3 deletions(-)
 create mode 100644 Documentation/ABI/testing/sysfs-bus-i2c

-- 
1.9.1


             reply	other threads:[~2014-10-09 20:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-09 20:07 Octavian Purdila [this message]
2014-10-09 20:07 ` [RFC PATCH 1/3] i2c: document the existing i2c sysfs ABI Octavian Purdila
2014-10-09 20:07 ` [RFC PATCH 2/3] i2c: document struct i2c_adapter Octavian Purdila
2014-10-09 20:07 ` [RFC PATCH 3/3] i2c: show and change bus frequency via sysfs Octavian Purdila
     [not found]   ` <CAJjB1qKQ0ND2CeF=Npahn0r19WjdTwc7D3Th7PLnn0FJxHa_KQ@mail.gmail.com>
2014-10-12  9:32     ` Octavian Purdila
2014-10-12 17:06       ` Guenter Roeck
2014-10-13 10:32         ` Octavian Purdila
2014-10-14  1:53       ` Mark Roszko
2014-10-14  9:24         ` Octavian Purdila

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=1412885235-14026-1-git-send-email-octavian.purdila@intel.com \
    --to=octavian.purdila@intel.com \
    --cc=johan@kernel.org \
    --cc=linux-api@vger.kernel.org \
    --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).