All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Stodden <daniel.stodden@gmail.com>
To: Wolfram Sang <wsa@kernel.org>
Cc: linux-i2c@vger.kernel.org, jdelvare@suse.de
Subject: Re: [RFC PATCH] i2c: Support Smbus 3.0 block sizes up to 255 bytes.
Date: Tue, 28 Jul 2020 05:46:42 -0700	[thread overview]
Message-ID: <CD3AE432-8D30-4116-A5A0-3538F674F466@gmail.com> (raw)
In-Reply-To: <14454F49-740B-4423-A2F9-4B00B18A9A74@gmail.com>



> On Jul 28, 2020, at 4:40 AM, Daniel Stodden <daniel.stodden@gmail.com> wrote:
> 
> “3” ;)

Sorry, I got confused. You’re suggesting to label the old calls “2” and
the new ones take the original name.

That’s fine! But we need to figure out what we really require, and which
protocol to prefer.

 * If the new block size can be too large for small clients with Smbus < 3
   slaves, we’re not going to deprecate those.

   But phasing out 32 byte transfers for good would make a simpler header.

 * If some clients need the old calls and make a new i2c_smbusX_data,
   then those aren’t /* deprecated */ any more.

   With the above scheme, we're making i2c_smbus_data size 255 and
   and rename the old type to smbus2.

Btw: I think I was confused because would have called those i2c_smbus1_ then.

Best,
Daniel

      reply	other threads:[~2020-07-28 12:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-28  0:47 [RFC PATCH] i2c: Support Smbus 3.0 block sizes up to 255 bytes daniel.stodden
2020-07-28  9:40 ` Wolfram Sang
2020-07-28 10:18   ` Daniel Stodden
2020-07-28 10:36     ` Wolfram Sang
2020-07-28 11:27       ` Daniel Stodden
2020-07-28 17:04   ` Jean Delvare
2020-07-28 21:16     ` Daniel Stodden
2020-07-29 10:51       ` Wolfram Sang
2020-07-28 11:16 ` Wolfram Sang
2020-07-28 11:40   ` Daniel Stodden
2020-07-28 12:46     ` Daniel Stodden [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=CD3AE432-8D30-4116-A5A0-3538F674F466@gmail.com \
    --to=daniel.stodden@gmail.com \
    --cc=jdelvare@suse.de \
    --cc=linux-i2c@vger.kernel.org \
    --cc=wsa@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.