From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrzej Hajda Subject: Re: [3/3] i2c: exynos5: do not check TRANS_STATUS in case of Exynos7 variant Date: Tue, 16 Jan 2018 10:40:36 +0100 Message-ID: References: <20171130143007.30258-4-a.hajda@samsung.com> <20180115205334.6ciwq5pouthtj3kx@ninjato> Mime-Version: 1.0 Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit Return-path: In-reply-to: <20180115205334.6ciwq5pouthtj3kx@ninjato> Content-language: en-US Sender: linux-samsung-soc-owner@vger.kernel.org To: Wolfram Sang Cc: Andi Shyti , Bartlomiej Zolnierkiewicz , Marek Szyprowski , "open list:I2C SUBSYSTEM" , "moderated list:ARM/SAMSUNG EXYNOS ARM ARCHITECTURES" List-Id: linux-i2c@vger.kernel.org On 15.01.2018 21:53, Wolfram Sang wrote: > On Thu, Nov 30, 2017 at 03:30:07PM +0100, Andrzej Hajda wrote: >> HSI2C_MASTER_ST_LOSE state is not documented properly, extensive tests >> show that hardware is usually able to recover from this state without >> interrupting the transfer. On the other side enforcing transfer repetition >> in such case does not help in many situations, especially on busy systems >> and causes -EAGAIN and -ETIMEOUT errors. Moreover documentation says that >> such state can be caused by slave clock stretching, and should not be treated >> as an error. >> >> Signed-off-by: Andrzej Hajda > Can this be applied independently of my comments to patch 2? > Yes, please apply it alone. I will continue work on patch 2. -- Regards Andrzej