From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jon Hunter Subject: Re: [PATCH V2 01/10] ARM: PMU: Add runtime PM Support Date: Thu, 5 Jul 2012 19:40:42 -0500 Message-ID: <4FF6340A.6020409@ti.com> References: <20120608094708.GC19062@mudshark.cambridge.arm.com> <4FD21930.4000800@ti.com> <20120611173930.GD28235@mudshark.cambridge.arm.com> <4FD64083.3020800@ti.com> <20120612092842.GA2991@mudshark.cambridge.arm.com> <4FD7B1DC.30108@ti.com> <20120612213150.GC24380@mudshark.cambridge.arm.com> <4FD7C597.7060501@ti.com> <20120702095539.GD22239@mudshark.cambridge.arm.com> <4FF1D15E.7040301@ti.com> <20120702220117.GD25234@mudshark.cambridge.arm.com> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Return-path: Received: from comal.ext.ti.com ([198.47.26.152]:44031 "EHLO comal.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750987Ab2GFAkr (ORCPT ); Thu, 5 Jul 2012 20:40:47 -0400 In-Reply-To: <20120702220117.GD25234@mudshark.cambridge.arm.com> Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: Will Deacon Cc: Kevin Hilman , Paul Walmsley , Benoit Cousson , Ming Lei , linux-omap , linux-arm Hi Will, On 07/02/2012 05:01 PM, Will Deacon wrote: > On Mon, Jul 02, 2012 at 05:50:38PM +0100, Jon Hunter wrote: >> On 07/02/2012 04:55 AM, Will Deacon wrote: >>> >>> Did you have any luck getting to the bottom of this? >> >> I am still waiting for feedback from design. They were trying to confirm >> my observations. Unfortunately, it is taking some time. I will ping them >> again. > > Ok, thanks. If pinging doesn't work, bribery can be quite effective with > hardware guys :) Yes looks like I am going to need to get creative :-) >>> It would be good to take your PMU suspend/resume patches once we know that >>> they will get used. >> >> Yes that would be good. I could drop the 4460 specific changes for now >> and make 4460 work in the same way as 4430 (using CTI) for the time >> being and see if we can get these in. However, I recall that was not >> working for you, but it was working fine for me. > > Indeed, that hack didn't help me and I'd rather not commit it if it only > partially fixes the problem. A better bet might just be to go with your > original approach and see how many bug reports we receive. That might also > help us narrow down the problem, but it's your call. Ok, I think that that is best. > In the meantime, I pushed what I think is the latest drop of your series to > a new branch on kernel.org: > > git://git.kernel.org/pub/scm/linux/kernel/git/will/linux.git perf/omap4-dev Looks good. Cheers Jon From mboxrd@z Thu Jan 1 00:00:00 1970 From: jon-hunter@ti.com (Jon Hunter) Date: Thu, 5 Jul 2012 19:40:42 -0500 Subject: [PATCH V2 01/10] ARM: PMU: Add runtime PM Support In-Reply-To: <20120702220117.GD25234@mudshark.cambridge.arm.com> References: <20120608094708.GC19062@mudshark.cambridge.arm.com> <4FD21930.4000800@ti.com> <20120611173930.GD28235@mudshark.cambridge.arm.com> <4FD64083.3020800@ti.com> <20120612092842.GA2991@mudshark.cambridge.arm.com> <4FD7B1DC.30108@ti.com> <20120612213150.GC24380@mudshark.cambridge.arm.com> <4FD7C597.7060501@ti.com> <20120702095539.GD22239@mudshark.cambridge.arm.com> <4FF1D15E.7040301@ti.com> <20120702220117.GD25234@mudshark.cambridge.arm.com> Message-ID: <4FF6340A.6020409@ti.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Hi Will, On 07/02/2012 05:01 PM, Will Deacon wrote: > On Mon, Jul 02, 2012 at 05:50:38PM +0100, Jon Hunter wrote: >> On 07/02/2012 04:55 AM, Will Deacon wrote: >>> >>> Did you have any luck getting to the bottom of this? >> >> I am still waiting for feedback from design. They were trying to confirm >> my observations. Unfortunately, it is taking some time. I will ping them >> again. > > Ok, thanks. If pinging doesn't work, bribery can be quite effective with > hardware guys :) Yes looks like I am going to need to get creative :-) >>> It would be good to take your PMU suspend/resume patches once we know that >>> they will get used. >> >> Yes that would be good. I could drop the 4460 specific changes for now >> and make 4460 work in the same way as 4430 (using CTI) for the time >> being and see if we can get these in. However, I recall that was not >> working for you, but it was working fine for me. > > Indeed, that hack didn't help me and I'd rather not commit it if it only > partially fixes the problem. A better bet might just be to go with your > original approach and see how many bug reports we receive. That might also > help us narrow down the problem, but it's your call. Ok, I think that that is best. > In the meantime, I pushed what I think is the latest drop of your series to > a new branch on kernel.org: > > git://git.kernel.org/pub/scm/linux/kernel/git/will/linux.git perf/omap4-dev Looks good. Cheers Jon