linux-renesas-soc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>,
	Linux I2C <linux-i2c@vger.kernel.org>,
	Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: [RFC PATCH] i2c: gpio: fault-injector: add 'lose_arbitration' injector
Date: Sat, 16 Feb 2019 14:04:48 +0100	[thread overview]
Message-ID: <20190216130447.7eiyjve3gusvyhfo@ninjato> (raw)
In-Reply-To: <CAMuHMdUFsMa4+FthqittPEG3u3DgZOphz+_CFqu6epSWJcJxSQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1498 bytes --]

Hi Geert,

> > Sure thing, this was a typical RFC marker :) It is now calculated based
> > on bit_data.udelay and has a comment.
> 
> But that value bears no direct relation to the transfer speed as used by the
> master to interfere with, right?

Yeah, the assumption would have been that i2c-gpio is configured as the
same speed as the master under test. However, ...

> Still, you have to guess anyway.

... I changed the user API meanwhile. The value you write is the value
used for this delay. Because 'number of interfered arbitrations' is
vague anyhow. Because of latencies, interrupts sometimes trigger twice
per interference, so this number becomes meaningless.

> > Any pointer for that information? I seem to recall that the format
> > string is also used to parse the user string to the set function. I
> > sadly can't find that documented, but all the helper macros in
> > fs/debugfs/file.c have a format string, too, even if WO.
> 
> fs/libfs.c:struct simple_attr {
> 
>         const char *fmt;        /* format for read operation */
> 
> It's being parsed using simple_strtoll(), so it takes whatever format is being
> passed by the writer.
> 
> Perhaps you were confused by the term "read", which is from the point of
> view of userspace, not of the driver.

Because all other users (even WO) have that still set, I prefer
consistency here.

Will send out next version, including panic-fault-injector, hopefully
today.

Thanks,

   Wolfram

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2019-02-16 13:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-21 14:28 [RFC PATCH] i2c: gpio: fault-injector: add 'lose_arbitration' injector Wolfram Sang
2019-02-05 13:31 ` Wolfram Sang
2019-02-11 10:30 ` Geert Uytterhoeven
2019-02-11 20:59   ` Wolfram Sang
2019-02-12  8:31     ` Geert Uytterhoeven
2019-02-16 13:04       ` 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=20190216130447.7eiyjve3gusvyhfo@ninjato \
    --to=wsa@the-dreams.de \
    --cc=geert@linux-m68k.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=wsa+renesas@sang-engineering.com \
    /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).