From: Fabio Estevam <festevam@gmail.com>
To: Pintu Agarwal <pintu.ping@gmail.com>
Cc: open list <linux-kernel@vger.kernel.org>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>,
Kernelnewbies <kernelnewbies@kernelnewbies.org>,
linux-pm@vger.kernel.org
Subject: Re: [IMX] [DRM]: suspend/resume support
Date: Wed, 19 Jun 2019 12:11:50 -0300 [thread overview]
Message-ID: <CAOMZO5BsJWTw0nCeUboam4kuKyCO3N_Ch5ZW8k5Y9KFtQBanhQ@mail.gmail.com> (raw)
In-Reply-To: <CAOuPNLhZhgN26rquLQq9zHBct1QxK-7hXAza0xk-0QooPGYLNw@mail.gmail.com>
On Wed, Jun 19, 2019 at 12:05 PM Pintu Agarwal <pintu.ping@gmail.com> 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.
next prev parent reply other threads:[~2019-06-19 15:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-17 13:49 [IMX] [DRM]: suspend/resume support Pintu Agarwal
2019-06-18 7:01 ` Oliver Neukum
2019-06-18 14:02 ` Fabio Estevam
2019-06-18 14:45 ` Pintu Agarwal
2019-06-18 15:09 ` Fabio Estevam
2019-06-19 13:33 ` Pintu Agarwal
2019-06-19 13:44 ` Fabio Estevam
2019-06-19 15:04 ` Pintu Agarwal
2019-06-19 15:11 ` Fabio Estevam [this message]
2019-06-19 15:29 ` Pintu Agarwal
2019-06-21 15:12 ` Pintu Agarwal
2019-06-21 15:40 ` Fabio Estevam
2019-06-22 8:13 ` Pintu Agarwal
2019-07-01 14:25 ` Pintu Agarwal
2019-07-11 15:29 ` [IMX] [DRM]: help in analyzing clock_summary rate difference Pintu Agarwal
2019-06-19 15:04 ` [IMX] [DRM]: suspend/resume support Greg KH
2019-06-19 15:17 ` Pintu Agarwal
2019-06-19 16:26 ` Valdis Klētnieks
2019-06-21 15:04 ` Pintu Agarwal
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAOMZO5BsJWTw0nCeUboam4kuKyCO3N_Ch5ZW8k5Y9KFtQBanhQ@mail.gmail.com \
--to=festevam@gmail.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pintu.ping@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).