Received: by 2002:a25:31c3:0:0:0:0:0 with SMTP id x186csp530186ybx; Wed, 6 Nov 2019 22:17:33 -0800 (PST) X-Google-Smtp-Source: APXvYqzZMEHComjvVhVr5d7kA/rKt6g3OVXPFkqeEeglfqB/70c0XpvtBDHc1DWr2GnKZ3RIAgcn X-Received: by 2002:a50:ec1a:: with SMTP id g26mr1769581edr.84.1573107453239; Wed, 06 Nov 2019 22:17:33 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1573107453; cv=none; d=google.com; s=arc-20160816; b=dW4hBmVtscrE13cDaRFnJ+DQgF7EaVQCX8NecqeJwy8E1musYqh3kDSdd9I+T1YzQd l4xyFFh6pwRt+mXrENoUcZlSmWnniQH3le+nnKdUK0wKczuStO/N6AhN7PHUgr56sfRZ Y3OZX+aKkRsXaVvHmoAnf16snCQ4Vh9AWb7fc9Tnc9r0y7/F7GQ2rt9VY/FyX/jDpv34 ZRE3k9L9b1BFLaQuqD4xvz/cLWqXS3FtdFHDjah5iu8FOFEiInzPidRQZgj9mxqtYZC4 Eg6yBoR9HNGiY0UoT9ALPZaxuCKrOXsYa7LQ8pUMJmgxpF0gXKeS3CpSNqn4PX4wAH7B 5NwA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=b6XwzsC8T7k6SsHnaEqnkGYpU/j8kgJJS6Ga6U3GP2U=; b=dXh78Y2ied4Qaeg0ytob8Y1mMWxr3GohWNu26RmokfMihnGnLfM4FiwxI2mkvKapXp FKZDYT8y5loUZsrZcKNFRXeTQV4CTM86FVrnSqKDtxfQx69mQZaezn7dA1K4EKCTuqtR BwS12DjSxaFiWoA5epY62hK4eV6D2+8PZfv1Khi5ERUmx3CqtM/bQkXZz71gz5KHUszL WfwbtFlHy3GuAi5G6XvhGAnCWTFOzuYuLlJmqq9xsm5OaqWaHA9K1dpppLU17QcBZTyV TWKAbZZHUiM+ouzb9Anpn2r6+kTbykfJvxuF99Ty8j577x9ZuqhSh+FlivAhF4MVEMja SjTg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=VIWMNYO2; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id d38si635179eda.53.2019.11.06.22.17.09; Wed, 06 Nov 2019 22:17:33 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=VIWMNYO2; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726985AbfKGGNV (ORCPT + 99 others); Thu, 7 Nov 2019 01:13:21 -0500 Received: from mail-ed1-f66.google.com ([209.85.208.66]:45259 "EHLO mail-ed1-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725763AbfKGGNU (ORCPT ); Thu, 7 Nov 2019 01:13:20 -0500 Received: by mail-ed1-f66.google.com with SMTP id b5so884968eds.12; Wed, 06 Nov 2019 22:13:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=b6XwzsC8T7k6SsHnaEqnkGYpU/j8kgJJS6Ga6U3GP2U=; b=VIWMNYO2uJZ/ucdnjhZQPeoGhFSDz7GxnECCBYJyaZJo/aA767Fx5wQZ4G/kd3863l WR+hwk509J/YPOvBRlwBfmWKJc4lub6uj+fHcMJDnxPfKLwVzsJP8m9F7TgmUe/ySThl zbAwfLtePYTJyT8qGRn6P+d2j3706q2iMY1q841WLX7iBaLfO1hd2p5HJoao2wa4QT0X mnASaMI2n5wraePRgoghikEcm95gEjyWQFfZjxHckPpJyD0HOlrKPZ9kSryeA/OA7uq1 bvA/UwDlyJOredDzeHpZaB4mqzuryo+geg847EC/h+YGoK2FAL2fPej4N0lfUZPjkPIa 2GRw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=b6XwzsC8T7k6SsHnaEqnkGYpU/j8kgJJS6Ga6U3GP2U=; b=lDTFys77s5QZksQoW1+vVyuWiKK6E79z7UTuaPThYeg7YbOkWlMI8t4iDEhFfZjFlf A6YxEK8HqCH5z0QwHmfwQTm8n7a1RNQIRjEXnQuInAT9KXaUiu5ceL9eNiIzS+2KiiYH 8lk4hZOJRNU+TDLmkjQStrJetM+Bc6qHF2lSfX81Ys6IP6gCze7a/E6KjZQTtX/XsYHg THAsVfHyN9+Ft2cYciwRI7nSClWzxVvSJ7mrPz9/iVFqFswkuyiiuyFoLIJUGj5Nxwzi 0QFnlbBozMDBQzFxEwTuaWfFQN1rKLLkl32ZZASaYGJ1/E7z4jsqFK99ohjPHORcOAni 25iw== X-Gm-Message-State: APjAAAXJL9vdiJv9Xc+N1rbvLNV8GcTM71tfPU5k/3DYI7iQoAGXK7Au WMJcyMTH2hu8mdhrIlKnW8vfJDZjMp/LvIF1A6Q= X-Received: by 2002:a17:906:698b:: with SMTP id i11mr1353680ejr.97.1573107198964; Wed, 06 Nov 2019 22:13:18 -0800 (PST) MIME-Version: 1.0 References: <20190219012447.5900-1-sxauwsk@163.com> <2019110516474778997625@163.com> In-Reply-To: <2019110516474778997625@163.com> From: Shubhrajyoti Datta Date: Thu, 7 Nov 2019 11:43:07 +0530 Message-ID: Subject: Re: Re: [PATCH v2] i2c: cadence: try reset when master receive arbitration lost To: "sxauwsk@163.com" Cc: Michal Simek , Shubhrajyoti Datta , Wolfram Sang , linux-arm-kernel , linux-i2c , linux-kernel Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Shikai, On Tue, Nov 5, 2019 at 2:18 PM sxauwsk@163.com wrote: > > >Hi Shikai, > > > >On Tue, Feb 19, 2019 at 8:19 AM Shikai Wang wrote: > >> > >> When the adapter receive arbitration lost error interrupts, > >> cdns_i2c_master_xfer return to the caller directly instead of resetting > >> the adapter which resulted in the adapter being out of control. > >> > >> So when driver detect err_status such as arbitration lost, > >> then try to repair and fix it. > >> > >I am missing the issue that you are facing. > >You are having a multimaster scenario and getting arbitration lost. > > > >the current code would attempt a retry did that lead to any issues? > > > >Can you explain the issue that you are facing? > > Of cource, The following describe my situation. > > In my product, Touchscreen connect to zynq-7000 XC7Z010 by i2c bus( Just connect only one i2c-device of touchscreen), > when user tap Touchscreen, Touchscreen interrupt send to CPU and notifyed i2c-driver to obtain location data by i2c-bus, So it is single master single slave. > > when Tap the screen frequently, sometimes CPU get interrupt from touchscreen and try to obtain data, then detect arbitration lost, the arbitration lost is surprising in non-multimaster scenario. Is there any other master in the configuration that we may not be triggering. Or can you probe the lines? > Although i2c-driver try three times, it's useless. You get bus busy? what is the issue. > > Actually i2c clock-line and data-line keep high, that mean i2c bus free. > Once this situation occur, i2c-control did't work anynay but cpu receive interrputs still. > > I am sorry that I have't found a good solution for this issuse;