rpms
/
kernel
2
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Linux v5.10.6 

Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
This commit is contained in:
Justin M. Forbes 2021-01-11 11:52:31 -06:00
parent f045479ce0
commit e18a08842c
309 changed files with 5329 additions and 1295 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

86
0001-ALSA-hda-via-Fix-runtime-PM-for-Clevo-W35xSS.patch Normal file
View File

@ -0,0 +1,86 @@
From 4bfd6247fa9164c8e193a55ef9c0ea3ee22f82d8 Mon Sep 17 00:00:00 2001
From: Takashi Iwai <tiwai@suse.de>
Date: Mon, 4 Jan 2021 16:30:46 +0100
Subject: [PATCH] ALSA: hda/via: Fix runtime PM for Clevo W35xSS
Clevo W35xSS_370SS with VIA codec has had the runtime PM problem that
looses the power state of some nodes after the runtime resume. This
was worked around by disabling the default runtime PM via a denylist
entry. Since 5.10.x made the runtime PM applied (casually) even
though it's disabled in the denylist, this problem was revisited. The
result was that disabling power_save_node feature suffices for the
runtime PM problem.
This patch implements the disablement of power_save_node feature in
VIA codec for the device. It also drops the former denylist entry,
too, as the runtime PM should work in the codec side properly now.
Fixes: b529ef2464ad ("ALSA: hda: Add Clevo W35xSS_370SS to the power_save blacklist")
Reported-by: Christian Labisch <clnetbox@gmail.com>
Cc: <stable@vger.kernel.org>
Link: https://lore.kernel.org/r/20210104153046.19993-1-tiwai@suse.de
Signed-off-by: Takashi Iwai <tiwai@suse.de>
---
sound/pci/hda/hda_intel.c | 2 --
sound/pci/hda/patch_via.c | 13 +++++++++++++
2 files changed, 13 insertions(+), 2 deletions(-)
diff --git a/sound/pci/hda/hda_intel.c b/sound/pci/hda/hda_intel.c
index 6852668f1bcb..770ad25f1907 100644
--- a/sound/pci/hda/hda_intel.c
+++ b/sound/pci/hda/hda_intel.c
@@ -2220,8 +2220,6 @@ static const struct snd_pci_quirk power_save_denylist[] = {
SND_PCI_QUIRK(0x1849, 0x7662, "Asrock H81M-HDS", 0),
/* https://bugzilla.redhat.com/show_bug.cgi?id=1525104 */
SND_PCI_QUIRK(0x1043, 0x8733, "Asus Prime X370-Pro", 0),
- /* https://bugzilla.redhat.com/show_bug.cgi?id=1581607 */
- SND_PCI_QUIRK(0x1558, 0x3501, "Clevo W35xSS_370SS", 0),
/* https://bugzilla.redhat.com/show_bug.cgi?id=1525104 */
SND_PCI_QUIRK(0x1558, 0x6504, "Clevo W65_67SB", 0),
/* https://bugzilla.redhat.com/show_bug.cgi?id=1525104 */
diff --git a/sound/pci/hda/patch_via.c b/sound/pci/hda/patch_via.c
index 7ef8f3105cdb..0ab40a8a68fb 100644
--- a/sound/pci/hda/patch_via.c
+++ b/sound/pci/hda/patch_via.c
@@ -1002,6 +1002,7 @@ static const struct hda_verb vt1802_init_verbs[] = {
enum {
VIA_FIXUP_INTMIC_BOOST,
VIA_FIXUP_ASUS_G75,
+ VIA_FIXUP_POWER_SAVE,
};
static void via_fixup_intmic_boost(struct hda_codec *codec,
@@ -1011,6 +1012,13 @@ static void via_fixup_intmic_boost(struct hda_codec *codec,
override_mic_boost(codec, 0x30, 0, 2, 40);
}
+static void via_fixup_power_save(struct hda_codec *codec,
+ const struct hda_fixup *fix, int action)
+{
+ if (action == HDA_FIXUP_ACT_PRE_PROBE)
+ codec->power_save_node = 0;
+}
+
static const struct hda_fixup via_fixups[] = {
[VIA_FIXUP_INTMIC_BOOST] = {
.type = HDA_FIXUP_FUNC,
@@ -1025,11 +1033,16 @@ static const struct hda_fixup via_fixups[] = {
{ }
}
},
+ [VIA_FIXUP_POWER_SAVE] = {
+ .type = HDA_FIXUP_FUNC,
+ .v.func = via_fixup_power_save,
+ },
};
static const struct snd_pci_quirk vt2002p_fixups[] = {
SND_PCI_QUIRK(0x1043, 0x1487, "Asus G75", VIA_FIXUP_ASUS_G75),
SND_PCI_QUIRK(0x1043, 0x8532, "Asus X202E", VIA_FIXUP_INTMIC_BOOST),
+ SND_PCI_QUIRK(0x1558, 0x3501, "Clevo W35xSS_370SS", VIA_FIXUP_POWER_SAVE),
{}
};
--
2.29.2

11
0001-Drop-that-for-now.patch
View File

@ -4,19 +4,18 @@ Date: Wed, 23 Jan 2019 14:36:37 +0100
Subject: [PATCH] Drop that for now
---
Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Makefile | 1 +
1 file changed, 1 insertion(+)
diff --git a/Makefile b/Makefile
index b70997f7ddf9..680d906eee35 100644
--- a/Makefile
+++ b/Makefile
@@ -498,7 +498,7 @@ KBUILD_AFLAGS := -D__ASSEMBLY__ -fno-PIE
KBUILD_CFLAGS := -Wall -Wundef -Werror=strict-prototypes -Wno-trigraphs \
@@ -496,6 +496,7 @@ KBUILD_CFLAGS := -Wall -Wundef -Werror=strict-prototypes -Wno-trigraphs \
-fno-strict-aliasing -fno-common -fshort-wchar -fno-PIE \
-Werror=implicit-function-declaration -Werror=implicit-int \
- -Wno-format-security \
+ -Wno-format-security -Wno-address-of-packed-member \
-Werror=return-type -Wno-format-security \
+ -Wno-address-of-packed-member \
-std=gnu89
KBUILD_CPPFLAGS := -D__KERNEL__
KBUILD_AFLAGS_KERNEL :=

2
0001-Input-rmi4-remove-the-need-for-artificial-IRQ-in-cas.patch
View File

@ -113,7 +113,7 @@ index 8cffa84c9650..6c4e3675601a 100644
- }
-
if (data->device_flags & RMI_DEVICE_HAS_PHYS_BUTTONS)
rmi_hid_pdata.f30_data.disable = true;
rmi_hid_pdata.gpio_data.disable = true;
data->xport.dev = hdev->dev.parent;
data->xport.pdata = rmi_hid_pdata;

22
0001-PCI-Add-MCFG-quirks-for-Tegra194-host-controllers.patch
View File

@ -1,6 +1,6 @@
From dc7294c776b82b0f0feec1536b2f4676806b4b8a Mon Sep 17 00:00:00 2001
From ec7b5bf1cc1444d9ad13bcef0f0f8d48ff9c0203 Mon Sep 17 00:00:00 2001
From: Peter Robinson <pbrobinson@gmail.com>
Date: Tue, 3 Nov 2020 14:04:29 +0000
Date: Sat, 19 Dec 2020 14:10:40 +0000
Subject: [PATCH] PCI: Add MCFG quirks for Tegra194 host controllers
The PCIe controller in Tegra194 SoC is not completely ECAM-compliant.
@ -29,7 +29,7 @@ Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
5 files changed, 117 insertions(+), 5 deletions(-)
diff --git a/drivers/acpi/pci_mcfg.c b/drivers/acpi/pci_mcfg.c
index 54b36b7ad47d..6573d495d9c1 100644
index 95f23acd5b80..53cab975f612 100644
--- a/drivers/acpi/pci_mcfg.c
+++ b/drivers/acpi/pci_mcfg.c
@@ -116,6 +116,13 @@ static struct mcfg_fixup mcfg_quirks[] = {
@ -47,10 +47,10 @@ index 54b36b7ad47d..6573d495d9c1 100644
{"APM ", "XGENE ", rev, seg, MCFG_BUS_ANY, \
&xgene_v1_pcie_ecam_ops }
diff --git a/drivers/pci/controller/dwc/Kconfig b/drivers/pci/controller/dwc/Kconfig
index 044a3761c44f..e4ee4bf9ac64 100644
index bc049865f8e0..c5d40951a6ad 100644
--- a/drivers/pci/controller/dwc/Kconfig
+++ b/drivers/pci/controller/dwc/Kconfig
@@ -247,25 +247,27 @@ config PCI_MESON
@@ -248,25 +248,27 @@ config PCI_MESON
implement the driver.
config PCIE_TEGRA194
@ -101,7 +101,7 @@ index a751553fa0db..dbb981876556 100644
+obj-$(CONFIG_ARM64) += pcie-tegra194.o
endif
diff --git a/drivers/pci/controller/dwc/pcie-tegra194.c b/drivers/pci/controller/dwc/pcie-tegra194.c
index 70498689d0c0..3db514e1ea7e 100644
index f920e7efe118..87c7929db727 100644
--- a/drivers/pci/controller/dwc/pcie-tegra194.c
+++ b/drivers/pci/controller/dwc/pcie-tegra194.c
@@ -22,6 +22,8 @@
@ -113,7 +113,7 @@ index 70498689d0c0..3db514e1ea7e 100644
#include <linux/phy/phy.h>
#include <linux/pinctrl/consumer.h>
#include <linux/platform_device.h>
@@ -324,6 +326,103 @@ struct tegra_pcie_dw_of_data {
@@ -311,6 +313,103 @@ struct tegra_pcie_dw_of_data {
enum dw_pcie_device_mode mode;
};
@ -217,7 +217,7 @@ index 70498689d0c0..3db514e1ea7e 100644
static inline struct tegra_pcie_dw *to_tegra_pcie(struct dw_pcie *pci)
{
return container_of(pci, struct tegra_pcie_dw, pci);
@@ -2403,3 +2502,6 @@ MODULE_DEVICE_TABLE(of, tegra_pcie_dw_of_match);
@@ -2339,3 +2438,6 @@ MODULE_DEVICE_TABLE(of, tegra_pcie_dw_of_match);
MODULE_AUTHOR("Vidya Sagar <vidyas@nvidia.com>");
MODULE_DESCRIPTION("NVIDIA PCIe host controller driver");
MODULE_LICENSE("GPL v2");
@ -225,10 +225,10 @@ index 70498689d0c0..3db514e1ea7e 100644
+#endif /* CONFIG_PCIE_TEGRA194 */
+
diff --git a/include/linux/pci-ecam.h b/include/linux/pci-ecam.h
index 1af5cb02ef7f..3fb16ada505a 100644
index 033ce74f02e8..ccbf3c38c6e6 100644
--- a/include/linux/pci-ecam.h
+++ b/include/linux/pci-ecam.h
@@ -57,6 +57,7 @@ extern const struct pci_ecam_ops pci_thunder_ecam_ops; /* Cavium ThunderX 1.x */
@@ -58,6 +58,7 @@ extern const struct pci_ecam_ops pci_thunder_ecam_ops; /* Cavium ThunderX 1.x */
extern const struct pci_ecam_ops xgene_v1_pcie_ecam_ops; /* APM X-Gene PCIe v1 */
extern const struct pci_ecam_ops xgene_v2_pcie_ecam_ops; /* APM X-Gene PCIe v2.x */
extern const struct pci_ecam_ops al_pcie_ops; /* Amazon Annapurna Labs PCIe */
@ -237,5 +237,5 @@ index 1af5cb02ef7f..3fb16ada505a 100644
#if IS_ENABLED(CONFIG_PCI_HOST_COMMON)
--
2.28.0
2.29.2

54
0001-drm-nouveau-kms-handle-mDP-connectors.patch Normal file
View File

@ -0,0 +1,54 @@
From 54a080fdc2e65b38aea4dd59dde357d6c340fa25 Mon Sep 17 00:00:00 2001
From: Karol Herbst <kherbst@redhat.com>
Date: Thu, 26 Nov 2020 14:47:50 +0100
Subject: [PATCH] drm/nouveau/kms: handle mDP connectors
In some cases we have the handle those explicitly as the fallback
connector type detection fails and marks those as eDP connectors.
Attempting to use such a connector with mutter leads to a crash of mutter
as it ends up with two eDP displays.
Information is taken from the official DCB documentation.
Upstream Nouveau commit: 95adf381b74e86a8a34b93c3fab73c15dd2f3f5c
Cc: stable@vger.kernel.org
Cc: dri-devel@lists.freedesktop.org
Cc: Ben Skeggs <bskeggs@redhat.com>
Reported-by: Mark Pearson <markpearson@lenovo.com>
Tested-by: Mark Pearson <markpearson@lenovo.com>
Signed-off-by: Karol Herbst <kherbst@redhat.com>
Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
---
drivers/gpu/drm/nouveau/include/nvkm/subdev/bios/conn.h | 1 +
drivers/gpu/drm/nouveau/nouveau_connector.c | 1 +
2 files changed, 2 insertions(+)
diff --git a/drivers/gpu/drm/nouveau/include/nvkm/subdev/bios/conn.h b/drivers/gpu/drm/nouveau/include/nvkm/subdev/bios/conn.h
index f5f59261ea81..d1beaad0c82b 100644
--- a/drivers/gpu/drm/nouveau/include/nvkm/subdev/bios/conn.h
+++ b/drivers/gpu/drm/nouveau/include/nvkm/subdev/bios/conn.h
@@ -14,6 +14,7 @@ enum dcb_connector_type {
DCB_CONNECTOR_LVDS_SPWG = 0x41,
DCB_CONNECTOR_DP = 0x46,
DCB_CONNECTOR_eDP = 0x47,
+ DCB_CONNECTOR_mDP = 0x48,
DCB_CONNECTOR_HDMI_0 = 0x60,
DCB_CONNECTOR_HDMI_1 = 0x61,
DCB_CONNECTOR_HDMI_C = 0x63,
diff --git a/drivers/gpu/drm/nouveau/nouveau_connector.c b/drivers/gpu/drm/nouveau/nouveau_connector.c
index 8b4b3688c7ae..4c992fd5bd68 100644
--- a/drivers/gpu/drm/nouveau/nouveau_connector.c
+++ b/drivers/gpu/drm/nouveau/nouveau_connector.c
@@ -1210,6 +1210,7 @@ drm_conntype_from_dcb(enum dcb_connector_type dcb)
case DCB_CONNECTOR_DMS59_DP0:
case DCB_CONNECTOR_DMS59_DP1:
case DCB_CONNECTOR_DP :
+ case DCB_CONNECTOR_mDP :
case DCB_CONNECTOR_USB_C : return DRM_MODE_CONNECTOR_DisplayPort;
case DCB_CONNECTOR_eDP : return DRM_MODE_CONNECTOR_eDP;
case DCB_CONNECTOR_HDMI_0 :
--
2.29.2

4
0001-efi-Lock-down-the-kernel-if-booted-in-secure-boot-mo.patch
View File

@ -27,8 +27,8 @@ index c9de4b36ca51..a1a012702915 100644
#include <linux/tboot.h>
+#include <linux/security.h>
#include <linux/usb/xhci-dbgp.h>
#include <uapi/linux/mount.h>
#include <linux/static_call.h>
#include <linux/swiotlb.h>
@@ -1104,6 +1105,13 @@ void __init setup_arch(char **cmdline_p)
if (efi_enabled(EFI_BOOT))
efi_init();

2
0001-ipmi-do-not-configure-ipmi-for-HPE-m400.patch
View File

@ -88,9 +88,9 @@ index 737c0b6b24ea..7901e780323b 100644
--- a/drivers/char/ipmi/ipmi_msghandler.c
+++ b/drivers/char/ipmi/ipmi_msghandler.c
@@ -34,6 +34,7 @@
#include <linux/uuid.h>
#include <linux/nospec.h>
#include <linux/vmalloc.h>
#include <linux/delay.h>
+#include <linux/dmi.h>
#define IPMI_DRIVER_VERSION "39.2"

13
0001-update-phy-on-pine64-a64-devices.patch
View File

@ -21,19 +21,6 @@ index 2165f238af13..9741fb5caa6f 100644
phy-handle = <&ext_rmii_phy1>;
phy-supply = <&reg_dc1sw>;
status = "okay";
diff --git a/arch/arm64/boot/dts/allwinner/sun50i-a64-sopine-baseboard.dts b/arch/arm64/boot/dts/allwinner/sun50i-a64-sopine-baseboard.dts
index 2f6ea9f3f6a2..079b10641ccd 100644
--- a/arch/arm64/boot/dts/allwinner/sun50i-a64-sopine-baseboard.dts
+++ b/arch/arm64/boot/dts/allwinner/sun50i-a64-sopine-baseboard.dts
@@ -79,7 +79,7 @@ &ehci1 {
&emac {
pinctrl-names = "default";
pinctrl-0 = <&rgmii_pins>;
- phy-mode = "rgmii";
+ phy-mode = "rgmii-id";
phy-handle = <&ext_rgmii_phy>;
phy-supply = <&reg_dc1sw>;
status = "okay";
--
2.28.0

132
ARM-dts-sun7i-pcduino3-nano-enable-RGMII-RX-TX-delay-on-PHY.patch
View File

@ -1,132 +0,0 @@
From patchwork Sun Oct 25 14:01:44 2020
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
X-Patchwork-Submitter: Adam Sampson <ats@offog.org>
X-Patchwork-Id: 11855267
Return-Path:
<SRS0=8R9C=EA=lists.infradead.org=linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@kernel.org>
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on
aws-us-west-2-korg-lkml-1.web.codeaurora.org
X-Spam-Level:
X-Spam-Status: No, score=-12.8 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH,
DKIM_SIGNED,DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,
MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,
USER_AGENT_GIT autolearn=ham autolearn_force=no version=3.4.0
Received: from mail.kernel.org (mail.kernel.org [198.145.29.99])
by smtp.lore.kernel.org (Postfix) with ESMTP id D1D99C388F7
for <linux-arm-kernel@archiver.kernel.org>;
Sun, 25 Oct 2020 14:04:02 +0000 (UTC)
Received: from merlin.infradead.org (merlin.infradead.org [205.233.59.134])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(No client certificate requested)
by mail.kernel.org (Postfix) with ESMTPS id 539B92225E
for <linux-arm-kernel@archiver.kernel.org>;
Sun, 25 Oct 2020 14:04:02 +0000 (UTC)
Authentication-Results: mail.kernel.org;
dkim=pass (2048-bit key) header.d=lists.infradead.org
header.i=@lists.infradead.org header.b="pKL4zMU1"
DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 539B92225E
Authentication-Results: mail.kernel.org;
dmarc=fail (p=none dis=none) header.from=offog.org
Authentication-Results: mail.kernel.org;
spf=none
smtp.mailfrom=linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;
d=lists.infradead.org; s=merlin.20170209; h=Sender:Content-Transfer-Encoding:
Content-Type:Cc:List-Subscribe:List-Help:List-Post:List-Archive:
List-Unsubscribe:List-Id:MIME-Version:Message-Id:Date:Subject:To:From:
Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender
:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Owner;
bh=Smw7tRUwTAlV9zXVX1uVl3+PN3QebXDyiZrExxBSCPU=; b=pKL4zMU1LMKGyGrnNBuRIJVlPn
yMf8/tMv8w7BT/mMtZkxY22WUlN4IpqNLAx1mdiIa5VUVbVpdsXYWYdSWaUvJe24nyJi8NycxIoO8
168UTytxMlzI5F18yr9bXZ79rSRW+/P0zQbb+OQPMPbJPNb1RusFtve8WGNCkqlOWUOpiVQqPFPJ9
hGhOsDJhXjep7y7HNpu7+UBYvZInmOOrAS079WoEc1jX4u6zDXt0ox24r0Fcc8wnVpsWpGxPhb0xZ
uZtguJOo2ItQdeT/6OfafjzV15qXfPGK+148ny4vyOvgHNvJX88R6RBIxqUdvQzoh10GTlb76K45i
Gfx5ufkA==;
Received: from localhost ([::1] helo=merlin.infradead.org)
by merlin.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux))
id 1kWgb2-0000uB-6w; Sun, 25 Oct 2020 14:02:08 +0000
Received: from a-painless.mh.aa.net.uk ([2001:8b0:0:30::51]
helo=alt.a-painless.mh.aa.net.uk)
by merlin.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux))
id 1kWgaz-0000tq-Kq
for linux-arm-kernel@lists.infradead.org; Sun, 25 Oct 2020 14:02:06 +0000
Received: from cartman.offog.org ([2001:8b0:83b:b53f::a])
by a-painless.mh.aa.net.uk with esmtps
(TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92)
(envelope-from <ats@offog.org>)
id 1kWgay-0001oV-R0; Sun, 25 Oct 2020 14:02:04 +0000
Received: from ats by cartman.offog.org with local (Exim 4.94)
(envelope-from <ats@offog.org>)
id 1kWgao-0007UQ-4s; Sun, 25 Oct 2020 14:01:54 +0000
From: Adam Sampson <ats@offog.org>
To: linux-sunxi@googlegroups.com, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: sun7i: pcduino3-nano: enable RGMII RX/TX delay on
PHY
Date: Sun, 25 Oct 2020 14:01:44 +0000
Message-Id: <20201025140144.28693-1-ats@offog.org>
X-Mailer: git-send-email 2.29.1
MIME-Version: 1.0
X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3
X-CRM114-CacheID: sfid-20201025_100205_812453_7FAF68C8
X-CRM114-Status: GOOD ( 13.85 )
X-BeenThere: linux-arm-kernel@lists.infradead.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <linux-arm-kernel.lists.infradead.org>
List-Unsubscribe:
<http://lists.infradead.org/mailman/options/linux-arm-kernel>,
<mailto:linux-arm-kernel-request@lists.infradead.org?subject=unsubscribe>
List-Archive: <http://lists.infradead.org/pipermail/linux-arm-kernel/>
List-Post: <mailto:linux-arm-kernel@lists.infradead.org>
List-Help: <mailto:linux-arm-kernel-request@lists.infradead.org?subject=help>
List-Subscribe:
<http://lists.infradead.org/mailman/listinfo/linux-arm-kernel>,
<mailto:linux-arm-kernel-request@lists.infradead.org?subject=subscribe>
Cc: Adam Sampson <ats@offog.org>
Sender: "linux-arm-kernel" <linux-arm-kernel-bounces@lists.infradead.org>
Errors-To:
linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org
The RX/TX delays for the Ethernet PHY on the Linksprite pcDuino 3 Nano
are configured in hardware, using resistors that are populated to pull
the RTL8211E's RXDLY/TXDLY pins low or high as needed.
phy-mode should be set to rgmii-id to reflect this. Previously it was
set to rgmii, which used to work but now results in the delays being
disabled again as a result of the bugfix in commit bbc4d71d6354 ("net:
phy: realtek: fix rtl8211e rx/tx delay config").
Tested on two pcDuino 3 Nano boards purchased in 2015. Without this fix,
Ethernet works unreliably on one board and doesn't work at all on the
other.
Fixes: 061035d456c9 ("ARM: dts: sun7i: Add dts file for pcDuino 3 Nano board")
Signed-off-by: Adam Sampson <ats@offog.org>
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
---
arch/arm/boot/dts/sun7i-a20-pcduino3-nano.dts | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm/boot/dts/sun7i-a20-pcduino3-nano.dts b/arch/arm/boot/dts/sun7i-a20-pcduino3-nano.dts
index fce2f7fcd084..bf38c66c1815 100644
--- a/arch/arm/boot/dts/sun7i-a20-pcduino3-nano.dts
+++ b/arch/arm/boot/dts/sun7i-a20-pcduino3-nano.dts
@@ -1,5 +1,5 @@
/*
- * Copyright 2015 Adam Sampson <ats@offog.org>
+ * Copyright 2015-2020 Adam Sampson <ats@offog.org>
*
* This file is dual-licensed: you can use it either under the terms
* of the GPL or the X11 license, at your option. Note that this dual
@@ -115,7 +115,7 @@ &gmac {
pinctrl-names = "default";
pinctrl-0 = <&gmac_rgmii_pins>;
phy-handle = <&phy1>;
- phy-mode = "rgmii";
+ phy-mode = "rgmii-id";
status = "okay";
};

64
arm-pandaboard-fix-add-bluetooth.patch Normal file
View File

@ -0,0 +1,64 @@
From b86516452cfd94321900abe7c8ac843c146a8c53 Mon Sep 17 00:00:00 2001
From: "H. Nikolaus Schaller" <hns@goldelico.com>
Date: Sat, 3 Oct 2020 16:10:01 +0200
Subject: ARM: dts: pandaboard es: add bluetooth uart for HCI
The wl271 bluetooth uart is connected to uart2.
Setup a serdev uart child and separate bluetooth and uart2 pinmux
from wl12xx pinmux to better group the pins and muxes.
Signed-off-by: H. Nikolaus Schaller <hns@goldelico.com>
Signed-off-by: Tony Lindgren <tony@atomide.com>
---
arch/arm/boot/dts/omap4-panda-es.dts | 32 ++++++++++++++++++++++++++++++++
1 file changed, 32 insertions(+)
diff --git a/arch/arm/boot/dts/omap4-panda-es.dts b/arch/arm/boot/dts/omap4-panda-es.dts
index 6afa8fd7c412d..7c6886cd738f0 100644
--- a/arch/arm/boot/dts/omap4-panda-es.dts
+++ b/arch/arm/boot/dts/omap4-panda-es.dts
@@ -49,6 +49,22 @@
OMAP4_IOPAD(0x0fc, PIN_INPUT_PULLUP | MUX_MODE3) /* gpio_113 */
>;
};
+
+ bt_pins: pinmux_bt_pins {
+ pinctrl-single,pins = <
+ OMAP4_IOPAD(0x06c, PIN_OUTPUT | MUX_MODE3) /* gpmc_a22.gpio_46 - BTEN */
+ OMAP4_IOPAD(0x072, PIN_OUTPUT_PULLUP | MUX_MODE3) /* gpmc_a25.gpio_49 - BTWAKEUP */
+ >;
+ };
+
+ uart2_pins: pinmux_uart2_pins {
+ pinctrl-single,pins = <
+ OMAP4_IOPAD(0x118, PIN_INPUT_PULLUP | MUX_MODE0) /* uart2_cts.uart2_cts - HCI */
+ OMAP4_IOPAD(0x11a, PIN_OUTPUT | MUX_MODE0) /* uart2_rts.uart2_rts */
+ OMAP4_IOPAD(0x11c, PIN_INPUT_PULLUP | MUX_MODE0) /* uart2_rx.uart2_rx */
+ OMAP4_IOPAD(0x11e, PIN_OUTPUT | MUX_MODE0) /* uart2_tx.uart2_tx */
+ >;
+ };
};
&led_wkgpio_pins {
@@ -80,3 +96,19 @@
&gpio1_target {
ti,no-reset-on-init;
};
+
+&wl12xx_gpio {
+ pinctrl-single,pins = <
+ OMAP4_IOPAD(0x066, PIN_OUTPUT | MUX_MODE3) /* gpmc_a19.gpio_43 */
+ OMAP4_IOPAD(0x070, PIN_OUTPUT_PULLUP | MUX_MODE3) /* gpmc_a24.gpio_48 */
+ >;
+};
+
+&uart2 {
+ pinctrl-names = "default";
+ pinctrl-0 = <&uart2_pins &bt_pins>;
+ bluetooth: tiwi {
+ compatible = "ti,wl1271-st";
+ enable-gpios = <&gpio2 14 GPIO_ACTIVE_HIGH>; /* GPIO_46 */
+ };
+};
--
cgit 1.2.3-1.el7

48
arm64-tegra-Use-valid-PWM-period-for-VDD_GPU-on-Tegra210.patch
View File

@ -1,48 +0,0 @@
From a267434b15bc06c72708327fb1110bf565577a15 Mon Sep 17 00:00:00 2001
From: Peter Robinson <pbrobinson@gmail.com>
Date: Tue, 3 Nov 2020 16:53:02 +0000
Subject: [PATCH] arm64: tegra: Use valid PWM period for VDD_GPU on Tegra210
From: Thierry Reding <treding@nvidia.com>
The PWM on Tegra210 can run at a maximum frequency of 48 MHz and cannot
reach the minimum period is 5334 ns. The currently configured period of
4880 ns is not within the valid range, so set it to 8000 ns. This value
was taken from the downstream DTS files and seems to work fine.
Signed-off-by: Thierry Reding <treding@nvidia.com>
Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
---
arch/arm64/boot/dts/nvidia/tegra210-p2180.dtsi | 2 +-
arch/arm64/boot/dts/nvidia/tegra210-p3450-0000.dts | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm64/boot/dts/nvidia/tegra210-p2180.dtsi b/arch/arm64/boot/dts/nvidia/tegra210-p2180.dtsi
index 6a4b50aaa25d..85ee7e6b71ac 100644
--- a/arch/arm64/boot/dts/nvidia/tegra210-p2180.dtsi
+++ b/arch/arm64/boot/dts/nvidia/tegra210-p2180.dtsi
@@ -337,7 +337,7 @@ psci {
vdd_gpu: regulator@100 {
compatible = "pwm-regulator";
- pwms = <&pwm 1 4880>;
+ pwms = <&pwm 1 8000>;
regulator-name = "VDD_GPU";
regulator-min-microvolt = <710000>;
regulator-max-microvolt = <1320000>;
diff --git a/arch/arm64/boot/dts/nvidia/tegra210-p3450-0000.dts b/arch/arm64/boot/dts/nvidia/tegra210-p3450-0000.dts
index 2282ea1c6279..195a43e2356b 100644
--- a/arch/arm64/boot/dts/nvidia/tegra210-p3450-0000.dts
+++ b/arch/arm64/boot/dts/nvidia/tegra210-p3450-0000.dts
@@ -818,7 +818,7 @@ vdd_cpu: regulator@5 {
vdd_gpu: regulator@6 {
compatible = "pwm-regulator";
- pwms = <&pwm 1 4880>;
+ pwms = <&pwm 1 8000>;
regulator-name = "VDD_GPU";
regulator-min-microvolt = <710000>;
--
2.28.0

75
bluetooth-fix-LL-privacy-BLE-device-fails-to-connect.patch
View File

@ -1,75 +0,0 @@
From MAILER-DAEMON Thu Nov 12 18:45:00 2020
From: Sathish Narasimman <nsathish41@gmail.com>
To: linux-bluetooth@vger.kernel.org
Cc: chethan.tumkur.narayan@intel.com, ravishankar.srivatsa@intel.com, kiran.k@intel.com, Sathish Narasimman <sathish.narasimman@intel.com>
Subject: [PATCH] Bluetooth: Fix: LL PRivacy BLE device fails to connect
Date: Thu, 22 Oct 2020 13:53:04 +0530
Message-Id: <20201022082304.31757-1-sathish.narasimman@intel.com>
List-ID: <linux-bluetooth.vger.kernel.org>
X-Mailing-List: linux-bluetooth@vger.kernel.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
When adding device to white list the device is added to resolving list
also it has to be added only when HCI_ENABLE_LL_PRIVACY flag is set.
HCI_ENABLE_LL_PRIVACY flag has to be tested before adding/deleting devices
to resolving list. use_ll_privacy macro is used only to check if controller
supports LL_Privacy.
https://bugzilla.kernel.org/show_bug.cgi?id=209745
Signed-off-by: Sathish Narasimman <sathish.narasimman@intel.com>
Reviewed-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
---
net/bluetooth/hci_request.c | 12 ++++++++----
1 file changed, 8 insertions(+), 4 deletions(-)
diff --git a/net/bluetooth/hci_request.c b/net/bluetooth/hci_request.c
index 6f12bab4d2fa..610ed0817bd7 100644
--- a/net/bluetooth/hci_request.c
+++ b/net/bluetooth/hci_request.c
@@ -698,7 +698,8 @@ static void del_from_white_list(struct hci_request *req, bdaddr_t *bdaddr,
cp.bdaddr_type);
hci_req_add(req, HCI_OP_LE_DEL_FROM_WHITE_LIST, sizeof(cp), &cp);
- if (use_ll_privacy(req->hdev)) {
+ if (use_ll_privacy(req->hdev) &&
+ hci_dev_test_flag(req->hdev, HCI_ENABLE_LL_PRIVACY)) {
struct smp_irk *irk;
irk = hci_find_irk_by_addr(req->hdev, bdaddr, bdaddr_type);
@@ -732,7 +733,8 @@ static int add_to_white_list(struct hci_request *req,
return -1;
/* White list can not be used with RPAs */
- if (!allow_rpa && !use_ll_privacy(hdev) &&
+ if (!allow_rpa &&
+ !hci_dev_test_flag(hdev, HCI_ENABLE_LL_PRIVACY) &&
hci_find_irk_by_addr(hdev, &params->addr, params->addr_type)) {
return -1;
}
@@ -750,7 +752,8 @@ static int add_to_white_list(struct hci_request *req,
cp.bdaddr_type);
hci_req_add(req, HCI_OP_LE_ADD_TO_WHITE_LIST, sizeof(cp), &cp);
- if (use_ll_privacy(hdev)) {
+ if (use_ll_privacy(hdev) &&
+ hci_dev_test_flag(hdev, HCI_ENABLE_LL_PRIVACY)) {
struct smp_irk *irk;
irk = hci_find_irk_by_addr(hdev, &params->addr,
@@ -812,7 +815,8 @@ static u8 update_white_list(struct hci_request *req)
}
/* White list can not be used with RPAs */
- if (!allow_rpa && !use_ll_privacy(hdev) &&
+ if (!allow_rpa &&
+ !hci_dev_test_flag(hdev, HCI_ENABLE_LL_PRIVACY) &&
hci_find_irk_by_addr(hdev, &b->bdaddr, b->bdaddr_type)) {
return 0x00;
}
--
2.17.1

254
brcmfmac-BCM4329-Fixes-and-improvement.patch
View File

@ -1,254 +0,0 @@
From patchwork Sun Aug 30 19:14:38 2020
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
X-Patchwork-Submitter: Dmitry Osipenko <digetx@gmail.com>
X-Patchwork-Id: 11745287
X-Patchwork-Delegate: kvalo@adurom.com
Return-Path: <SRS0=8jSp=CI=vger.kernel.org=linux-wireless-owner@kernel.org>
Received: from mail.kernel.org (pdx-korg-mail-1.web.codeaurora.org
[172.30.200.123])
by pdx-korg-patchwork-2.web.codeaurora.org (Postfix) with ESMTP id 8D83D722
for <patchwork-linux-wireless@patchwork.kernel.org>;
Sun, 30 Aug 2020 19:18:07 +0000 (UTC)
Received: from vger.kernel.org (vger.kernel.org [23.128.96.18])
by mail.kernel.org (Postfix) with ESMTP id 74984206F0
for <patchwork-linux-wireless@patchwork.kernel.org>;
Sun, 30 Aug 2020 19:18:07 +0000 (UTC)
Authentication-Results: mail.kernel.org;
dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com
header.b="nVMf6eR/"
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
id S1727940AbgH3TRr (ORCPT
<rfc822;patchwork-linux-wireless@patchwork.kernel.org>);
Sun, 30 Aug 2020 15:17:47 -0400
Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36384 "EHLO
lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
with ESMTP id S1726350AbgH3TPI (ORCPT
<rfc822;linux-wireless@vger.kernel.org>);
Sun, 30 Aug 2020 15:15:08 -0400
Received: from mail-lf1-x141.google.com (mail-lf1-x141.google.com
[IPv6:2a00:1450:4864:20::141])
by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 6E897C061236;
Sun, 30 Aug 2020 12:15:07 -0700 (PDT)
Received: by mail-lf1-x141.google.com with SMTP id j15so2315573lfg.7;
Sun, 30 Aug 2020 12:15:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=20161025;
h=from:to:cc:subject:date:message-id:in-reply-to:references
:mime-version:content-transfer-encoding;
bh=85fBH067dHvKQNq6ek+W6lpUInMb+ZStwZLTCqTuQ3g=;
b=nVMf6eR/tzJR9bU6YV5ktJWXhIRVVdwtYx5dR5sOF9HNUZJR1lw0R2eZ5yKGcbs3Ij
UCrio8mvGQhynAaPTXjMhm57mDu723ApUr0TiZXjmUoJrFQVIFl6VYZeCDu3dXXFGUw0
XasSLQZ6ak9UxEk4Xen3Q2U/Zr/P+/jB0QY1vR+MRsiIFzZXwQRQpM9IJzj4yIYopB5X
9XhWNhf2QWh9gH61eTumnKsNzptLg/c8atZt15ncup5uu1C2f/rwt/4dav6jO2dmbGAs
p9NeFTAyGXpQxrzCtfDUCTXvmsS6UEY3o15iWQaZopVbo0ypnts/6Vg8upR1VNQVxnM7
E7Zw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to
:references:mime-version:content-transfer-encoding;
bh=85fBH067dHvKQNq6ek+W6lpUInMb+ZStwZLTCqTuQ3g=;
b=WwmOJDBXyk7Su9lj9yFvo0X22q549x/nNNUuUYCmUf8OjvUL6LwAkcQ7l+F6X41BtP
n1fYqGH6S7w68U3pIL2yyzR7YOl1NDYvZp3LRNGc6Y0dljwZbMMrbTXkdnimwrVneXLQ
CLjOSIYQkJgtWX9ZG/Uaq+hnaY7BX9EMntr7mXYbD+O8Xmr8/Zb/jUJSKiKIxAVW48JM
z2B7XRLEfmd8ELQoMhqtCw/23wbQ6tnT5tdtt+ngDJWh7aXnUaVgO8i/tQf0Th3JXBdj
dB5/P8FDMKrLNwxVYaaHyo/vs86AeUzj+J7Vu+jSQYbWobKSsN0h9FsVwsoEzud1cPlw
s9Tg==
X-Gm-Message-State: AOAM531EgBgv8kHi8OlvBWwXAThNCUT/1OO1iu8iU00rAeqI5Tb40pod
ZyIrbVjNZJe6MgLKqLMeZrw=
X-Google-Smtp-Source:
ABdhPJzI4lUuYNLpOO2XLO2AmkS9fShcfxSPyVOk6XVuyEYlvT5tmtBLoLVIApzOMF3Luuy0a5TW7Q==
X-Received: by 2002:ac2:5e2c:: with SMTP id o12mr3918764lfg.71.1598814905875;
Sun, 30 Aug 2020 12:15:05 -0700 (PDT)
Received: from localhost.localdomain (109-252-170-211.dynamic.spd-mgts.ru.
[109.252.170.211])
by smtp.gmail.com with ESMTPSA id
e23sm1409709lfj.80.2020.08.30.12.15.04
(version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256);
Sun, 30 Aug 2020 12:15:05 -0700 (PDT)
From: Dmitry Osipenko <digetx@gmail.com>
To: Arend van Spriel <arend.vanspriel@broadcom.com>,
Franky Lin <franky.lin@broadcom.com>,
Hante Meuleman <hante.meuleman@broadcom.com>,
Chi-Hsien Lin <chi-hsien.lin@cypress.com>,
Wright Feng <wright.feng@cypress.com>,
Kalle Valo <kvalo@codeaurora.org>
Cc: linux-wireless@vger.kernel.org,
brcm80211-dev-list.pdl@broadcom.com,
brcm80211-dev-list@cypress.com, netdev@vger.kernel.org,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v3 2/3] brcmfmac: drop chip id from debug messages
Date: Sun, 30 Aug 2020 22:14:38 +0300
Message-Id: <20200830191439.10017-3-digetx@gmail.com>
X-Mailer: git-send-email 2.27.0
In-Reply-To: <20200830191439.10017-1-digetx@gmail.com>
References: <20200830191439.10017-1-digetx@gmail.com>
MIME-Version: 1.0
Sender: linux-wireless-owner@vger.kernel.org
Precedence: bulk
List-ID: <linux-wireless.vger.kernel.org>
X-Mailing-List: linux-wireless@vger.kernel.org
The chip ID was already printed out at the time when debug message about
the changed F2 watermark is printed, hence let's drop the unnecessary part
of the debug messages. This cleans code a tad and also allows to re-use
the F2 watermark debug messages by multiple chips.
Suggested-by: Arend van Spriel <arend.vanspriel@broadcom.com>
Signed-off-by: Dmitry Osipenko <digetx@gmail.com>
---
drivers/net/wireless/broadcom/brcm80211/brcmfmac/sdio.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/sdio.c b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/sdio.c
index b16944a898f9..d4989e0cd7be 100644
--- a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/sdio.c
+++ b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/sdio.c
@@ -4280,7 +4280,7 @@ static void brcmf_sdio_firmware_callback(struct device *dev, int err,
break;
case SDIO_DEVICE_ID_BROADCOM_4329:
case SDIO_DEVICE_ID_BROADCOM_4339:
- brcmf_dbg(INFO, "set F2 watermark to 0x%x*4 bytes for 4339\n",
+ brcmf_dbg(INFO, "set F2 watermark to 0x%x*4 bytes\n",
CY_4339_F2_WATERMARK);
brcmf_sdiod_writeb(sdiod, SBSDIO_WATERMARK,
CY_4339_F2_WATERMARK, &err);
@@ -4293,7 +4293,7 @@ static void brcmf_sdio_firmware_callback(struct device *dev, int err,
CY_4339_MESBUSYCTRL, &err);
break;
case SDIO_DEVICE_ID_BROADCOM_43455:
- brcmf_dbg(INFO, "set F2 watermark to 0x%x*4 bytes for 43455\n",
+ brcmf_dbg(INFO, "set F2 watermark to 0x%x*4 bytes\n",
CY_43455_F2_WATERMARK);
brcmf_sdiod_writeb(sdiod, SBSDIO_WATERMARK,
CY_43455_F2_WATERMARK, &err);
From patchwork Sun Aug 30 19:14:39 2020
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
X-Patchwork-Submitter: Dmitry Osipenko <digetx@gmail.com>
X-Patchwork-Id: 11745291
X-Patchwork-Delegate: kvalo@adurom.com
Return-Path: <SRS0=8jSp=CI=vger.kernel.org=linux-wireless-owner@kernel.org>
Received: from mail.kernel.org (pdx-korg-mail-1.web.codeaurora.org
[172.30.200.123])
by pdx-korg-patchwork-2.web.codeaurora.org (Postfix) with ESMTP id BC61D722
for <patchwork-linux-wireless@patchwork.kernel.org>;
Sun, 30 Aug 2020 19:18:14 +0000 (UTC)
Received: from vger.kernel.org (vger.kernel.org [23.128.96.18])
by mail.kernel.org (Postfix) with ESMTP id A440D20757
for <patchwork-linux-wireless@patchwork.kernel.org>;
Sun, 30 Aug 2020 19:18:14 +0000 (UTC)
Authentication-Results: mail.kernel.org;
dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com
header.b="ADD6Kq4a"
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
id S1727902AbgH3TRq (ORCPT
<rfc822;patchwork-linux-wireless@patchwork.kernel.org>);
Sun, 30 Aug 2020 15:17:46 -0400
Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36392 "EHLO
lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
with ESMTP id S1726380AbgH3TPJ (ORCPT
<rfc822;linux-wireless@vger.kernel.org>);
Sun, 30 Aug 2020 15:15:09 -0400
Received: from mail-lf1-x142.google.com (mail-lf1-x142.google.com
[IPv6:2a00:1450:4864:20::142])
by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 6439FC061239;
Sun, 30 Aug 2020 12:15:08 -0700 (PDT)
Received: by mail-lf1-x142.google.com with SMTP id j15so2315593lfg.7;
Sun, 30 Aug 2020 12:15:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=20161025;
h=from:to:cc:subject:date:message-id:in-reply-to:references
:mime-version:content-transfer-encoding;
bh=WKk6KWPNkMHUCww/FbErLxUYYQtEUh3n/PTtmJB/IIQ=;
b=ADD6Kq4arZJOO7Z+X6dlbNFUKa2MGhu79OcOljRz3WAcc/N3H23SdadMXUusZl7Re7
mavcADGOOGjw4YPLh4Bd3AHe3Wf3GrR9xszVDjKeNWBVzpgfPFpbu+G5v/ZCc1IocLez
Tml2HhWF++QwC8/gg0QSMJMYiVTHYrz7Mfq31KkwcMzdX/uXIwpZBuRtIx3Vf6OfTE4I
gSfTcZ6mcSbFla2yJur9lviMamt/2uiHZG0/UTLDqfDQ0fXciUFWXW/wU1YYVwLxynkp
32H0oWWSihfW4LFt7gufNGgSOCh6YMorVxHCY3+a2JagEhMaXuLn853leokAN8VD3nsO
IjnQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to
:references:mime-version:content-transfer-encoding;
bh=WKk6KWPNkMHUCww/FbErLxUYYQtEUh3n/PTtmJB/IIQ=;
b=P70ZXffe7IiriynRgLFOrgujg3zCp+qiQV2DtraBUnPXzHbxNDRH7MnRX8RyYwJZs7
MDwZwyOsryxbtpv/1lQfakB0pFKDzMAqpRhxIc4amXyIBz2g4uoZIDStNSODVhXtjG5H
h4uPuSz9neHI7vO4/7Yp1kvBCS29fbXLIKIFGR4QrwqWxGuaMhNyeXs2Eb3K/jkyfDjn
1HVDqw+yW5WX2R5Rq7xkjw05AMrqSVvecbX+WV/ksoCgYd3N9bS52B0rBA3Qd6uOADTj
82vYn1zNANhjSnTRMC0hOTZmzmnqZsyksYdQrpbyEsdpHaKbB6GkX7ylp3TM9XDpD9xK
+ROQ==
X-Gm-Message-State: AOAM532osjv7Nw1P0/HRBwzPySBJZh+vqXrZj/Ko6Yzt0eyt2qeOFDG3
JOT89QLhVftNg53aBYKa2p4=
X-Google-Smtp-Source:
ABdhPJzL0Cdo7AKGH5FiC2AREv1bSdtUCg+BEl1uu43NLTd1wRmGMfv3vj1BvcduUPeX7jN48VJ+7Q==
X-Received: by 2002:ac2:41cc:: with SMTP id d12mr4018561lfi.20.1598814906867;
Sun, 30 Aug 2020 12:15:06 -0700 (PDT)
Received: from localhost.localdomain (109-252-170-211.dynamic.spd-mgts.ru.
[109.252.170.211])
by smtp.gmail.com with ESMTPSA id
e23sm1409709lfj.80.2020.08.30.12.15.05
(version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256);
Sun, 30 Aug 2020 12:15:06 -0700 (PDT)
From: Dmitry Osipenko <digetx@gmail.com>
To: Arend van Spriel <arend.vanspriel@broadcom.com>,
Franky Lin <franky.lin@broadcom.com>,
Hante Meuleman <hante.meuleman@broadcom.com>,
Chi-Hsien Lin <chi-hsien.lin@cypress.com>,
Wright Feng <wright.feng@cypress.com>,
Kalle Valo <kvalo@codeaurora.org>
Cc: linux-wireless@vger.kernel.org,
brcm80211-dev-list.pdl@broadcom.com,
brcm80211-dev-list@cypress.com, netdev@vger.kernel.org,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v3 3/3] brcmfmac: set F2 SDIO block size to 128 bytes for
BCM4329
Date: Sun, 30 Aug 2020 22:14:39 +0300
Message-Id: <20200830191439.10017-4-digetx@gmail.com>
X-Mailer: git-send-email 2.27.0
In-Reply-To: <20200830191439.10017-1-digetx@gmail.com>
References: <20200830191439.10017-1-digetx@gmail.com>
MIME-Version: 1.0
Sender: linux-wireless-owner@vger.kernel.org
Precedence: bulk
List-ID: <linux-wireless.vger.kernel.org>
X-Mailing-List: linux-wireless@vger.kernel.org
Setting F2 block size to 128 bytes for BCM4329 allows to significantly
improve RX throughput on NVIDIA Tegra20. Before this change the throughput
was capped to 30 Mbit/s on Tegra, now throughput is at 40 Mbit/s, which is
a maximum throughput for the BCM4329 chip. The F2 block size is borrowed
from the downstream BCMDHD driver. The comment in the BCMDHD driver says
that 128B improves throughput and turns out that it works for the brcmfmac
as well.
Signed-off-by: Dmitry Osipenko <digetx@gmail.com>
---
drivers/net/wireless/broadcom/brcm80211/brcmfmac/bcmsdh.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/bcmsdh.c b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/bcmsdh.c
index 0dc4de2fa9f6..318bd00bf94f 100644
--- a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/bcmsdh.c
+++ b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/bcmsdh.c
@@ -45,6 +45,7 @@
#define SDIO_FUNC2_BLOCKSIZE 512
#define SDIO_4373_FUNC2_BLOCKSIZE 256
#define SDIO_435X_FUNC2_BLOCKSIZE 256
+#define SDIO_4329_FUNC2_BLOCKSIZE 128
/* Maximum milliseconds to wait for F2 to come up */
#define SDIO_WAIT_F2RDY 3000
@@ -920,6 +921,9 @@ int brcmf_sdiod_probe(struct brcmf_sdio_dev *sdiodev)
case SDIO_DEVICE_ID_BROADCOM_4356:
f2_blksz = SDIO_435X_FUNC2_BLOCKSIZE;
break;
+ case SDIO_DEVICE_ID_BROADCOM_4329:
+ f2_blksz = SDIO_4329_FUNC2_BLOCKSIZE;
+ break;
default:
break;
}

24
configs/fedora/generic/CONFIG_ACPI_DPTF Normal file
View File

@ -0,0 +1,24 @@
# CONFIG_ACPI_DPTF:
#
# Intel Dynamic Platform and Thermal Framework (DPTF) is a platform
# level hardware/software solution for power and thermal management.
#
# As a container for multiple power/thermal technologies, DPTF provides
# a coordinated approach for different policies to effect the hardware
# state of a system.
#
# For more information see:
# <https://01.org/intel%C2%AE-dynamic-platform-and-thermal-framework-dptf-chromium-os/overview>
#
# Symbol: ACPI_DPTF [=n]
# Type : bool
# Defined at drivers/acpi/dptf/Kconfig:3
# Prompt: Intel DPTF (Dynamic Platform and Thermal Framework) Support
# Depends on: ACPI [=y] && X86 [=y]
# Location:
# -> Power management and ACPI options
# -> ACPI (Advanced Configuration and Power Interface) Support (ACPI [=y])
#
#
#
# CONFIG_ACPI_DPTF is not set

18
configs/fedora/generic/CONFIG_ACPI_TABLE_UPGRADE
View File

@ -1 +1,19 @@
# CONFIG_ACPI_TABLE_UPGRADE:
#
# This option provides functionality to upgrade arbitrary ACPI tables
# via initrd. No functional change if no ACPI tables are passed via
# initrd, therefore it's safe to say Y.
# See Documentation/admin-guide/acpi/initrd_table_override.rst for details
#
# Symbol: ACPI_TABLE_UPGRADE [=y]
# Type : bool
# Defined at drivers/acpi/Kconfig:349
# Prompt: Allow upgrading ACPI tables via initrd
# Depends on: ACPI [=y] && BLK_DEV_INITRD [=y] && ARCH_HAS_ACPI_TABLE_UPGRADE [=y]
# Location:
# -> Power management and ACPI options
# -> ACPI (Advanced Configuration and Power Interface) Support (ACPI [=y])
#
#
#
CONFIG_ACPI_TABLE_UPGRADE=y

22
configs/fedora/generic/CONFIG_ADXRS290 Normal file
View File

@ -0,0 +1,22 @@
# CONFIG_ADXRS290:
#
# Say yes here to build support for Analog Devices ADXRS290 programmable
# digital output gyroscope.
#
# This driver can also be built as a module. If so, the module will be
# called adxrs290.
#
# Symbol: ADXRS290 [=n]
# Type : tristate
# Defined at drivers/iio/gyro/Kconfig:44
# Prompt: Analog Devices ADXRS290 Dual-Axis MEMS Gyroscope SPI driver
# Depends on: IIO [=m] && SPI [=y]
# Location:
# -> Device Drivers
# -> Industrial I/O support (IIO [=m])
# -> Digital gyroscope sensors
# Selects: IIO_BUFFER [=y] && IIO_TRIGGERED_BUFFER [=m]
#
#
#
CONFIG_ADXRS290=m

15
configs/fedora/generic/CONFIG_ARCH_VISCONTI Normal file
View File

@ -0,0 +1,15 @@
# CONFIG_ARCH_VISCONTI:
#
# This enables support for Toshiba Visconti SoCs Family.
#
# Symbol: ARCH_VISCONTI [=n]
# Type : bool
# Defined at arch/arm64/Kconfig.platforms:302
# Prompt: Toshiba Visconti SoC Family
# Location:
# -> Platform selection
# Selects: PINCTRL [=y] && PINCTRL_VISCONTI [=n]
#
#
#
# CONFIG_ARCH_VISCONTI is not set

29
configs/fedora/generic/CONFIG_ARM64_ERRATUM_1508412 Normal file
View File

@ -0,0 +1,29 @@
# CONFIG_ARM64_ERRATUM_1508412:
#
# This option adds a workaround for Arm Cortex-A77 erratum 1508412.
#
# Affected Cortex-A77 cores (r0p0, r1p0) could deadlock on a sequence
# of a store-exclusive or read of PAR_EL1 and a load with device or
# non-cacheable memory attributes. The workaround depends on a firmware
# counterpart.
#
# KVM guests must also have the workaround implemented or they can
# deadlock the system.
#
# Work around the issue by inserting DMB SY barriers around PAR_EL1
# register reads and warning KVM users. The DMB barrier is sufficient
# to prevent a speculative PAR_EL1 read.
#
# If unsure, say Y.
#
# Symbol: ARM64_ERRATUM_1508412 [=y]
# Type : bool
# Defined at arch/arm64/Kconfig:639
# Prompt: Cortex-A77: 1508412: workaround deadlock on sequence of NC/Device load and store exclusive or PAR read
# Location:
# -> Kernel Features
# -> ARM errata workarounds via the alternatives framework
#
#
#
CONFIG_ARM64_ERRATUM_1508412=y

17
configs/fedora/generic/CONFIG_ARM_CMN Normal file
View File

@ -0,0 +1,17 @@
# CONFIG_ARM_CMN:
#
# Support for PMU events monitoring on the Arm CMN-600 Coherent Mesh
# Network interconnect.
#
# Symbol: ARM_CMN [=n]
# Type : tristate
# Defined at drivers/perf/Kconfig:44
# Prompt: Arm CMN-600 PMU support
# Depends on: PERF_EVENTS [=y] && (ARM64 [=y] || COMPILE_TEST [=n] && 64BIT [=y])
# Location:
# -> Device Drivers
# -> Performance monitor support
#
#
#
# CONFIG_ARM_CMN is not set

21
configs/fedora/generic/CONFIG_ARM_SMMU_V3_SVA Normal file
View File

@ -0,0 +1,21 @@
# CONFIG_ARM_SMMU_V3_SVA:
#
# Support for sharing process address spaces with devices using the
# SMMUv3.
#
# Say Y here if your system supports SVA extensions such as PCIe PASID
# and PRI.
#
# Symbol: ARM_SMMU_V3_SVA [=n]
# Type : bool
# Defined at drivers/iommu/Kconfig:311
# Prompt: Shared Virtual Addressing support for the ARM SMMUv3
# Depends on: IOMMU_SUPPORT [=y] && ARM_SMMU_V3 [=y]
# Location:
# -> Device Drivers
# -> IOMMU Hardware Support (IOMMU_SUPPORT [=y])
# -> ARM Ltd. System MMU Version 3 (SMMUv3) Support (ARM_SMMU_V3 [=y])
#
#
#
# CONFIG_ARM_SMMU_V3_SVA is not set

25
configs/fedora/generic/CONFIG_AS73211 Normal file
View File

@ -0,0 +1,25 @@
# CONFIG_AS73211:
#
# If you say yes here you get support for the AMS AS73211
# JENCOLOR(R) Digital XYZ Sensor.
#
# For triggered measurements, you will need an additional trigger driver
# like IIO_HRTIMER_TRIGGER or IIO_SYSFS_TRIGGER.
#
# This driver can also be built as a module. If so, the module
# will be called as73211.
#
# Symbol: AS73211 [=n]
# Type : tristate
# Defined at drivers/iio/light/Kconfig:89
# Prompt: AMS AS73211 XYZ color sensor
# Depends on: IIO [=m] && I2C [=y]
# Location:
# -> Device Drivers
# -> Industrial I/O support (IIO [=m])
# -> Light sensors
# Selects: IIO_BUFFER [=y] && IIO_TRIGGERED_BUFFER [=m]
#
#
#
# CONFIG_AS73211 is not set

19
configs/fedora/generic/CONFIG_ATH11K_AHB Normal file
View File

@ -0,0 +1,19 @@
# CONFIG_ATH11K_AHB:
#
# This module adds support for AHB bus
#
# Symbol: ATH11K_AHB [=n]
# Type : tristate
# Defined at drivers/net/wireless/ath/ath11k/Kconfig:14
# Prompt: Atheros ath11k AHB support
# Depends on: NETDEVICES [=y] && WLAN [=y] && WLAN_VENDOR_ATH [=y] && ATH11K [=m] && REMOTEPROC [=y]
# Location:
# -> Device Drivers
# -> Network device support (NETDEVICES [=y])
# -> Wireless LAN (WLAN [=y])
# -> Atheros/Qualcomm devices (WLAN_VENDOR_ATH [=y])
# -> Qualcomm Technologies 802.11ax chipset support (ATH11K [=m])
#
#
#
CONFIG_ATH11K_AHB=m

20
configs/fedora/generic/CONFIG_ATH11K_PCI Normal file
View File

@ -0,0 +1,20 @@
# CONFIG_ATH11K_PCI:
#
# This module adds support for PCIE bus
#
# Symbol: ATH11K_PCI [=n]
# Type : tristate
# Defined at drivers/net/wireless/ath/ath11k/Kconfig:21
# Prompt: Atheros ath11k PCI support
# Depends on: NETDEVICES [=y] && WLAN [=y] && WLAN_VENDOR_ATH [=y] && ATH11K [=m] && PCI [=y]
# Location:
# -> Device Drivers
# -> Network device support (NETDEVICES [=y])
# -> Wireless LAN (WLAN [=y])
# -> Atheros/Qualcomm devices (WLAN_VENDOR_ATH [=y])
# -> Qualcomm Technologies 802.11ax chipset support (ATH11K [=m])
# Selects: MHI_BUS [=m] && QRTR [=n] && QRTR_MHI [=n]
#
#
#
CONFIG_ATH11K_PCI=m

20
configs/fedora/generic/CONFIG_BACKLIGHT_KTD253 Normal file
View File

@ -0,0 +1,20 @@
# CONFIG_BACKLIGHT_KTD253:
#
# Say y to enabled the backlight driver for the Kinetic KTD253
# which is a 1-wire GPIO-controlled backlight found in some mobile
# phones.
#
# Symbol: BACKLIGHT_KTD253 [=n]
# Type : tristate
# Defined at drivers/video/backlight/Kconfig:185
# Prompt: Backlight Driver for Kinetic KTD253
# Depends on: HAS_IOMEM [=y] && BACKLIGHT_CLASS_DEVICE [=y] && (GPIOLIB [=y] || COMPILE_TEST [=n])
# Location:
# -> Device Drivers
# -> Graphics support
# -> Backlight & LCD device support
# -> Lowlevel Backlight controls (BACKLIGHT_CLASS_DEVICE [=y])
#
#
#
CONFIG_BACKLIGHT_KTD253=m

18
configs/fedora/generic/CONFIG_BPF_PRELOAD Normal file
View File

@ -0,0 +1,18 @@
# CONFIG_BPF_PRELOAD:
#
# This builds kernel module with several embedded BPF programs that are
# pinned into BPF FS mount point as human readable files that are
# useful in debugging and introspection of BPF programs and maps.
#
# Symbol: BPF_PRELOAD [=n]
# Type : bool
# Defined at kernel/bpf/preload/Kconfig:6
# Prompt: Preload BPF file system with kernel specific program and map iterators
# Depends on: BPF [=y] && !COMPILE_TEST [=n]
# Location:
# -> General setup
# Selects: USERMODE_DRIVER [=n]
#
#
#
CONFIG_BPF_PRELOAD=y

15
configs/fedora/generic/CONFIG_BPF_PRELOAD_UMD Normal file
View File

@ -0,0 +1,15 @@
# CONFIG_BPF_PRELOAD_UMD:
#
# This builds bpf_preload kernel module with embedded user mode driver.
# Symbol: BPF_PRELOAD_UMD [=m]
# Type : tristate
# Defined at kernel/bpf/preload/Kconfig:19
# Prompt: bpf_preload kernel module with user mode driver
# Depends on: BPF_PRELOAD [=y] && CC_CAN_LINK [=y] && (m && MODULES [=y] || CC_CAN_LINK_STATIC [=y])
# Location:
# -> General setup
# -> Preload BPF file system with kernel specific program and map iterators (BPF_PRELOAD [=y])
#
#
#
CONFIG_BPF_PRELOAD_UMD=m

25
configs/fedora/generic/CONFIG_CAN_ISOTP Normal file
View File

@ -0,0 +1,25 @@
# CONFIG_CAN_ISOTP:
#
# CAN Transport Protocols offer support for segmented Point-to-Point
# communication between CAN nodes via two defined CAN Identifiers.
# As CAN frames can only transport a small amount of data bytes
# (max. 8 bytes for 'classic' CAN and max. 64 bytes for CAN FD) this
# segmentation is needed to transport longer PDUs as needed e.g. for
# vehicle diagnosis (UDS, ISO 14229) or IP-over-CAN traffic.
# This protocol driver implements data transfers according to
# ISO 15765-2:2016 for 'classic' CAN and CAN FD frame types.
# If you want to perform automotive vehicle diagnostic services (UDS),
# say 'y'.
#
# Symbol: CAN_ISOTP [=n]
# Type : tristate
# Defined at net/can/Kconfig:58
# Prompt: ISO 15765-2:2016 CAN transport protocol
# Depends on: NET [=y] && CAN [=m]
# Location:
# -> Networking support (NET [=y])
# -> CAN bus subsystem support (CAN [=m])
#
#
#
# CONFIG_CAN_ISOTP is not set

21
configs/fedora/generic/CONFIG_CAN_MCP251XFD Normal file
View File

@ -0,0 +1,21 @@
# CONFIG_CAN_MCP251XFD:
#
# Driver for the Microchip MCP251XFD SPI FD-CAN controller
# family.
#
# Symbol: CAN_MCP251XFD [=n]
# Type : tristate
# Defined at drivers/net/can/spi/mcp251xfd/Kconfig:3
# Prompt: Microchip MCP251xFD SPI CAN controllers
# Depends on: NET [=y] && CAN [=m] && CAN_DEV [=m] && SPI [=y]
# Location:
# -> Networking support (NET [=y])
# -> CAN bus subsystem support (CAN [=m])
# -> CAN Device Drivers
# -> Platform CAN drivers with Netlink support (CAN_DEV [=m])
# -> CAN SPI interfaces
# Selects: REGMAP [=y]
#
#
#
# CONFIG_CAN_MCP251XFD is not set

1
configs/fedora/generic/CONFIG_CHARGER_BQ25980 Normal file
View File

@ -0,0 +1 @@
# CONFIG_CHARGER_BQ25980 is not set

19
configs/fedora/generic/CONFIG_CHELSIO_INLINE_CRYPTO Normal file
View File

@ -0,0 +1,19 @@
# CONFIG_CHELSIO_INLINE_CRYPTO:
#
# Enable support for inline crypto.
# Allows enable/disable from list of inline crypto drivers.
#
# Symbol: CHELSIO_INLINE_CRYPTO [=y]
# Type : bool
# Defined at drivers/net/ethernet/chelsio/inline_crypto/Kconfig:6
# Prompt: Chelsio Inline Crypto support
# Depends on: NETDEVICES [=y] && ETHERNET [=y] && NET_VENDOR_CHELSIO [=y] && CHELSIO_T4 [=m]
# Location:
# -> Device Drivers
# -> Network device support (NETDEVICES [=y])
# -> Ethernet driver support (ETHERNET [=y])
# -> Chelsio devices (NET_VENDOR_CHELSIO [=y])
#
#
#
CONFIG_CHELSIO_INLINE_CRYPTO=y

2
configs/fedora/generic/CONFIG_CHELSIO_IPSEC_INLINE
View File

@ -1 +1 @@
CONFIG_CHELSIO_IPSEC_INLINE=y
CONFIG_CHELSIO_IPSEC_INLINE=m

20
configs/fedora/generic/CONFIG_CHELSIO_TLS_DEVICE
View File

@ -1,19 +1 @@
# CONFIG_CHELSIO_TLS_DEVICE:
#
# This flag enables support for kernel tls offload over Chelsio T6
# crypto accelerator. CONFIG_CHELSIO_TLS_DEVICE flag can be enabled
# only if CONFIG_TLS and CONFIG_TLS_DEVICE flags are enabled.
#
# Symbol: CHELSIO_TLS_DEVICE [=y]
# Type : bool
# Defined at drivers/crypto/chelsio/Kconfig:46
# Prompt: Chelsio Inline KTLS Offload
# Depends on: CRYPTO [=y] && CRYPTO_HW [=y] && CHELSIO_T4 [=m] && TLS_DEVICE [=y]
# Location:
# -> Cryptographic API (CRYPTO [=y])
# -> Hardware crypto devices (CRYPTO_HW [=y])
# Selects: CRYPTO_DEV_CHELSIO [=m]
#
#
#
CONFIG_CHELSIO_TLS_DEVICE=y
CONFIG_CHELSIO_TLS_DEVICE=m

1
configs/fedora/generic/CONFIG_CRYPTO_SHA512 Normal file
View File

@ -0,0 +1 @@
CONFIG_CRYPTO_SHA512=y

23
configs/fedora/generic/CONFIG_CRYPTO_SM2 Normal file
View File

@ -0,0 +1,23 @@
# CONFIG_CRYPTO_SM2:
#
# Generic implementation of the SM2 public key algorithm. It was
# published by State Encryption Management Bureau, China.
# as specified by OSCCA GM/T 0003.1-2012 -- 0003.5-2012.
#
# References:
# https://tools.ietf.org/html/draft-shen-sm2-ecdsa-02
# http://www.oscca.gov.cn/sca/xxgk/2010-12/17/content_1002386.shtml
# http://www.gmbz.org.cn/main/bzlb.html
#
# Symbol: CRYPTO_SM2 [=n]
# Type : tristate
# Defined at crypto/Kconfig:263
# Prompt: SM2 algorithm
# Depends on: CRYPTO [=y]
# Location:
# -> Cryptographic API (CRYPTO [=y])
# Selects: CRYPTO_SM3 [=m] && CRYPTO_AKCIPHER [=y] && CRYPTO_MANAGER [=y] && MPILIB [=y] && ASN1 [=y]
#
#
#
CONFIG_CRYPTO_SM2=m

17
configs/fedora/generic/CONFIG_CRYPTO_USER_API_ENABLE_OBSOLETE Normal file
View File

@ -0,0 +1,17 @@
# CONFIG_CRYPTO_USER_API_ENABLE_OBSOLETE:
#
# Allow obsolete cryptographic algorithms to be selected that have
# already been phased out from internal use by the kernel, and are
# only useful for userspace clients that still rely on them.
#
# Symbol: CRYPTO_USER_API_ENABLE_OBSOLETE [=y]
# Type : bool
# Defined at crypto/Kconfig:1915
# Prompt: Enable obsolete cryptographic algorithms for userspace
# Depends on: CRYPTO [=y] && CRYPTO_USER_API [=y]
# Location:
# -> Cryptographic API (CRYPTO [=y])
#
#
#
# CONFIG_CRYPTO_USER_API_ENABLE_OBSOLETE is not set

19
configs/fedora/generic/CONFIG_CRYPTO_USER_API_RNG_CAVP Normal file
View File

@ -0,0 +1,19 @@
# CONFIG_CRYPTO_USER_API_RNG_CAVP:
#
# This option enables extra API for CAVP testing via the user-space
# interface: resetting of DRBG entropy, and providing Additional Data.
# This should only be enabled for CAVP testing. You should say
# no unless you know what this is.
#
# Symbol: CRYPTO_USER_API_RNG_CAVP [=n]
# Type : bool
# Defined at crypto/Kconfig:1895
# Prompt: Enable CAVP testing of DRBG
# Depends on: CRYPTO [=y] && CRYPTO_USER_API_RNG [=y] && CRYPTO_DRBG [=y]
# Location:
# -> Cryptographic API (CRYPTO [=y])
# -> User-space interface for random number generator algorithms (CRYPTO_USER_API_RNG [=y])
#
#
#
# CONFIG_CRYPTO_USER_API_RNG_CAVP is not set

19
configs/fedora/generic/CONFIG_CSD_LOCK_WAIT_DEBUG Normal file
View File

@ -0,0 +1,19 @@
# CONFIG_CSD_LOCK_WAIT_DEBUG:
#
# This option enables debug prints when CPUs are slow to respond
# to the smp_call_function*() IPI wrappers. These debug prints
# include the IPI handler function currently executing (if any)
# and relevant stack traces.
#
# Symbol: CSD_LOCK_WAIT_DEBUG [=n]
# Type : bool
# Defined at lib/Kconfig.debug:1380
# Prompt: Debugging for csd_lock_wait(), called from smp_call_function*()
# Depends on: DEBUG_KERNEL [=y] && 64BIT [=y]
# Location:
# -> Kernel hacking
# -> Lock Debugging (spinlocks, mutexes, etc...)
#
#
#
# CONFIG_CSD_LOCK_WAIT_DEBUG is not set

20
configs/fedora/generic/CONFIG_DMA_PERNUMA_CMA Normal file
View File

@ -0,0 +1,20 @@
# CONFIG_DMA_PERNUMA_CMA:
#
# Enable this option to get pernuma CMA areas so that devices like
# ARM64 SMMU can get local memory by DMA coherent APIs.
#
# You can set the size of pernuma CMA by specifying "cma_pernuma=size"
# on the kernel's command line.
#
# Symbol: DMA_PERNUMA_CMA [=n]
# Type : bool
# Defined at kernel/dma/Kconfig:126
# Prompt: Enable separate DMA Contiguous Memory Area for each NUMA Node
# Depends on: DMA_CMA [=y]
# Location:
# -> Library routines
# -> DMA Contiguous Memory Allocator (DMA_CMA [=y])
#
#
#
# CONFIG_DMA_PERNUMA_CMA is not set

1
configs/fedora/generic/CONFIG_DPTF_PCH_FIVR Normal file
View File

@ -0,0 +1 @@
# CONFIG_DPTF_PCH_FIVR is not set

20
configs/fedora/generic/CONFIG_DRM_AMD_DC_SI Normal file
View File

@ -0,0 +1,20 @@
# CONFIG_DRM_AMD_DC_SI:
#
# Choose this option to enable new AMD DC support for SI asics
# by default. This includes Tahiti, Pitcairn, Cape Verde, Oland.
# Hainan is not supported by AMD DC and it has no physical DCE6.
#
# Symbol: DRM_AMD_DC_SI [=n]
# Type : bool
# Defined at drivers/gpu/drm/amd/display/Kconfig:34
# Prompt: AMD DC support for Southern Islands ASICs
# Depends on: HAS_IOMEM [=y] && DRM [=m] && DRM_AMDGPU [=m]
# Location:
# -> Device Drivers
# -> Graphics support
# -> AMD GPU (DRM_AMDGPU [=m])
# -> Display Engine Configuration
#
#
#
CONFIG_DRM_AMD_DC_SI=y

1
configs/fedora/generic/CONFIG_DRM_CDNS_MHDP8546 Normal file
View File

@ -0,0 +1 @@
# CONFIG_DRM_CDNS_MHDP8546 is not set

1
configs/fedora/generic/CONFIG_DRM_LONTIUM_LT9611 Normal file
View File

@ -0,0 +1 @@
# CONFIG_DRM_LONTIUM_LT9611 is not set

1
configs/fedora/generic/CONFIG_DRM_PANEL_MANTIX_MLAF057WE51 Normal file
View File

@ -0,0 +1 @@
CONFIG_DRM_PANEL_MANTIX_MLAF057WE51=m

1
configs/fedora/generic/CONFIG_DRM_TOSHIBA_TC358762 Normal file
View File

@ -0,0 +1 @@
CONFIG_DRM_TOSHIBA_TC358762=m

1
configs/fedora/generic/CONFIG_DRM_TOSHIBA_TC358775 Normal file
View File

@ -0,0 +1 @@
CONFIG_DRM_TOSHIBA_TC358775=m

23
configs/fedora/generic/CONFIG_DWMAC_INTEL_PLAT Normal file
View File

@ -0,0 +1,23 @@
# CONFIG_DWMAC_INTEL_PLAT:
#
# Support for ethernet controllers on Intel SoCs
#
# This selects the Intel platform specific glue layer support for
# the stmmac device driver. This driver is used for the Intel Keem Bay
# SoC.
# Symbol: DWMAC_INTEL_PLAT [=n]
# Type : tristate
# Defined at drivers/net/ethernet/stmicro/stmmac/Kconfig:212
# Prompt: Intel dwmac support
# Depends on: NETDEVICES [=y] && ETHERNET [=y] && NET_VENDOR_STMICRO [=y] && STMMAC_PLATFORM [=m] && OF [=y] && COMMON_CLK [=y] && STMMAC_ETH [=m]
# Location:
# -> Device Drivers
# -> Network device support (NETDEVICES [=y])
# -> Ethernet driver support (ETHERNET [=y])
# -> STMicroelectronics devices (NET_VENDOR_STMICRO [=y])
# -> STMicroelectronics Multi-Gigabit Ethernet driver (STMMAC_ETH [=m])
# -> STMMAC Platform bus support (STMMAC_PLATFORM [=m])
#
#
#
CONFIG_DWMAC_INTEL_PLAT=m

2
configs/fedora/generic/CONFIG_EVM
View File

@ -1 +1 @@
# CONFIG_EVM is not set
CONFIG_EVM=y

1
configs/fedora/generic/CONFIG_EVM_ADD_XATTRS Normal file
View File

@ -0,0 +1 @@
# CONFIG_EVM_ADD_XATTRS is not set

1
configs/fedora/generic/CONFIG_EVM_ATTR_FSUUID Normal file
View File

@ -0,0 +1 @@
CONFIG_EVM_ATTR_FSUUID=y

1
configs/fedora/generic/CONFIG_EVM_LOAD_X509 Normal file
View File

@ -0,0 +1 @@
# CONFIG_EVM_LOAD_X509 is not set

18
configs/fedora/generic/CONFIG_FAULT_INJECTION_USERCOPY Normal file
View File

@ -0,0 +1,18 @@
# CONFIG_FAULT_INJECTION_USERCOPY:
#
# Provides fault-injection capability to inject failures
# in usercopy functions (copy_from_user(), get_user(), ...).
#
# Symbol: FAULT_INJECTION_USERCOPY [=n]
# Type : bool
# Defined at lib/Kconfig.debug:1771
# Prompt: Fault injection capability for usercopy functions
# Depends on: FAULT_INJECTION [=y]
# Location:
# -> Kernel hacking
# -> Kernel Testing and Coverage
# -> Fault-injection framework (FAULT_INJECTION [=y])
#
#
#
# CONFIG_FAULT_INJECTION_USERCOPY is not set

22
configs/fedora/generic/CONFIG_FUSE_DAX Normal file
View File

@ -0,0 +1,22 @@
# CONFIG_FUSE_DAX:
#
# This allows bypassing guest page cache and allows mapping host page
# cache directly in guest address space.
#
# If you want to allow mounting a Virtio Filesystem with the "dax"
# option, answer Y.
#
# Symbol: FUSE_DAX [=y]
# Type : bool
# Defined at fs/fuse/Kconfig:42
# Prompt: Virtio Filesystem Direct Host Memory Access support
# Depends on: VIRTIO_FS [=m] && FS_DAX [=y] && DAX_DRIVER [=y]
# Location:
# -> File systems
# -> FUSE (Filesystem in Userspace) support (FUSE_FS [=m])
# -> Virtio Filesystem (VIRTIO_FS [=m])
# Selects: INTERVAL_TREE [=y]
#
#
#
CONFIG_FUSE_DAX=y

2
configs/fedora/generic/CONFIG_GNSS
View File

@ -1 +1 @@
# CONFIG_GNSS is not set
CONFIG_GNSS=m

1
configs/fedora/generic/CONFIG_GNSS_MTK_SERIAL Normal file
View File

@ -0,0 +1 @@
CONFIG_GNSS_MTK_SERIAL=m

1
configs/fedora/generic/CONFIG_GNSS_SIRF_SERIAL Normal file
View File

@ -0,0 +1 @@
CONFIG_GNSS_SIRF_SERIAL=m

1
configs/fedora/generic/CONFIG_GNSS_UBX_SERIAL Normal file
View File

@ -0,0 +1 @@
CONFIG_GNSS_UBX_SERIAL=m

1
configs/fedora/generic/CONFIG_GPIO_CDEV_V1 Normal file
View File

@ -0,0 +1 @@
CONFIG_GPIO_CDEV_V1=y

1
configs/fedora/generic/CONFIG_GPIO_MXC Normal file
View File

@ -0,0 +1 @@
CONFIG_GPIO_MXC=m

21
configs/fedora/generic/CONFIG_HDC2010 Normal file
View File

@ -0,0 +1,21 @@
# CONFIG_HDC2010:
#
# Say yes here to build support for the Texas Instruments
# HDC2010 and HDC2080 relative humidity and temperature sensors.
#
# To compile this driver as a module, choose M here: the module
# will be called hdc2010.
#
# Symbol: HDC2010 [=n]
# Type : tristate
# Defined at drivers/iio/humidity/Kconfig:41
# Prompt: TI HDC2010 relative humidity and temperature sensor
# Depends on: IIO [=m] && I2C [=y]
# Location:
# -> Device Drivers
# -> Industrial I/O support (IIO [=m])
# -> Humidity sensors
#
#
#
CONFIG_HDC2010=m

21
configs/fedora/generic/CONFIG_HID_VIVALDI Normal file
View File

@ -0,0 +1,21 @@
# CONFIG_HID_VIVALDI:
#
# Say Y here if you want to enable support for Vivaldi keyboards.
#
# Vivaldi keyboards use a vendor-specific (Google) HID usage to report
# how the keys in the top row are physically ordered.
#
# Symbol: HID_VIVALDI [=n]
# Type : tristate
# Defined at drivers/hid/Kconfig:400
# Prompt: Vivaldi Keyboard
# Depends on: INPUT [=y] && HID [=y]
# Location:
# -> Device Drivers
# -> HID support
# -> HID bus support (HID [=y])
# -> Special HID drivers
#
#
#
CONFIG_HID_VIVALDI=m

19
configs/fedora/generic/CONFIG_HISI_HIKEY_USB Normal file
View File

@ -0,0 +1,19 @@
# CONFIG_HISI_HIKEY_USB:
#
# If you say yes here this adds support for the on-board USB GPIO hub
# found on HiKey 960/970 boards, which is necessary to support
# switching between the dual-role USB-C port and the USB-A host ports
# using only one USB controller.
#
# Symbol: HISI_HIKEY_USB [=n]
# Type : tristate
# Defined at drivers/misc/Kconfig:459
# Prompt: USB GPIO Hub on HiSilicon Hikey 960/970 Platform
# Depends on: (OF [=y] && GPIOLIB [=y] || COMPILE_TEST [=n]) && USB_ROLE_SWITCH [=m]
# Location:
# -> Device Drivers
# -> Misc devices
#
#
#
CONFIG_HISI_HIKEY_USB=m

32
configs/fedora/generic/CONFIG_HIST_TRIGGERS_DEBUG
View File

@ -1,33 +1 @@
# CONFIG_HIST_TRIGGERS_DEBUG:
#
# Add "hist_debug" file for each event, which when read will
# dump out a bunch of internal details about the hist triggers
# defined on that event.
#
# The hist_debug file serves a couple of purposes:
#
# - Helps developers verify that nothing is broken.
#
# - Provides educational information to support the details
# of the hist trigger internals as described by
# Documentation/trace/histogram-design.rst.
#
# The hist_debug output only covers the data structures
# related to the histogram definitions themselves and doesn't
# display the internals of map buckets or variable values of
# running histograms.
#
# If unsure, say N.
#
# Symbol: HIST_TRIGGERS_DEBUG [=n]
# Type : bool
# Defined at kernel/trace/Kconfig:850
# Prompt: Hist trigger debug support
# Depends on: TRACING_SUPPORT [=y] && FTRACE [=y] && HIST_TRIGGERS [=y]
# Location:
# -> Kernel hacking
# -> Tracers (FTRACE [=y])
#
#
#
# CONFIG_HIST_TRIGGERS_DEBUG is not set

21
configs/fedora/generic/CONFIG_HW_RANDOM_XIPHERA Normal file
View File

@ -0,0 +1,21 @@
# CONFIG_HW_RANDOM_XIPHERA:
#
# This driver provides kernel-side support for Xiphera True Random
# Number Generator Intellectual Property Core.
#
# To compile this driver as a module, choose M here: the
# module will be called xiphera-trng.
#
# Symbol: HW_RANDOM_XIPHERA [=n]
# Type : tristate
# Defined at drivers/char/hw_random/Kconfig:529
# Prompt: Xiphera FPGA based True Random Number Generator support
# Depends on: HW_RANDOM [=y] && HAS_IOMEM [=y]
# Location:
# -> Device Drivers
# -> Character devices
# -> Hardware Random Number Generator Core support (HW_RANDOM [=y])
#
#
#
CONFIG_HW_RANDOM_XIPHERA=m

25
configs/fedora/generic/CONFIG_I2C_MLXBF Normal file
View File

@ -0,0 +1,25 @@
# CONFIG_I2C_MLXBF:
#
# Enabling this option will add I2C SMBus support for Mellanox BlueField
# system.
#
# This driver can also be built as a module. If so, the module will be
# called i2c-mlxbf.
#
# This driver implements an I2C SMBus host controller and enables both
# master and slave functions.
#
# Symbol: I2C_MLXBF [=n]
# Type : tristate
# Defined at drivers/i2c/busses/Kconfig:734
# Prompt: Mellanox BlueField I2C controller
# Depends on: I2C [=y] && HAS_IOMEM [=y] && ARM64 [=y]
# Location:
# -> Device Drivers
# -> I2C support
# -> I2C support (I2C [=y])
# -> I2C Hardware Bus support
#
#
#
CONFIG_I2C_MLXBF=m

21
configs/fedora/generic/CONFIG_I2C_SLAVE_TESTUNIT Normal file
View File

@ -0,0 +1,21 @@
# CONFIG_I2C_SLAVE_TESTUNIT:
#
# This backend can be used to trigger test cases for I2C bus masters
# which require a remote device with certain capabilities, e.g.
# multi-master, SMBus Host Notify, etc. Please read
# Documentation/i2c/slave-testunit-backend.rst for further details.
#
# Symbol: I2C_SLAVE_TESTUNIT [=n]
# Type : tristate
# Defined at drivers/i2c/Kconfig:128
# Prompt: I2C eeprom testunit driver
# Depends on: I2C [=y] && I2C_SLAVE [=y]
# Location:
# -> Device Drivers
# -> I2C support
# -> I2C support (I2C [=y])
# -> I2C slave support (I2C_SLAVE [=y])
#
#
#
# CONFIG_I2C_SLAVE_TESTUNIT is not set

1
configs/fedora/generic/CONFIG_IIO_BUFFER_DMA Normal file
View File

@ -0,0 +1 @@
CONFIG_IIO_BUFFER_DMA=m

1
configs/fedora/generic/CONFIG_IIO_BUFFER_DMAENGINE Normal file
View File

@ -0,0 +1 @@
CONFIG_IIO_BUFFER_DMAENGINE=m

19
configs/fedora/generic/CONFIG_IIO_TRIGGERED_EVENT Normal file
View File

@ -0,0 +1,19 @@
# CONFIG_IIO_TRIGGERED_EVENT:
#
# Provides helper functions for setting up triggered events.
#
# Symbol: IIO_TRIGGERED_EVENT [=n]
# Type : tristate
# Defined at drivers/iio/Kconfig:65
# Prompt: Enable triggered events support
# Depends on: IIO [=m]
# Location:
# -> Device Drivers
# -> Industrial I/O support (IIO [=m])
# Selects: IIO_TRIGGER [=y]
# Selected by [n]:
# - HI8435 [=n] && IIO [=m] && SPI [=y]
#
#
#
CONFIG_IIO_TRIGGERED_EVENT=m

1
configs/fedora/generic/CONFIG_IMA_DEFAULT_HASH Normal file
View File

@ -0,0 +1 @@
CONFIG_IMA_DEFAULT_HASH="sha256"

1
configs/fedora/generic/CONFIG_INET_MPTCP_DIAG Normal file
View File

@ -0,0 +1 @@
CONFIG_INET_MPTCP_DIAG=m

1
configs/fedora/generic/CONFIG_INTEL_MEI_VIRTIO Normal file
View File

@ -0,0 +1 @@
# CONFIG_INTEL_MEI_VIRTIO is not set

22
configs/fedora/generic/CONFIG_JOYSTICK_ADC Normal file
View File

@ -0,0 +1,22 @@
# CONFIG_JOYSTICK_ADC:
#
# Say Y here if you have a simple joystick connected over ADC.
#
# To compile this driver as a module, choose M here: the
# module will be called adc-joystick.
#
# Symbol: JOYSTICK_ADC [=n]
# Type : tristate
# Defined at drivers/input/joystick/Kconfig:45
# Prompt: Simple joystick connected over ADC
# Depends on: !UML && INPUT [=y] && INPUT_JOYSTICK [=y] && IIO [=m]
# Location:
# -> Device Drivers
# -> Input device support
# -> Generic input layer (needed for keyboard, mouse, ...) (INPUT [=y])
# -> Joysticks/Gamepads (INPUT_JOYSTICK [=y])
# Selects: IIO_BUFFER_CB [=m]
#
#
#
CONFIG_JOYSTICK_ADC=m

2
configs/fedora/generic/CONFIG_JOYSTICK_MAGELLAN
View File

@ -1 +1 @@
CONFIG_JOYSTICK_MAGELLAN=m
# CONFIG_JOYSTICK_MAGELLAN is not set

2
configs/fedora/generic/CONFIG_JOYSTICK_SPACEBALL
View File

@ -1 +1 @@
CONFIG_JOYSTICK_SPACEBALL=m
# CONFIG_JOYSTICK_SPACEBALL is not set

2
configs/fedora/generic/CONFIG_JOYSTICK_SPACEORB
View File

@ -1 +1 @@
CONFIG_JOYSTICK_SPACEORB=m
# CONFIG_JOYSTICK_SPACEORB is not set

2
configs/fedora/generic/CONFIG_JOYSTICK_STINGER
View File

@ -1 +1 @@
CONFIG_JOYSTICK_STINGER=m
# CONFIG_JOYSTICK_STINGER is not set

2
configs/fedora/generic/CONFIG_JOYSTICK_TWIDJOY
View File

@ -1 +1 @@
CONFIG_JOYSTICK_TWIDJOY=m
# CONFIG_JOYSTICK_TWIDJOY is not set

2
configs/fedora/generic/CONFIG_JOYSTICK_WARRIOR
View File

@ -1 +1 @@
CONFIG_JOYSTICK_WARRIOR=m
# CONFIG_JOYSTICK_WARRIOR is not set

2
configs/fedora/generic/CONFIG_JOYSTICK_ZHENHUA
View File

@ -1 +1 @@
CONFIG_JOYSTICK_ZHENHUA=m
# CONFIG_JOYSTICK_ZHENHUA is not set

17
configs/fedora/generic/CONFIG_KEXEC_IMAGE_VERIFY_SIG Normal file
View File

@ -0,0 +1,17 @@
# CONFIG_KEXEC_IMAGE_VERIFY_SIG:
#
# Enable Image signature verification support.
#
# Symbol: KEXEC_IMAGE_VERIFY_SIG [=y]
# Type : bool
# Defined at arch/arm64/Kconfig:1095
# Prompt: Enable Image signature verification support
# Depends on: KEXEC_SIG [=y] && EFI [=y] && SIGNED_PE_FILE_VERIFICATION [=y]
# Location:
# -> Kernel Features
# -> kexec file based system call (KEXEC_FILE [=y])
# -> Verify kernel signature during kexec_file_load() syscall (KEXEC_SIG [=y])
#
#
#
CONFIG_KEXEC_IMAGE_VERIFY_SIG=y

24
configs/fedora/generic/CONFIG_KGDB_HONOUR_BLOCKLIST Normal file
View File

@ -0,0 +1,24 @@
# CONFIG_KGDB_HONOUR_BLOCKLIST:
#
# If set to Y the debug core will use the kprobe blocklist to
# identify symbols where it is unsafe to set breakpoints.
# In particular this disallows instrumentation of functions
# called during debug trap handling and thus makes it very
# difficult to inadvertently provoke recursive trap handling.
#
# If unsure, say Y.
#
# Symbol: KGDB_HONOUR_BLOCKLIST [=y]
# Type : bool
# Defined at lib/Kconfig.kgdb:27
# Prompt: KGDB: use kprobe blocklist to prohibit unsafe breakpoints
# Depends on: KGDB [=y] && HAVE_KPROBES [=y] && MODULES [=y]
# Location:
# -> Kernel hacking
# -> Generic Kernel Debugging Instruments
# -> KGDB: kernel debugger (KGDB [=y])
# Selects: KPROBES [=y]
#
#
#
CONFIG_KGDB_HONOUR_BLOCKLIST=y

1
configs/fedora/generic/CONFIG_LEDS_ARIEL Normal file
View File

@ -0,0 +1 @@
# CONFIG_LEDS_ARIEL is not set

20
configs/fedora/generic/CONFIG_LEDS_LP50XX Normal file
View File

@ -0,0 +1,20 @@
# CONFIG_LEDS_LP50XX:
#
# If you say yes here you get support for the Texas Instruments
# LP5036, LP5030, LP5024, LP5018, LP5012 and LP5009 LED driver.
#
# To compile this driver as a module, choose M here: the
# module will be called leds-lp50xx.
#
# Symbol: LEDS_LP50XX [=n]
# Type : tristate
# Defined at drivers/leds/Kconfig:398
# Prompt: LED Support for TI LP5036/30/24/18/12/9 LED driver chip
# Depends on: NEW_LEDS [=y] && LEDS_CLASS [=y] && REGMAP_I2C [=y] && (LEDS_CLASS_MULTICOLOR [=m] || !LEDS_CLASS_MULTICOLOR [=m])
# Location:
# -> Device Drivers
# -> LED Support (NEW_LEDS [=y])
#
#
#
CONFIG_LEDS_LP50XX=m

20
configs/fedora/generic/CONFIG_MFD_ENE_KB3930 Normal file
View File

@ -0,0 +1,20 @@
# CONFIG_MFD_ENE_KB3930:
#
# This adds support for the power-off functionality and access to
# the registers that control LEDS and USB port power on ENE KB3930
# Embedded Controller. To use the LED functionality LEDS_ARIEL must
# be enabled.
#
# Symbol: MFD_ENE_KB3930 [=n]
# Type : tristate
# Defined at drivers/mfd/Kconfig:402
# Prompt: ENE KB3930 Embedded Controller support
# Depends on: HAS_IOMEM [=y] && I2C [=y] && (MACH_MMP3_DT [=y] || COMPILE_TEST [=n])
# Location:
# -> Device Drivers
# -> Multifunction device drivers
# Selects: MFD_CORE [=y]
#
#
#
CONFIG_MFD_ENE_KB3930=m

24
configs/fedora/generic/CONFIG_MFD_HI6421_SPMI Normal file
View File

@ -0,0 +1,24 @@
# CONFIG_MFD_HI6421_SPMI:
#
# Add support for HiSilicon Hi6421v600 SPMI PMIC. Hi6421 includes
# multi-functions, such as regulators, RTC, codec, Coulomb counter,
# etc.
#
# This driver includes core APIs _only_. You have to select
# individual components like voltage regulators under corresponding
# menus in order to enable them.
# We communicate with the Hi6421v600 via a SPMI bus.
#
# Symbol: MFD_HI6421_SPMI [=n]
# Type : tristate
# Defined at drivers/staging/hikey9xx/Kconfig:26
# Prompt: HiSilicon Hi6421v600 SPMI PMU/Codec IC
# Depends on: STAGING [=y] && OF [=y] && SPMI [=m]
# Location:
# -> Device Drivers
# -> Staging drivers (STAGING [=y])
# Selects: MFD_CORE [=y]
#
#
#
# CONFIG_MFD_HI6421_SPMI is not set

22
configs/fedora/generic/CONFIG_MFD_INTEL_M10_BMC Normal file
View File

@ -0,0 +1,22 @@
# CONFIG_MFD_INTEL_M10_BMC:
#
# Support for the Intel MAX 10 board management controller using the
# SPI interface.
#
# This driver provides common support for accessing the device,
# additional drivers must be enabled in order to use the functionality
# of the device.
#
# Symbol: MFD_INTEL_M10_BMC [=n]
# Type : tristate
# Defined at drivers/mfd/Kconfig:2156
# Prompt: Intel MAX 10 Board Management Controller
# Depends on: HAS_IOMEM [=y] && SPI_MASTER [=y]
# Location:
# -> Device Drivers
# -> Multifunction device drivers
# Selects: REGMAP_SPI_AVMM [=n] && MFD_CORE [=y]
#
#
#
CONFIG_MFD_INTEL_M10_BMC=m

20
configs/fedora/generic/CONFIG_MFD_INTEL_PMC_BXT
View File

@ -1,21 +1 @@
# CONFIG_MFD_INTEL_PMC_BXT:
#
# This driver provides support for the PMC (Power Management
# Controller) on Intel Broxton and Apollo Lake. The PMC is a
# multi-function device that exposes IPC, General Control
# Register and P-unit access. In addition this creates devices
# for iTCO watchdog and telemetry that are part of the PMC.
#
# Symbol: MFD_INTEL_PMC_BXT [=n]
# Type : tristate
# Defined at drivers/mfd/Kconfig:650
# Prompt: Intel PMC Driver for Broxton
# Depends on: HAS_IOMEM [=y] && X86 [=y] && X86_PLATFORM_DEVICES [=y] && ACPI [=y]
# Location:
# -> Device Drivers
# -> Multifunction device drivers
# Selects: INTEL_SCU_IPC [=n] && MFD_CORE [=y]
#
#
#
# CONFIG_MFD_INTEL_PMC_BXT is not set

0
linux-kernel-test.patch → configs/fedora/generic/CONFIG_MFD_KHADAS_MCU
View File

18
configs/fedora/generic/CONFIG_MFD_MP2629
View File

@ -1,19 +1 @@
# CONFIG_MFD_MP2629:
#
# Select this option to enable support for Monolithic Power Systems
# battery charger. This provides ADC, thermal and battery charger power
# management functions.
#
# Symbol: MFD_MP2629 [=n]
# Type : tristate
# Defined at drivers/mfd/Kconfig:452
# Prompt: Monolithic Power Systems MP2629 ADC and Battery charger
# Depends on: HAS_IOMEM [=y] && I2C [=y]
# Location:
# -> Device Drivers
# -> Multifunction device drivers
# Selects: REGMAP_I2C [=m]
#
#
#
# CONFIG_MFD_MP2629 is not set

19
configs/fedora/generic/CONFIG_MFD_MT6360
View File

@ -1,20 +1 @@
# CONFIG_MFD_MT6360:
#
# Say Y here to enable MT6360 PMU/PMIC/LDO functional support.
# PMU part includes Charger, Flashlight, RGB LED
# PMIC part includes 2-channel BUCKs and 2-channel LDOs
# LDO part includes 4-channel LDOs
#
# Symbol: MFD_MT6360 [=n]
# Type : tristate
# Defined at drivers/mfd/Kconfig:911
# Prompt: Mediatek MT6360 SubPMIC
# Depends on: HAS_IOMEM [=y] && I2C [=y]
# Location:
# -> Device Drivers
# -> Multifunction device drivers
# Selects: MFD_CORE [=y] && REGMAP_I2C [=m] && REGMAP_IRQ [=y]
#
#
#
# CONFIG_MFD_MT6360 is not set

21
configs/fedora/generic/CONFIG_MFD_SL28CPLD Normal file
View File

@ -0,0 +1,21 @@
# CONFIG_MFD_SL28CPLD:
#
# Say yes here to enable support for the Kontron sl28cpld board
# management controller.
#
# It can be found on the following boards:
# * SMARC-sAL28
#
# Symbol: MFD_SL28CPLD [=n]
# Type : tristate
# Defined at drivers/mfd/Kconfig:1189
# Prompt: Kontron sl28cpld Board Management Controller
# Depends on: HAS_IOMEM [=y] && I2C [=y]
# Location:
# -> Device Drivers
# -> Multifunction device drivers
# Selects: MFD_SIMPLE_MFD_I2C [=n]
#
#
#
# CONFIG_MFD_SL28CPLD is not set

19
configs/fedora/generic/CONFIG_MHI_BUS_DEBUG Normal file
View File

@ -0,0 +1,19 @@
# CONFIG_MHI_BUS_DEBUG:
#
# Enable debugfs support for use with the MHI transport. Allows
# reading and/or modifying some values within the MHI controller
# for debug and test purposes.
#
# Symbol: MHI_BUS_DEBUG [=n]
# Type : bool
# Defined at drivers/bus/mhi/Kconfig:16
# Prompt: Debugfs support for the MHI bus
# Depends on: MHI_BUS [=m] && DEBUG_FS [=y]
# Location:
# -> Device Drivers
# -> Bus devices
# -> Modem Host Interface (MHI) bus (MHI_BUS [=m])
#
#
#
# CONFIG_MHI_BUS_DEBUG is not set

1
configs/fedora/generic/CONFIG_MVPP2_PTP Normal file
View File

@ -0,0 +1 @@
CONFIG_MVPP2_PTP=y

18
configs/fedora/generic/CONFIG_NFS_V4_2_READ_PLUS Normal file
View File

@ -0,0 +1,18 @@
# CONFIG_NFS_V4_2_READ_PLUS:
#
# This is intended for developers only. The READ_PLUS operation has
# been shown to have issues under specific conditions and should not
# be used in production.
#
# Symbol: NFS_V4_2_READ_PLUS [=n]
# Type : bool
# Defined at fs/nfs/Kconfig:209
# Prompt: NFS: Enable support for the NFSv4.2 READ_PLUS operation
# Depends on: NETWORK_FILESYSTEMS [=y] && NFS_V4_2 [=y]
# Location:
# -> File systems
# -> Network File Systems (NETWORK_FILESYSTEMS [=y])
#
#
#
# CONFIG_NFS_V4_2_READ_PLUS is not set

18
configs/fedora/generic/CONFIG_PCIE_HISI_ERR Normal file
View File

@ -0,0 +1,18 @@
# CONFIG_PCIE_HISI_ERR:
#
# Say Y here if you want error handling support
# for the PCIe controller's errors on HiSilicon HIP SoCs
#
# Symbol: PCIE_HISI_ERR [=n]
# Type : bool
# Defined at drivers/pci/controller/Kconfig:301
# Prompt: HiSilicon HIP PCIe controller error handling driver
# Depends on: PCI [=y] && ACPI_APEI_GHES [=y] && (ARM64 [=y] || COMPILE_TEST [=n])
# Location:
# -> Device Drivers
# -> PCI support (PCI [=y])
# -> PCI controller drivers
#
#
#
# CONFIG_PCIE_HISI_ERR is not set

21
configs/fedora/generic/CONFIG_PCS_XPCS Normal file
View File

@ -0,0 +1,21 @@
# CONFIG_PCS_XPCS:
#
# This module provides helper functions for Synopsys DesignWare XPCS
# controllers.
#
# Symbol: PCS_XPCS [=m]
# Type : tristate
# Defined at drivers/net/pcs/Kconfig:8
# Prompt: Synopsys DesignWare XPCS controller
# Depends on: NETDEVICES [=y] && MDIO_DEVICE [=y]
# Location:
# -> Device Drivers
# -> Network device support (NETDEVICES [=y])
# -> PCS device drivers
# Selects: MDIO_BUS [=y]
# Selected by [m]:
# - STMMAC_ETH [=m] && NETDEVICES [=y] && ETHERNET [=y] && NET_VENDOR_STMICRO [=y] && HAS_IOMEM [=y] && HAS_DMA [=y]
#
#
#
CONFIG_PCS_XPCS=m

19
configs/fedora/generic/CONFIG_PHY_HI3670_USB Normal file
View File

@ -0,0 +1,19 @@
# CONFIG_PHY_HI3670_USB:
#
# Enable this to support the HISILICON HI3670 USB PHY.
#
# To compile this driver as a module, choose M here.
#
# Symbol: PHY_HI3670_USB [=n]
# Type : tristate
# Defined at drivers/staging/hikey9xx/Kconfig:4
# Prompt: hi3670 USB PHY support
# Depends on: STAGING [=y] && (ARCH_HISI [=y] && ARM64 [=y] || COMPILE_TEST [=n])
# Location:
# -> Device Drivers
# -> Staging drivers (STAGING [=y])
# Selects: GENERIC_PHY [=y] && MFD_SYSCON [=y]
#
#
#
# CONFIG_PHY_HI3670_USB is not set

1
configs/fedora/generic/CONFIG_PHY_INTEL_KEEMBAY_EMMC Normal file
View File

@ -0,0 +1 @@
# CONFIG_PHY_INTEL_KEEMBAY_EMMC is not set

1
configs/fedora/generic/CONFIG_PHY_INTEL_LGM_EMMC Normal file
View File

@ -0,0 +1 @@
# CONFIG_PHY_INTEL_LGM_EMMC is not set

1
configs/fedora/generic/CONFIG_PINCTRL_MSM8226 Normal file
View File

@ -0,0 +1 @@
# CONFIG_PINCTRL_MSM8226 is not set

Some files were not shown because too many files have changed in this diff Show More