From: "Bence Csókás" <bence98@sch.bme.hu>
To: <linux-i2c@vger.kernel.org>
Cc: "Bence Csókás" <bence98@sch.bme.hu>,
linux-kernel@vger.kernel.org, "Wolfram Sang" <wsa@the-dreams.de>
Subject: [PATCH v4 1/2] i2c: Add I2C_AQ_NO_REP_START adapter quirk
Date: Wed, 31 Mar 2021 19:19:20 +0000 [thread overview]
Message-ID: <20210331191921.1066172-2-bence98@sch.bme.hu> (raw)
In-Reply-To: <20210331191921.1066172-1-bence98@sch.bme.hu>
This quirk signifies that the adapter cannot do a repeated
START, it always issues a STOP condition after transfers.
Suggested-by: Wolfram Sang <wsa@the-dreams.de>
Signed-off-by: Bence Csókás <bence98@sch.bme.hu>
---
include/linux/i2c.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/include/linux/i2c.h b/include/linux/i2c.h
index 56622658b215..a670ae129f4b 100644
--- a/include/linux/i2c.h
+++ b/include/linux/i2c.h
@@ -687,6 +687,8 @@ struct i2c_adapter_quirks {
#define I2C_AQ_NO_ZERO_LEN_READ BIT(5)
#define I2C_AQ_NO_ZERO_LEN_WRITE BIT(6)
#define I2C_AQ_NO_ZERO_LEN (I2C_AQ_NO_ZERO_LEN_READ | I2C_AQ_NO_ZERO_LEN_WRITE)
+/* adapter cannot do repeated START */
+#define I2C_AQ_NO_REP_START BIT(7)
/*
* i2c_adapter is the structure used to identify a physical i2c bus along
--
2.31.0
next prev parent reply other threads:[~2021-03-31 19:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-31 19:19 [PATCH v4 0/2] Adding i2c-cp2615: i2c support for Silicon Labs' CP2615 Digital Audio Bence Csókás
2021-03-31 19:19 ` Bence Csókás [this message]
2021-04-05 20:45 ` [PATCH v4 1/2] i2c: Add I2C_AQ_NO_REP_START adapter quirk Wolfram Sang
2021-03-31 19:19 ` [PATCH v4 2/2] Adding i2c-cp2615: i2c support for Silicon Labs' CP2615 Digital Audio Bridge Bence Csókás
2021-03-31 20:46 ` kernel test robot
2021-04-01 6:11 ` kernel test robot
2021-04-05 20:46 ` 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=20210331191921.1066172-2-bence98@sch.bme.hu \
--to=bence98@sch.bme.hu \
--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).