From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: linux-i2c@vger.kernel.org
Cc: linux-renesas-soc@vger.kernel.org,
Alain Volmat <alain.volmat@st.com>,
Wolfram Sang <wsa+renesas@sang-engineering.com>
Subject: [PATCH v2 0/1] i2c: add slave testunit driver
Date: Mon, 14 Sep 2020 09:17:36 +0200 [thread overview]
Message-ID: <20200914071737.6354-1-wsa+renesas@sang-engineering.com> (raw)
Motivated by a series by Alain Volmat which implements SMBus Host Notify
support as a slave backend (already upstream), I wondered how I could
actually test it. Then, I picked up my old idea of a "custom remote
device" and implemented it as another slave backend. This is the outcome
and it works quite well on my Renesas Lager board where I connected two
I2C busses where both I2C controllers are master and slave. One slave is
the testunit, one slave is the HostNotify listener.
As mentioned elsewhere, support for SMBus Alert and I2C_M_RECV_LEN are
already planned. But I guess you can do much more.
Ideas and comments welcome!
Happy hacking,
Wolfram
Wolfram Sang (1):
i2c: add slave testunit driver
Documentation/i2c/slave-testunit-backend.rst | 66 +++++++
drivers/i2c/Kconfig | 8 +
drivers/i2c/Makefile | 1 +
drivers/i2c/i2c-slave-testunit.c | 174 +++++++++++++++++++
4 files changed, 249 insertions(+)
create mode 100644 Documentation/i2c/slave-testunit-backend.rst
create mode 100644 drivers/i2c/i2c-slave-testunit.c
--
2.20.1
next reply other threads:[~2020-09-14 7:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-14 7:17 Wolfram Sang [this message]
2020-09-14 7:17 ` [PATCH v2 1/1] i2c: add slave testunit driver Wolfram Sang
2020-09-14 8:36 ` Wolfram Sang
2020-09-14 8:40 ` Alain Volmat
2020-09-21 9:05 ` Wolfram Sang
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=20200914071737.6354-1-wsa+renesas@sang-engineering.com \
--to=wsa+renesas@sang-engineering.com \
--cc=alain.volmat@st.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
/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).