linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jarkko Nikula <jarkko.nikula@linux.intel.com>
To: Hans de Goede <hdegoede@redhat.com>,
	Oliver Neukum <oneukum@suse.com>,
	andriy.shevchenko@linux.intel.com,
	mika.westerberg@linux.intel.com, linux-i2c@vger.kernel.org
Subject: Re: [PATCH] i2c-designware: increase timeout of semaphore transfer
Date: Mon, 20 Mar 2017 15:52:12 +0200	[thread overview]
Message-ID: <4ddb7df4-774a-904a-eabd-3c02f419b9fe@linux.intel.com> (raw)
In-Reply-To: <704db0f5-7951-3d07-1d0b-4c742dd562d0@redhat.com>

On 03/20/17 15:39, Hans de Goede wrote:
> Hi,
>
> On 20-03-17 14:37, Oliver Neukum wrote:
>> Our testing shows the semaphore failing to be transferred on CherryTrail
>> in about 0.5% of all cases. The existing timeout needs to be lengthened
>> to accomodate the worst cases.
>>
>> V2: Rebased on
>> https://cgit.freedesktop.org/drm-intel/commit/?h=topic/designware-baytrail
>>
>>
>> Signed-off-by: Oliver Neukum <oneukum@suse.com>
>
> Looks good to me:
>
> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
>
Acked-by: Jarkko Nikula <jarkko.nikula@linux.intel.com>

  reply	other threads:[~2017-03-20 13:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-20 13:37 [PATCH] i2c-designware: increase timeout of semaphore transfer Oliver Neukum
2017-03-20 13:39 ` Hans de Goede
2017-03-20 13:52   ` Jarkko Nikula [this message]
2017-03-22  8:48 ` Wolfram Sang
  -- strict thread matches above, loose matches on Subject: below --
2017-03-16 16:24 Oliver Neukum
2017-03-16 16:35 ` Andy Shevchenko
2017-03-17  7:35   ` Hans de Goede
2017-03-20 13:39     ` Oliver Neukum

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=4ddb7df4-774a-904a-eabd-3c02f419b9fe@linux.intel.com \
    --to=jarkko.nikula@linux.intel.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=hdegoede@redhat.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=oneukum@suse.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).