From: Enric Balletbo i Serra <enric.balletbo@collabora.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Peter Huewe <peterhuewe@gmx.de>,
Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
wsa@the-dreams.de, tpmdd-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, Bryan Freed <bfreed@chromium.org>
Subject: Re: [tpmdd-devel] [PATCH v2] tpm: Apply a sane minimum adapterlimit value for retransmission.
Date: Thu, 2 Mar 2017 18:31:03 +0100 [thread overview]
Message-ID: <584dcb98-a78c-a070-465f-52e977650e5e@collabora.com> (raw)
In-Reply-To: <20170302172419.GA11265@lunn.ch>
Hi Andrew,
On 02/03/17 18:24, Andrew Lunn wrote:
>>>> Hi Enric
>>>>
>>>> Maybe you should remember that you need to use smaller transfers? If
>>>> you don't remember, but use the full size message every time and only
>>>> drop back on error, the i2c core is going to log rate limited
>>>> messages. By remembering, there will only be one such message in the
>>>> log.
>>>>
>>
>
>> Maybe I did not explain well but this is what the code does, when
>> i2c-core fails with -EOPNOTSUPP because the msg is too long for this
>> adapter it loop with a smaller chunk of fixed size, so you only see
>> the i2c-core message once.
>
> Hi Enric
>
> Would it not be more accurate to say, that you only see the i2c-core
> message once, for this transfer request. Is the next transfer request
> again going to use the longer length? then fail, maybe generate
> another i2c core message, depending on rate limiting, and then use the
> lower message size? I think it does.
>
> Which is why i suggested remembering the length.
>
Ah ok, sorry I did not understand you, got it now. Yes, so with this every time you do, i.e. a tpm_getpubek, you will see the i2c-core message, right. Thanks. Sounds a good suggestion for me.
Cheers,
Enric
> Andrew
>
prev parent reply other threads:[~2017-03-02 20:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-01 15:36 Enric Balletbo i Serra
2017-03-02 0:27 ` Andrew Lunn
2017-03-02 12:55 ` [tpmdd-devel] " Jarkko Sakkinen
2017-03-02 13:43 ` Peter Huewe
2017-03-02 16:34 ` Enric Balletbo i Serra
2017-03-02 17:24 ` Andrew Lunn
2017-03-02 17:31 ` Enric Balletbo i Serra [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=584dcb98-a78c-a070-465f-52e977650e5e@collabora.com \
--to=enric.balletbo@collabora.com \
--cc=andrew@lunn.ch \
--cc=bfreed@chromium.org \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=tpmdd-devel@lists.sourceforge.net \
--cc=wsa@the-dreams.de \
/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
all inboxes | Powered by JetHome®