From: Neil Armstrong <narmstrong@baylibre.com>
To: Kevin Hilman <khilman@baylibre.com>, dri-devel@lists.freedesktop.org
Cc: linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/2] drm/meson: add resume/suspend hooks
Date: Wed, 28 Aug 2019 10:05:57 +0200 [thread overview]
Message-ID: <b8ea00c4-3749-e571-edb6-ae5091b23247@baylibre.com> (raw)
In-Reply-To: <7h5zmixvrz.fsf@baylibre.com>
On 27/08/2019 21:17, Kevin Hilman wrote:
> Neil Armstrong <narmstrong@baylibre.com> writes:
>
>> This serie adds the resume/suspend hooks in the Amlogic Meson VPU main driver
>> and the DW-HDMI Glue driver to correctly save state and disable HW before
>> suspend, and succesfully re-init the HW to recover functionnal display
>> after resume.
>>
>> This serie has been tested on Amlogic G12A based SEI510 board, using
>> the newly accepted VRTC driver and the rtcwake utility.
>
> Tested-by: Kevin Hilman <khilman@baylibre.com>
>
> Tested on my G12A SEI510 board, and I verified that it fixes
> suspend/resume issues previously seen.
>
> Kevin
>
Thanks,
Applying to drm-misc-next (for v5.5), with a typo fix in the first patch commit log:
s/suspens/suspend
Neil
_______________________________________________
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-08-28 8:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-27 9:58 [PATCH 0/2] drm/meson: add resume/suspend hooks Neil Armstrong
2019-08-27 9:58 ` [PATCH 1/2] drm/meson: dw_hdmi: " Neil Armstrong
2019-08-27 9:58 ` [PATCH 2/2] drm/meson: " Neil Armstrong
2019-08-27 16:44 ` [PATCH 0/2] " Daniel Vetter
2019-08-27 19:17 ` Kevin Hilman
2019-08-28 8:05 ` Neil Armstrong [this message]
2019-08-28 15:12 ` Kevin Hilman
2019-08-28 15:14 ` Neil Armstrong
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=b8ea00c4-3749-e571-edb6-ae5091b23247@baylibre.com \
--to=narmstrong@baylibre.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
/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).