Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752544AbbBXMWr (ORCPT ); Tue, 24 Feb 2015 07:22:47 -0500 Received: from smtp.math.uni-bielefeld.de ([129.70.45.10]:47497 "EHLO smtp.math.uni-bielefeld.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750850AbbBXMWp (ORCPT ); Tue, 24 Feb 2015 07:22:45 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Tue, 24 Feb 2015 13:22:41 +0100 From: Tobias Jakobi To: myungjoo.ham@samsung.com Cc: =?UTF-8?Q?=EC=B5=9C=EC=B0=AC=EC=9A=B0?= , Tobias Jakobi , kgene@kernel.org, =?UTF-8?Q?=EB=B0=95?= =?UTF-8?Q?=EA=B2=BD=EB=AF=BC?= , rafael.j.wysocki@intel.com, mark.rutland@arm.com, ABHILASH KESAVAN , tomasz.figa@gmail.com, Krzysztof Kozlowski , Bartlomiej Zolnierkiewicz , robh+dt@kernel.org, =?UTF-8?Q?=EB=8C=80?= =?UTF-8?Q?=EC=9D=B8=EA=B8=B0?= , linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-samsung-soc@vger.kernel.org Subject: Re: Re: [PATCHv3 0/8] devfreq: Add generic exynos memory-bus frequency driver In-Reply-To: <473523680.35451424740978095.JavaMail.weblogic@epmlwas05a> References: <473523680.35451424740978095.JavaMail.weblogic@epmlwas05a> Message-ID: <3d11219e3af0d964bd6396c6be320276@math.uni-bielefeld.de> User-Agent: Roundcube Webmail/1.1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1251 Lines: 32 Hello MyungJoo! On 2015-02-24 02:22, MyungJoo Ham wrote: > Unless you are willing to wait for 2 minutes after the kernal hangs, > you may want to adjust "DEFAULT_HUNG_TASK_TIMEOUT" to shorter value > (120 --> 5 for 5 seconds). It seems that you've cut it off in the > middle > of that "120 sec" wait. Thanks for the hint! Yes, I should probably adjust this value when doing more tests. > If it's in D state (in kernel), gdb won't work as you are experiencing. > Sorry for not testing with HDMI; my Exynos devices do not have HDMI. :) Well, like I said above, the HDMI doesn't seen to be affected by the low MIF/INT clocks. I have tested this with 1280x720 here on my Odroid X2, but I also have another user (with a U3 if I remember correctly) who also confirms that HDMI is working in combination with devfreq and simple_ondemand. I guess it's just the G2D engine that doesn't like the low clocks. Maybe it also affects the IPP subsystem, but I have no means to test this. With best wishes, Tobias -- 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/