From: Fabio Estevam <festevam@gmail.com>
To: Pintu Agarwal <pintu.ping@gmail.com>
Cc: linux-pm@vger.kernel.org,
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>
Subject: Re: [IMX] [DRM]: suspend/resume support
Date: Wed, 19 Jun 2019 10:44:31 -0300 [thread overview]
Message-ID: <CAOMZO5ADK1L5UMM9XZetHvmjTvmvUg99G7VPdeXitgpctGLCkw@mail.gmail.com> (raw)
In-Reply-To: <CAOuPNLjYhkP_kL+q-ZpiDZMMpOHrU88BFBc2agtnCzXt8dihOg@mail.gmail.com>
On Wed, Jun 19, 2019 at 10:33 AM Pintu Agarwal <pintu.ping@gmail.com> wrote:
> You can think that the version I am using right now is almost 4.9 itself.
"almost 4.9" does not help, sorry.
> Upgrading again to higher kernel version is again difficult, also
> customer does not want it.
dw-hdmi is well supported on i.MX6 with mainline, so you could simply try that.
Try booting 5.1.11 on your custom board with a very minimal dts with
HDMI support.
Then you can test suspend/resume and see if HDMI hangs or not.
> Another approach I tried is, installing hdmi {dw-hdmi.ko,
> dw_hdmi-imx.ko} as a module, just after the resume.
> With this also system hangs during installation of dw_hdmi-imx.ko at
> below location:
>
> imx_drm_driver_load(..)
> |
> |--> component_bind_all(...)
> |
> |-> component_bind(ipu)
> |
> |
> ipu_drm_bind(..)
> |
> |-> ipu_crtc_init(..)
> |
> |-> ipu_plane_irq(..)
> |
> | ----> << __HANGS HERE__ >>
I am not able to reproduce this hang. As I mentioned yesterday
suspend/resume is working just fine.
We would be glad to help fixing the hang if you could reproduce it
with a mainline kernel.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-06-19 13:44 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 [this message]
2019-06-19 15:04 ` Pintu Agarwal
2019-06-19 15:11 ` Fabio Estevam
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=CAOMZO5ADK1L5UMM9XZetHvmjTvmvUg99G7VPdeXitgpctGLCkw@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).