From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sergei Shtylyov Subject: Re: [PATCH 07/13] ARM: dts: r8a7792: initial SoC device tree Date: Tue, 7 Jun 2016 23:58:45 +0300 Message-ID: References: <13205049.n7pM8utpHF@wasted.cogentembedded.com> <2539026.OyU5nvpxa6@wasted.cogentembedded.com> <20160601005751.GG20527@verge.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: linux-renesas-soc-owner@vger.kernel.org To: Geert Uytterhoeven Cc: Simon Horman , linux-renesas-soc@vger.kernel.org, Rob Herring , Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , "devicetree@vger.kernel.org" , Magnus Damm , Russell King , "linux-arm-kernel@lists.infradead.org" List-Id: devicetree@vger.kernel.org On 06/07/2016 10:13 AM, Geert Uytterhoeven wrote: [...] >>> And that the system behaves sanely on suspend/resume. >> >> I'd be thankful if you told me how to test that. :-) > > System suspend: > > echo mem > /sys/power/state Oh. I know that one! :-) > System resume: You're gonna need a "wakeup-source" in your DTS, e.g. gpio-keys. > Serial should work too, echo "enabled" to the corresponding wakeup > file in /sys first. I'm afraid I couldn't find that file. All I saw were RPM controls... > In case of issues, try "echo 0 > /sys/module/printk/parameters/console_suspend". There's no problems suspending, it's the resuming that's a problem for me. > Good luck! As usual, there was no luck. :-) WBR, Sergei