From: Wolfram Sang <wsa@the-dreams.de>
To: linux-i2c@vger.kernel.org
Cc: linux-sh@vger.kernel.org, "Magnus Damm" <magnus.damm@gmail.com>,
"Simon Horman" <horms@verge.net.au>,
"Laurent Pinchart" <laurent.pinchart@ideasonboard.com>,
"Geert Uytterhoeven" <geert@linux-m68k.org>,
"Wolfram Sang" <wsa@the-dreams.de>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Andrey Danin" <danindrey@mail.ru>,
"Marc Dietrich" <marvin24@gmx.de>,
"Debora Grosse" <debora@mds.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH 3/3] i2c: slave: add documentation for i2c-slave-eeprom
Date: Thu, 12 Mar 2015 12:42:03 +0000 [thread overview]
Message-ID: <1426164123-8853-4-git-send-email-wsa@the-dreams.de> (raw)
In-Reply-To: <1426164123-8853-1-git-send-email-wsa@the-dreams.de>
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
---
Documentation/i2c/slave-eeprom-backend | 14 ++++++++++++++
1 file changed, 14 insertions(+)
create mode 100644 Documentation/i2c/slave-eeprom-backend
diff --git a/Documentation/i2c/slave-eeprom-backend b/Documentation/i2c/slave-eeprom-backend
new file mode 100644
index 00000000000000..c8444ef82acfa3
--- /dev/null
+++ b/Documentation/i2c/slave-eeprom-backend
@@ -0,0 +1,14 @@
+Linux I2C slave eeprom backend
+===============
+
+by Wolfram Sang <wsa@sang-engineering.com> in 2014-15
+
+This is a proof-of-concept backend which acts like an EEPROM on the connected
+I2C bus. The memory contents can be modified from userspace via this file
+located in sysfs:
+
+ /sys/bus/i2c/devices/<device-direcory>/slave-eeprom
+
+As of 2015, Linux doesn't support poll on binary sysfs files, so there is no
+notfication when another master changed the content.
+
--
2.1.4
next prev parent reply other threads:[~2015-03-12 12:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-12 12:42 [PATCH 0/3] i2c: slave: API updates Wolfram Sang
2015-03-12 12:42 ` [PATCH 1/3] i2c: slave: rework the slave API Wolfram Sang
[not found] ` <1426164123-8853-2-git-send-email-wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
2015-03-19 20:17 ` Uwe Kleine-König
2015-03-20 7:15 ` Wolfram Sang
2015-03-20 7:24 ` Uwe Kleine-König
2015-03-20 7:31 ` Wolfram Sang
2015-03-20 7:44 ` Uwe Kleine-König
[not found] ` <20150320074447.GE10068-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2015-03-20 8:18 ` Wolfram Sang
2015-03-12 12:42 ` [PATCH 2/3] Documentation: i2c: describe the new slave mode Wolfram Sang
2015-03-12 13:27 ` Geert Uytterhoeven
2015-03-19 20:11 ` Uwe Kleine-König
[not found] ` <20150319201137.GY10068-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2015-03-20 7:30 ` Wolfram Sang
2015-03-20 7:42 ` Uwe Kleine-König
2015-03-20 8:22 ` Wolfram Sang
2015-03-12 12:42 ` Wolfram Sang [this message]
2015-03-12 13:28 ` [PATCH 0/3] i2c: slave: API updates Geert Uytterhoeven
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=1426164123-8853-4-git-send-email-wsa@the-dreams.de \
--to=wsa@the-dreams.de \
--cc=danindrey@mail.ru \
--cc=debora@mds.com \
--cc=geert@linux-m68k.org \
--cc=horms@verge.net.au \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=marvin24@gmx.de \
--cc=u.kleine-koenig@pengutronix.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).