From: Wolfram Sang <wsa@the-dreams.de>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linux-i2c <linux-i2c@vger.kernel.org>
Subject: Re: PMBus and SMBUS_BLOCK with "extended" lenght
Date: Wed, 19 Apr 2017 08:54:36 +0200 [thread overview]
Message-ID: <20170419065436.GA1432@katana> (raw)
In-Reply-To: <1492580427.25766.131.camel@kernel.crashing.org>
[-- Attachment #1: Type: text/plain, Size: 344 bytes --]
> Not a huge deal, all this is just a thought, I don't think I have a
> device to deal with today that will return more on any of my systems (I
> can double check later). I just noticed that while reading the PMbus
> spec.
I once stumbled over a TPM device which had a flag to send either 32 or
255 byte. Can't recall which exactly, though.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2017-04-19 6:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-31 8:17 PMBus and SMBUS_BLOCK with "extended" lenght Benjamin Herrenschmidt
2017-03-31 16:33 ` Wolfram Sang
2017-04-19 5:40 ` Benjamin Herrenschmidt
2017-04-19 6:54 ` 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=20170419065436.GA1432@katana \
--to=wsa@the-dreams.de \
--cc=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).