This is a multi-part message in MIME format.
--nextPart2752678.blusAEmjoU
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Hi,
I would like to add initial support for (various) Quartz64 devices from Pine64 to the Debian kernel. I've made a patch for it (attached).
Before submitting a MR to the Debian kernel repo, you need to verify whether the change actually achieves what you want to achieve and you'd do that by building a kernel with the patch and test that out on the actual device.
But I don't have a Quartz64 device, so I can't do that myself.
So I'm looking for people who do have such a device and are willing to help me by testing it on an actual Quartz64 device.
Cheers,
Diederik
--nextPart2752678.blusAEmjoU
Content-Disposition: attachment; filename="0001-Add-initial-support-for-Pine64-s-Quartz64-devices.patch"
Content-Transfer-Encoding: 7Bit
Content-Type: text/x-patch; charset="UTF-8"; name="0001-Add-initial-support-for-Pine64-s-Quartz64-devices.patch"
From af034db5cee66c141446ee52d8cce00092b0779d Mon Sep 17 00:00:00 2001
From: Diederik de Haas <
didi.debian@cknow.org>
Date: Sun, 21 Nov 2021 15:47:46 +0100
Subject: [PATCH] Add initial support for Pine64's Quartz64 devices
https://wiki.pine64.org/wiki/Quartz64_Development gives a very good
overview of components needed by Quartz64 devices and their upstreaming
status. In kernel 5.19 most remaining components became part of the
upstream kernel and with 6.0 the corresponding Device Tree parts were
included in Linus' tree.
Many of these components are shared between Model A, Model B, SOQuartz
and the PineNote, so all these devices will be supported.
ROCKCHIP_VOP2 is the Visual Output Processor (VOP) of newer Rockchip SoCs.
The MMC_SDHCI_OF_DWCMSHC is needed for eMMC support.
The MOTORCOMM_PHY is needed for GbE functionality. According to the
driver maintainer it needs to be y instead of m to stop the generic PHY
driver from being loaded before the motorcomm one, as the motorcomm
chip has a zeroed out vendor ID.
Therefor make the driver built-in.
The PCIE_ROCKCHIP_DW_HOST is for PCIe controller support in Rockchip
RK356X SoC's.
PHY_ROCKCHIP_NANENG_COMBO_PHY is needed for Combo PHY support using the
NaNeng IP block. This phy can be used as pcie-phy, usb3-phy, sata-phy or sgmii-phy and is used for PCIe/SATA/USB3.
The SND_SOC_RK817 is for Analog audio and SOC_ROCKCHIP_I2S_TDM is too
for now, but it will get HDMI audio functionality in the future.
---
debian/changelog | 14 ++++++++++++++
debian/config/arm64/config | 7 +++++++
2 files changed, 21 insertions(+)
diff --git a/debian/changelog b/debian/changelog
index a7d304fc9f..cf98874ddd 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,17 @@
+linux (6.0-1~exp2) UNRELEASED; urgency=medium
+
+ [ Diederik de Haas ]
+ * [arm64] drivers/gpu/drm/rockchip: Enable ROCKCHIP_VOP2
+ * [arm64] drivers/mmc/host: Enable MMC_SDHCI_OF_DWCMSHC as module
+ * [arm64] drivers/net/phy: Enable MOTORCOMM_PHY
+ * [arm64] drivers/pci/controller/dwc: Enable PCIE_ROCKCHIP_DW_HOST
+ * [arm64] drivers/phy/rockchip: Enable PHY_ROCKCHIP_NANENG_COMBO_PHY as
+ module
+ * [arm64] sound/soc/codecs: Enable SND_SOC_RK817 as module
+ * [arm64] sound/soc/rockchip: Enable SND_SOC_ROCKCHIP_I2S_TDM as module
+
+ -- Salvatore Bonaccorso <
carnil@debian.org> Mon, 10 Oct 2022 14:11:55 +0200 +
linux (6.0-1~exp1) experimental; urgency=medium
* New upstream release:
https://kernel