From: CameronNemo <CameronNemo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] linux5.18: include rk356x related module
Date: Wed, 08 Jun 2022 03:52:00 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37440@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 845 bytes --]
There is a new pull request by CameronNemo against master on the void-packages repository
https://github.com/CameronNemo/void-packages rk356x
https://github.com/void-linux/void-packages/pull/37440
linux5.18: include rk356x related module
I took a couple minutes and reviewed our kconfig compared to what is recommended in the Pine64 wiki.
(<https://wiki.pine64.org/wiki/Quartz64_Development#Linux_Kernel_Config_Options>)
Only one config item was missing.
On ARM64, include the `ROCKCHIP_SARADC` driver which is used by some
rk3566 and rk3568 boards for handling analog microphone input.
[ci skip]
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **NO**
A patch file from https://github.com/void-linux/void-packages/pull/37440.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-rk356x-37440.patch --]
[-- Type: text/x-diff, Size: 944 bytes --]
From abc6ebc848f7aebba8e2a819755648952d477d9d Mon Sep 17 00:00:00 2001
From: Cameron Nemo <cnemo@tutanota.com>
Date: Tue, 7 Jun 2022 18:48:08 -0700
Subject: [PATCH] linux5.18: include rk356x related module
On ARM64, include the ROCKCHIP_SARADC driver which is used by some
rk3566 and rk3568 boards for handling analog microphone input.
---
srcpkgs/linux5.18/files/arm64-dotconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/srcpkgs/linux5.18/files/arm64-dotconfig b/srcpkgs/linux5.18/files/arm64-dotconfig
index 81fbc7918e6c..e19dc7450215 100644
--- a/srcpkgs/linux5.18/files/arm64-dotconfig
+++ b/srcpkgs/linux5.18/files/arm64-dotconfig
@@ -10309,7 +10309,7 @@ CONFIG_QCOM_VADC_COMMON=m
# CONFIG_QCOM_SPMI_IADC is not set
# CONFIG_QCOM_SPMI_VADC is not set
CONFIG_QCOM_SPMI_ADC5=m
-# CONFIG_ROCKCHIP_SARADC is not set
+CONFIG_ROCKCHIP_SARADC=m
CONFIG_SC27XX_ADC=m
CONFIG_SD_ADC_MODULATOR=m
CONFIG_SUN4I_GPADC=m
next reply other threads:[~2022-06-08 1:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 1:52 CameronNemo [this message]
2022-06-14 15:58 ` [PR PATCH] [Merged]: " sgn
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37440@inbox.vuxu.org \
--to=cameronnemo@users.noreply.github.com \
--cc=ml@inbox.vuxu.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).