From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Rafael J. Wysocki" Date: Wed, 02 Nov 2011 23:17:00 +0000 Subject: Re: [PATCH 3/3] ARM: mach-shmobile: sh7372 A4R support (v4) Message-Id: <201111030017.00780.rjw@sisk.pl> List-Id: References: <201110200012.43840.rjw@sisk.pl> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Magnus Damm Cc: Guennadi Liakhovetski , Linux-sh list , Linux PM list , Linux Kernel On Wednesday, November 02, 2011, Magnus Damm wrote: > On Wed, Nov 2, 2011 at 11:38 AM, Guennadi Liakhovetski > wrote: > > On Thu, 20 Oct 2011, Rafael J. Wysocki wrote: > > > >> From: Magnus Damm > >> > >> This change adds support for the sh7372 A4R power domain. > > > > This version still breaks I2C (#0) on mackerel. Tested with your > > sh7372-test branch of Oct 18th plus these four patches: > > > > 6b29305a PM / Domains: Add default power off governor function (v2) > > 3d578ae PM / Domains: Add device stop governor function (v2) > > 6c2cd02 ARM: mach-shmobile: sh7372 A4R support (v4) > > 9da11f4 ARM: mach-shmobile: sh7372 A3SP support (v4) > > Exactly how does it break IIC0? It causes some initialization issues to happen. I get the following messages on every boot: i2c-sh_mobile i2c-sh_mobile.0: Transfer request timed out i2c-sh_mobile i2c-sh_mobile.0: Polling timed out three times in a row (there's a delay too). The A4R patch is the source of that. > Does the same happen with the code base for upcoming 3.2-rc1 from > latest linux git? Yes, it does, AFAICT. Thanks, Rafael