From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: linux-i2c <linux-i2c@vger.kernel.org>
Subject: PMBus and SMBUS_BLOCK with "extended" lenght
Date: Fri, 31 Mar 2017 19:17:27 +1100 [thread overview]
Message-ID: <1490948247.3177.233.camel@kernel.crashing.org> (raw)
Hi folks !
Did anybody give thoughts to how we could support "smbus" block
transfers with a size up to 0xff ? This is an extension of smbus
that part of the PMbus protocol spec.
Our current code has a lot of places where I2C_SMBUS_BLOCK_MAX is
hard wired. Including down in almost all drivers.
So it would have to be an evolutionary process.
I was thinking a message flag along with a functionality bit
maybe ?
Cheers,
Ben.
next reply other threads:[~2017-03-31 8:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-31 8:17 Benjamin Herrenschmidt [this message]
2017-03-31 16:33 ` PMBus and SMBUS_BLOCK with "extended" lenght Wolfram Sang
2017-04-19 5:40 ` Benjamin Herrenschmidt
2017-04-19 6:54 ` 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=1490948247.3177.233.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=linux-i2c@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).