From: Neil Armstrong <narmstrong.kernel@gmail.com>
To: "张 宁" <zhangn1985@outlook.com>,
"linux-amlogic@lists.infradead.org"
<linux-amlogic@lists.infradead.org>, Nick <nick@khadas.com>,
"Neil Armstrong" <narmstrong@baylibre.com>
Subject: Re: How to test meson_gx_pm
Date: Mon, 27 Jun 2022 11:39:17 +0200 [thread overview]
Message-ID: <b2c13330-8c03-a08b-19d5-10afc8b28c2c@gmail.com> (raw)
In-Reply-To: <OS0P286MB06419BC49795C5CC383B8D75CDB99@OS0P286MB0641.JPNP286.PROD.OUTLOOK.COM>
Hi,
On 27/06/2022 10:52, 张 宁 wrote:
> Hi, Neil
>
> I understand meson_gx_pm is rejected by upstream[0].
>
> but it's OK to add this driver to personal kernel build or downstream kernel build for GXBB.
>
> as a 6 years old driver, is it still work as expected?
No idea, it should be tested.
> I find this driver has been added to Khadas's mainline linux release for years. but they didn't do tests this driver.
>
> how to test this driver is a problem now.
>
> the driver is for suspend, thus can I use
> "
> # echo mem > /sys/power/state
> "
> from command line?
>
> And how to wakeup device? power key on SBC?
Any wakeup source configured in bl301 code embeded in the FIP bootable binary should work.
Usually Bluetooth & IR are configured in addition to a power key, but the vendor u-boot source
should be checked to confirm.
Neil
>
> BR.
> Ning.
>
>
> [0]: https://lore.kernel.org/lkml/1478183365-23708-1-git-send-email-narmstrong@baylibre.com/
> _______________________________________________
> linux-amlogic mailing list
> linux-amlogic@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-amlogic
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2022-06-27 9:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 8:52 How to test meson_gx_pm 张 宁
2022-06-27 9:39 ` Neil Armstrong [this message]
2022-06-27 13:26 ` 回复: " 张 宁
2022-07-02 7:43 ` 张 宁
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=b2c13330-8c03-a08b-19d5-10afc8b28c2c@gmail.com \
--to=narmstrong.kernel@gmail.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=narmstrong@baylibre.com \
--cc=nick@khadas.com \
--cc=zhangn1985@outlook.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