From: Fabio Estevam <festevam@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] imx6-sabresd: Improve the explanation of the fragment file
Date: Sat, 7 Oct 2017 19:04:05 -0300 [thread overview]
Message-ID: <1507413845-11329-1-git-send-email-festevam@gmail.com> (raw)
From: Fabio Estevam <fabio.estevam@nxp.com>
Improve the explanation of the need for using the performance governor.
This problem is specific to mx6sabresd board and the Egalax touchscreen
running a mainline kernel, so make this clear.
Signed-off-by: Fabio Estevam <fabio.estevam@nxp.com>
---
board/freescale/imx6-sabresd/linux_qt5.fragment | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/board/freescale/imx6-sabresd/linux_qt5.fragment b/board/freescale/imx6-sabresd/linux_qt5.fragment
index 5c0505e..ffa5f63 100644
--- a/board/freescale/imx6-sabresd/linux_qt5.fragment
+++ b/board/freescale/imx6-sabresd/linux_qt5.fragment
@@ -1,4 +1,4 @@
-# Currently kernel mainline exhibits issues when running cpufreq as ondemand
-# governor on mx6.
+# Currently mx6sabresd exhibits touchscreen issues when running cpufreq as
+# ondemand governor with a mainline kernel.
# CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND is not set
CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y
--
2.7.4
reply other threads:[~2017-10-07 22:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1507413845-11329-1-git-send-email-festevam@gmail.com \
--to=festevam@gmail.com \
--cc=buildroot@busybox.net \
/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