From: Wolfram Sang <wsa@the-dreams.de>
To: Nicola Corna <nicola@corna.info>
Cc: Jonathan Cameron <jic23@kernel.org>,
Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald <pmeerw@pmeerw.net>,
linux-i2c@vger.kernel.org
Subject: Re: [RESEND PATCH 1/3] i2c: added FUNC flag for unsupported clock stretching
Date: Tue, 20 Oct 2015 17:35:11 +0200 [thread overview]
Message-ID: <20151020153511.GI5379@katana> (raw)
In-Reply-To: <1442410323-9833-1-git-send-email-nicola@corna.info>
[-- Attachment #1: Type: text/plain, Size: 1858 bytes --]
On Wed, Sep 16, 2015 at 03:32:01PM +0200, Nicola Corna wrote:
> Added I2C_FUNC_NO_CLK_STRETCH, to be used when clock stretching is not
> supported.
>
> Signed-off-by: Nicola Corna <nicola@corna.info>
I think this should be rather a quirk than a functionality, i.e.
I2C_AQ_NO_CLK_STRETCH. Agree?
> ---
> Documentation/i2c/functionality | 1 +
> include/uapi/linux/i2c.h | 1 +
> 2 files changed, 2 insertions(+)
>
> diff --git a/Documentation/i2c/functionality b/Documentation/i2c/functionality
> index 4aae8ed..f53807e 100644
> --- a/Documentation/i2c/functionality
> +++ b/Documentation/i2c/functionality
> @@ -21,6 +21,7 @@ For the most up-to-date list of functionality constants, please check
> I2C_M_REV_DIR_ADDR and I2C_M_NO_RD_ACK
> flags (which modify the I2C protocol!)
> I2C_FUNC_NOSTART Can skip repeated start sequence
> + I2C_FUNC_NO_CLK_STRETCH Does NOT support clock stretching
> I2C_FUNC_SMBUS_QUICK Handles the SMBus write_quick command
> I2C_FUNC_SMBUS_READ_BYTE Handles the SMBus read_byte command
> I2C_FUNC_SMBUS_WRITE_BYTE Handles the SMBus write_byte command
> diff --git a/include/uapi/linux/i2c.h b/include/uapi/linux/i2c.h
> index b0a7dd6..59e4b43 100644
> --- a/include/uapi/linux/i2c.h
> +++ b/include/uapi/linux/i2c.h
> @@ -88,6 +88,7 @@ struct i2c_msg {
> #define I2C_FUNC_SMBUS_PEC 0x00000008
> #define I2C_FUNC_NOSTART 0x00000010 /* I2C_M_NOSTART */
> #define I2C_FUNC_SLAVE 0x00000020
> +#define I2C_FUNC_NO_CLK_STRETCH 0x00000040 /* No check for SCL low */
> #define I2C_FUNC_SMBUS_BLOCK_PROC_CALL 0x00008000 /* SMBus 2.0 */
> #define I2C_FUNC_SMBUS_QUICK 0x00010000
> #define I2C_FUNC_SMBUS_READ_BYTE 0x00020000
> --
> 2.5.1
>
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-10-20 15:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-16 13:32 [RESEND PATCH 1/3] i2c: added FUNC flag for unsupported clock stretching Nicola Corna
2015-10-20 15:35 ` Wolfram Sang [this message]
2015-10-27 19:14 ` Nicola Corna
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=20151020153511.GI5379@katana \
--to=wsa@the-dreams.de \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-i2c@vger.kernel.org \
--cc=nicola@corna.info \
--cc=pmeerw@pmeerw.net \
/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).