Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753445AbbFXNSo (ORCPT ); Wed, 24 Jun 2015 09:18:44 -0400 Received: from mga03.intel.com ([134.134.136.65]:13469 "EHLO mga03.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752818AbbFXNSf (ORCPT ); Wed, 24 Jun 2015 09:18:35 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.13,671,1427785200"; d="scan'208";a="513518633" Date: Wed, 24 Jun 2015 16:18:30 +0300 From: "mika.westerberg@linux.intel.com" To: "De Marchi, Lucas" Cc: "christian.ruppert@alitech.com" , "lucas.de.marchi@gmail.com" , "linux-kernel@vger.kernel.org" , "wsa@the-dreams.de" , "Mello, Fabio" , "jarkko.nikula@linux.intel.com" , "christian.ruppert@abilis.com" , "linux-i2c@vger.kernel.org" Subject: Re: [PATCH] i2c: designware: use enable on resume instead initialization Message-ID: <20150624131830.GF827@lahna.fi.intel.com> References: <1433785828-4100-1-git-send-email-lucas.de.marchi@gmail.com> <20150609085146.GD1478@lahna.fi.intel.com> <20150610070722.GM1478@lahna.fi.intel.com> <20150624112723.GE827@lahna.fi.intel.com> <1435150578.1075.5.camel@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1435150578.1075.5.camel@intel.com> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 977 Lines: 17 On Wed, Jun 24, 2015 at 12:56:19PM +0000, De Marchi, Lucas wrote: > Yeah, but it would be bad to ignore the problem as well. The way it is now > kills any possibility of using DW controller for reading sensors like > gyroscope, accelerometer, barometer that have higher sampling rate etc. I'll > try to come up with a new patch but since I can't reproduce the problem here > it'd be good to know if there's any means for me to test. What do you think > that could be done? Maybe putting the controller to sleep only in case of > errors? Instead of disabling the adapter after each transfer, I wonder if it is enough if we just mask all interrupts? That should also prevent the interrupt loop Christian is seeing on his hardware. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/