[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150624131830.GF827@lahna.fi.intel.com>
Date: Wed, 24 Jun 2015 16:18:30 +0300
From: "mika.westerberg@...ux.intel.com" <mika.westerberg@...ux.intel.com>
To: "De Marchi, Lucas" <lucas.demarchi@...el.com>
Cc: "christian.ruppert@...tech.com" <christian.ruppert@...tech.com>,
"lucas.de.marchi@...il.com" <lucas.de.marchi@...il.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"wsa@...-dreams.de" <wsa@...-dreams.de>,
"Mello, Fabio" <fabio.mello@...el.com>,
"jarkko.nikula@...ux.intel.com" <jarkko.nikula@...ux.intel.com>,
"christian.ruppert@...lis.com" <christian.ruppert@...lis.com>,
"linux-i2c@...r.kernel.org" <linux-i2c@...r.kernel.org>
Subject: Re: [PATCH] i2c: designware: use enable on resume instead
initialization
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@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists