From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.6 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 413E3C31E5B for ; Wed, 19 Jun 2019 15:11:38 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 1202021880 for ; Wed, 19 Jun 2019 15:11:38 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="sBFjUPLA" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725899AbfFSPLh (ORCPT ); Wed, 19 Jun 2019 11:11:37 -0400 Received: from mail-lf1-f68.google.com ([209.85.167.68]:41894 "EHLO mail-lf1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726009AbfFSPLh (ORCPT ); Wed, 19 Jun 2019 11:11:37 -0400 Received: by mail-lf1-f68.google.com with SMTP id 136so12419026lfa.8; Wed, 19 Jun 2019 08:11:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=c4lE+fDC/zjvYHc6bMY9y0fXVZdkPQJMI12oOjRnI+k=; b=sBFjUPLAQ8cjPXN9JHlZlv22CPccFqpl0Ah+uRBwMn8r1UCgPDCoEhbg46/fdDQuok Me2HINI71XxTkeo9la7F1nAB+b5IIrWzNrNrldg5nGsUkWbAWAFjG8kv1uLXBdG9zUt8 LloQTMvNLcvcV9DDQMu7FuEjIdwTrNiE7fk0NVySbjzJSRwFm9be/71NIi2GITXQNVPt i3q+l2vt0qusV20jkNMXhHaSwhBe+wOFaTi296FszorbodLdURk0IHm/G2vutH7m8hDa Rokc24nejYYYW1E2BBqQP/YYfucJda/ZFDubDjJvisckgB5hzCHrOjhKqZeTv/hxpPAn NatA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=c4lE+fDC/zjvYHc6bMY9y0fXVZdkPQJMI12oOjRnI+k=; b=QRRvqMs2FEOXrePXEITXxF+wkPkMhpcviGi0wNjFTenHwsfrgJthGkYpmVgsfgB9m2 mTR+nJGPY9/3YeelPIOyKrNXaHhqJOnpXkcRfjWhQ0nixZYKnhwYKN26R42N0aa3A7lZ ZBLtdFT4+atyE71DshfBEDBPEidba4AvbvA5VAH/Yotqy8gMtf9SV97Sbf0ZefNrY4wt ybuY70W3BXWv1LHyu3ZTNrtbdqFQadrMlUgNOU7a/9LjdaXPaaD/Qu30sOwg/RjYBQua Max+71uOpqV1whPA3eKLXCFGkr9q10w3dCmL1KksKMb/aG6+3EBnsSrhGx6HK0ZvonvW RM2w== X-Gm-Message-State: APjAAAVYfZKx3IV4mJ3ylD6kTa2WNyo+keGPtrsM3QuoOqjPIlEACx9A tKcNfXqyTRjMLU7iwsf9Z3gqDcuWSGzt/G+oxAY= X-Google-Smtp-Source: APXvYqyCK8YTFUBv1UQndRV7hhrkJSwGjOFnCWzcsoSyOWUwr+U9SgjEgPfsQwWEyMFD3ET+TTI6fNJRcqHDftXikr0= X-Received: by 2002:a05:6512:29a:: with SMTP id j26mr28681961lfp.44.1560957095128; Wed, 19 Jun 2019 08:11:35 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Fabio Estevam Date: Wed, 19 Jun 2019 12:11:50 -0300 Message-ID: Subject: Re: [IMX] [DRM]: suspend/resume support To: Pintu Agarwal Cc: open list , "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" , Kernelnewbies , linux-pm@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Sender: linux-pm-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-pm@vger.kernel.org On Wed, Jun 19, 2019 at 12:05 PM Pintu Agarwal wrote: > Okay. I will surely try it on another IMX6 fresh board. > With 5.1.11 you mean the kernel from mainline kernel.org > Or, is there a separate kernel repo for imx6. If yes, please let me know. 5.1.11 from kernel.org > > Then you can test suspend/resume and see if HDMI hangs or not. > > > By this suspend/resume, you mean "suspend-to-ram" or "suspend-to-disk" ? I tested with "echo mem > /sys/power/state" > This scenario is not with suspend/resume. > This hang is, when we make hdmi as a loadable module (.ko) and trying > to install it after resume. > In this case, suspend/resume will not come into picture. Not sure why > it still hangs. > Do you have any clue for this scenario? I haven't tried this one. Please test it with 5.1.11 and if it fails, please report.