From: Wolfram Sang <wsa@the-dreams.de>
To: Jean Delvare <jdelvare@suse.de>
Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>,
linux-i2c@vger.kernel.org, linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH] i2c: algo-bit: add support for I2C_M_STOP
Date: Thu, 22 Jun 2017 12:15:20 +0200 [thread overview]
Message-ID: <20170622101520.hwbzunqg5xxehttp@ninjato> (raw)
In-Reply-To: <20170622110606.6ae3aabc@endymion>
[-- Attachment #1: Type: text/plain, Size: 930 bytes --]
> I remember wishing I could drop support, asking around, and a few
> people replying to me that 10-bit slaves actually exist. But of course
> I can't find the discussion thread again.
Dropping 10-bit support would be super nice from a maintenance point of
view, but I didn't have hopes for that to happen ;) This is why I wanted
to buy a device to be able to test.
> However it seems that in many cases I2C_M_TEN is used directly (instead
> of the more correct I2C_CLIENT_TEN.) See for example
Yeah, good idea to scan for I2C_CLIENT_TEN directly. From a glimpse, I
didn't see a device which I could easily buy, connect, and sniff the
wires. But it is not urgent anyhow.
> I see also commits explicitly adding or fixing 10-bit address support
> in various I2C bus drivers, I don't think developers would be doing
> that if they didn't need it.
Agreed. It will stay, I had no intention of removing it.
Thanks for the help!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2017-06-22 10:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-17 17:12 [PATCH] i2c: algo-bit: add support for I2C_M_STOP Wolfram Sang
2017-06-19 8:30 ` Jean Delvare
2017-06-20 17:28 ` Wolfram Sang
2017-06-21 7:18 ` Jean Delvare
2017-06-21 14:30 ` Wolfram Sang
2017-06-22 9:06 ` Jean Delvare
2017-06-22 10:15 ` Wolfram Sang [this message]
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=20170622101520.hwbzunqg5xxehttp@ninjato \
--to=wsa@the-dreams.de \
--cc=jdelvare@suse.de \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=wsa+renesas@sang-engineering.com \
/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