From: Andrew Lunn <andrew-g2DYL2Zd6BY@public.gmane.org>
To: Enric Balletbo i Serra
<enric.balletbo-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>
Cc: wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Bryan Freed <bfreed-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>,
tpmdd-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [PATCH v2] tpm: Apply a sane minimum adapterlimit value for retransmission.
Date: Thu, 2 Mar 2017 18:24:19 +0100 [thread overview]
Message-ID: <20170302172419.GA11265@lunn.ch> (raw)
In-Reply-To: <2c648dea-35df-cdf7-3882-40bb855d3573-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>
> >> 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.
Andrew
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
next prev parent reply other threads:[~2017-03-02 17:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-01 15:36 [PATCH v2] tpm: Apply a sane minimum adapterlimit value for retransmission Enric Balletbo i Serra
[not found] ` <20170301153617.10106-1-enric.balletbo-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>
2017-03-02 0:27 ` Andrew Lunn
2017-03-02 12:55 ` Jarkko Sakkinen
[not found] ` <20170302125543.bsn7z5zkerabzh4u-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2017-03-02 13:43 ` Peter Huewe
[not found] ` <BA3AA3EA-054E-4B65-82C2-C01EBD2849F2-Mmb7MZpHnFY@public.gmane.org>
2017-03-02 16:34 ` Enric Balletbo i Serra
[not found] ` <2c648dea-35df-cdf7-3882-40bb855d3573-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>
2017-03-02 17:24 ` Andrew Lunn [this message]
[not found] ` <20170302172419.GA11265-g2DYL2Zd6BY@public.gmane.org>
2017-03-02 17:31 ` Enric Balletbo i Serra
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=20170302172419.GA11265@lunn.ch \
--to=andrew-g2dyl2zd6by@public.gmane.org \
--cc=bfreed-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org \
--cc=enric.balletbo-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=tpmdd-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.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).