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: Tue, 18 Jun 2019 12:09:23 -0300 [thread overview]
Message-ID: <CAOMZO5BY8JcLNMCRCC_d=emy8HR6kE=dB9f5qfZ=ci_c+Jak0w@mail.gmail.com> (raw)
In-Reply-To: <CAOuPNLgEEfDca4aeT1+q8GfUfGzbJ4x6JwGf-ROB1pgpXUBHSw@mail.gmail.com>
On Tue, Jun 18, 2019 at 11:46 AM Pintu Agarwal <pintu.ping@gmail.com> wrote:
> Thank you so much for your reply.
> Yes, I already checked the latest mainline kernel changes until 5.2-**.
> I see that there are many cleanup related changes, but still I see
> that suspend/resume functions are missing in dw_hdmi-imx driver.
Please see this recently submitted patch:
https://lore.kernel.org/patchwork/patch/1084057/
> So, I am trying to implement myself.
> Also, I see that suspend/resume is missing even in :
> drivers/gpu/drm/imx/ipuv3-crtc.c
> I am trying this also (not sure if we need this as well).
>
> Can you point out some specific patches which can be helpful ?
>
> Currently, what I observed is that hdmi bind() functions are not getting called.
> Not sure who is responsible for triggering this bind function.
> Or, irq remains disabled after resume, and we need to enable it back
> again (but how ?)
> Or, we may need to enable vblank events and thus irqs can be enabled.
>
> So, I am exploring many possibilities.
> If you have any suggestions please let me know.
The suggestion I have is to try to use latest mainline kernel. If you
see any issues with it, please report.
The combination you mentioned in a prior thread (kernel 3.10 +
backported drm patches 4.9) is not really something the community can
help you.
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2019-06-18 20:53 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 [this message]
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
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='CAOMZO5BY8JcLNMCRCC_d=emy8HR6kE=dB9f5qfZ=ci_c+Jak0w@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).