ASOC: Intel: sof_sdw: add quirk for Intel 'Rooks County' NUC M15
Subsystems (12)
Sasha Levin
maintainerPATCH 9/15 net: wwan: t7xx: do not compile with -Werror
In reply to Sasha LevinFrom: "Jiri Slaby (SUSE)" <[email protected]>
[ Upstream commit 362f0b6678ad1377c322a7dd237ea6785efc7342 ]
When playing with various compilers or their versions, some choke on the t7xx code. For example (with gcc 13):
In file included from ./arch/s390/include/generated/asm/rwonce.h:1,
from ../include/linux/compiler.h:247,
from ../include/linux/build_bug.h:5,
from ../include/linux/bits.h:22,
from ../drivers/net/wwan/t7xx/t7xx_state_monitor.c:17:
In function 'preempt_count',
inlined from 't7xx_fsm_append_event' at ../drivers/net/wwan/t7xx/t7xx_state_monitor.c:439:43: ../include/asm-generic/rwonce.h:44:26: error: array subscript 0 is outside array bounds of 'const volatile int[0]' [-Werror=array-bounds=]
There is no reason for any code in the kernel to be built with -Werror by default. Note that we have generic CONFIG_WERROR. So if anyone wants -Werror, they can enable that.
--- drivers/net/wwan/t7xx/Makefile | 2 -- 1 file changed, 2 deletions(-)
drivers/net/wwan/t7xx/Makefile +0 -2
@@ -1,7 +1,5 @@ # SPDX-License-Identifier: GPL-2.0-only -ccflags-y += -Werror - obj-${CONFIG_MTK_T7XX} := mtk_t7xx.o mtk_t7xx-y:= t7xx_pci.o \ t7xx_pcie_mac.o \
Signature · 1 line
2.39.2
Sasha Levin
maintainerPATCH 14/15 wifi: ath11k: reduce the MHI timeout to 20s
In reply to Sasha LevinFrom: Kalle Valo <[email protected]>
[ Upstream commit cf5fa3ca0552f1b7ba8490de40700bbfb6979b17 ]
Currently ath11k breaks after hibernation, the reason being that ath11k expects that the wireless device will have power during suspend and the firmware will continue running. But of course during hibernation the power from the device is cut off and firmware is not running when resuming, so ath11k will fail.
(The reason why ath11k needs the firmware running is the interaction between mac80211 and MHI stack, it's a long story and more info in the bugzilla report.)
In SUSE kernels the watchdog timeout is reduced from the default 120 to 60 seconds:
CONFIG_DPM_WATCHDOG_TIMEOUT=60
But as the ath11k MHI timeout is 90 seconds the kernel will crash before will ath11k will recover in resume callback. To avoid the crash reduce the MHI timeout to just 20 seconds.
Tested-on: WCN6855 hw2.0 PCI WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.9
--- drivers/net/wireless/ath/ath11k/mhi.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/net/wireless/ath/ath11k/mhi.c +1 -1
@@ -16,7 +16,7 @@#include "pci.h" #include "pcic.h" -#define MHI_TIMEOUT_DEFAULT_MS 90000 +#define MHI_TIMEOUT_DEFAULT_MS 20000#define RDDM_DUMP_SIZE 0x420000static struct mhi_channel_config ath11k_mhi_channels_qca6390[] = {
Signature · 7 lines
2.39.2 -- ath11k mailing list [email protected] http://lists.infradead.org/mailman/listinfo/ath11k
Sasha Levin
maintainerPATCH 1/15 ASOC: Intel: sof_sdw: add quirk for Intel 'Rooks County' NUC M15
From: Eugene Huang <[email protected]>
[ Upstream commit 3c728b1bc5b99c5275ac5c7788ef814c0e51ef54 ]
Same quirks as the 'Bishop County' NUC M15, except the rt711 is in the 'JD2 100K' jack detection mode.
--- sound/soc/intel/boards/sof_sdw.c | 11 +++++++++++ 1 file changed, 11 insertions(+)
sound/soc/intel/boards/sof_sdw.c +11 -0
@@ -213,6 +213,17 @@ static const struct dmi_system_id sof_sdw_quirk_table[] = {SOF_SDW_PCH_DMIC | RT711_JD1), }, + { +/* NUC15 'Rooks County' LAPRC510 and LAPRC710 skews */ + .callback = sof_sdw_quirk_cb, + .matches = { +DMI_MATCH (DMI_SYS_VENDOR ,"Intel(R) Client Systems" ), + DMI_MATCH(DMI_PRODUCT_NAME, "LAPRC"), + }, + .driver_data = (void *)(SOF_SDW_TGL_HDMI | +SOF_SDW_PCH_DMIC | + RT711_JD2_100K), + }, /* TigerLake-SDCA devices */ { .callback = sof_sdw_quirk_cb,
Signature · 1 line
2.39.2
Sasha Levin
maintainerPATCH 3/15 ASoC: soc-pcm: fix hw->formats cleared by soc_pcm_hw_init() for dpcm
From: Shengjiu Wang <[email protected]>
[ Upstream commit 083a25b18d6ad9f1f540e629909aa3eaaaf01823 ]
The hw->formats may be set by snd_dmaengine_pcm_refine_runtime_hwparams() in component's startup()/open(), but soc_pcm_hw_init() will init hw->formats in dpcm_runtime_setup_fe() after component's startup()/open(), which causes the valuable hw->formats to be cleared.
So need to store the hw->formats before initialization, then restore it after initialization.
--- sound/soc/soc-pcm.c | 4 ++++ 1 file changed, 4 insertions(+)
sound/soc/soc-pcm.c +4 -0
@@ -1649,10 +1649,14 @@ static void dpcm_runtime_setup_fe(struct snd_pcm_substream *substream)struct snd_pcm_hardware *hw = &runtime->hw;struct snd_soc_dai *dai;int stream = substream->stream; +u64 formats = hw->formats;int i;soc_pcm_hw_init (hw); +if (formats) + hw->formats &= formats; +for_each_rtd_cpu_dais (fe, i, dai) {struct snd_soc_pcm_stream *cpu_stream;
Signature · 1 line
2.39.2
Sasha Levin
maintainerPATCH 2/15 ASoC: Intel: soc-acpi: add table for Intel 'Rooks County' NUC M15
In reply to Sasha LevinFrom: Eugene Huang <[email protected]>
[ Upstream commit 9c691a42b8926c8966561265cdae3ddc7464d3a2 ]
Same topology as the HP Omen 16-k0005TX, except with the rt1316 amp on link2.
--- .../intel/common/soc-acpi-intel-adl-match.c | 20 +++++++++++++++++++ 1 file changed, 20 insertions(+)
sound/soc/intel/common/soc-acpi-intel-adl-match.c +20 -0
@@ -354,6 +354,20 @@ static const struct snd_soc_acpi_link_adr adl_sdw_rt711_link0_rt1316_link3[] = { {} }; +static const struct snd_soc_acpi_link_adr adl_sdw_rt711_link0_rt1316_link2[] = { + { + .mask =BIT (0 ), + .num_adr =ARRAY_SIZE (rt711_sdca_0_adr), + .adr_d = rt711_sdca_0_adr, + }, + { + .mask =BIT (2 ), + .num_adr =ARRAY_SIZE (rt1316_2_single_adr), + .adr_d = rt1316_2_single_adr, + }, + {} +}; +static const struct snd_soc_acpi_adr_device mx8373_2_adr[] = { { .adr =0x000223019F837300ull ,
@@ -612,6 +626,12 @@ struct snd_soc_acpi_mach snd_soc_acpi_intel_adl_sdw_machines[] = { .drv_name = "sof_sdw", .sof_tplg_filename = "sof-adl-rt711-l0-rt1316-l3.tplg", }, + { + .link_mask = 0x5, /* 2 active links required */ + .links = adl_sdw_rt711_link0_rt1316_link2, + .drv_name = "sof_sdw", + .sof_tplg_filename = "sof-adl-rt711-l0-rt1316-l2.tplg", + }, { .link_mask = 0x1, /* link0 required */ .links = adl_rvp,
Signature · 1 line
2.39.2
Sasha Levin
maintainerPATCH 4/15 x86/hyperv: Block root partition functionality in a Confidential VM
In reply to Sasha LevinFrom: Michael Kelley <[email protected]>
[ Upstream commit f8acb24aaf89fc46cd953229462ea8abe31b395f ]
Hyper-V should never specify a VM that is a Confidential VM and also running in the root partition. Nonetheless, explicitly block such a combination to guard against a compromised Hyper-V maliciously trying to exploit root partition functionality in a Confidential VM to expose Confidential VM secrets. No known bug is being fixed, but the attack surface for Confidential VMs on Hyper-V is reduced.
--- arch/x86/kernel/cpu/mshyperv.c | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-)
arch/x86/kernel/cpu/mshyperv.c +8 -4
@@ -291,12 +291,16 @@ static void __init ms_hyperv_init_platform(void)* To mirror what Windows does we should extract CPU management * features and use the ReservedIdentityBit to detect if Linux is the * root partition. But that requires negotiating CPU management -* interface (a process to be finalized). +* interface (a process to be finalized). For now, use the privilege +* flag as the indicator for running as root. * -* For now, use the privilege flag as the indicator for running as -* root. +* Hyper-V should never specify running as root and as a Confidential +* VM. But to protect against a compromised/malicious Hyper-V trying +* to exploit root behavior to expose Confidential VM memory, ignore +* the root partition setting if also a Confidential VM. */ -if (cpuid_ebx (HYPERV_CPUID_FEATURES ) &HV_CPU_MANAGEMENT ) { +if ((ms_hyperv.priv_high &HV_CPU_MANAGEMENT ) && + !(ms_hyperv.priv_high &HV_ISOLATION )) { hv_root_partition = true;pr_info ("Hyper-V: running as root partition\n" ); }
Signature · 1 line
2.39.2
Sasha Levin
maintainerPATCH 5/15 ASoC: amd: yc: Add DMI entries to support Victus by HP Laptop 16-e1xxx (8A22)
In reply to Sasha LevinFrom: Ge-org Brohammer <[email protected]>
[ Upstream commit 205efd4619b860404ebb5882e5a119eb3b3b3716 ]
This model requires an additional detection quirk to enable the internal microphone.
Tried to use git send-email this time.
--- sound/soc/amd/yc/acp6x-mach.c | 7 +++++++ 1 file changed, 7 insertions(+)
sound/soc/amd/yc/acp6x-mach.c +7 -0
@@ -269,6 +269,13 @@ static const struct dmi_system_id yc_acp_quirk_table[] = { DMI_MATCH(DMI_BOARD_NAME, "8A43"), } }, + { + .driver_data = &acp6x_card, + .matches = { + DMI_MATCH(DMI_BOARD_VENDOR, "HP"), + DMI_MATCH(DMI_BOARD_NAME, "8A22"), + } + }, {} };
Signature · 1 line
2.39.2
Sasha Levin
maintainerPATCH 7/15 ASoC: Intel: bytcr_rt5640: Add quirk for the Acer Iconia One 7 B1-750
In reply to Sasha LevinFrom: Hans de Goede <[email protected]>
[ Upstream commit e38c5e80c3d293a883c6f1d553f2146ec0bda35e ]
The Acer Iconia One 7 B1-750 tablet mostly works fine with the defaults for an Bay Trail CR tablet. Except for the internal mic, instead of an analog mic on IN3 a digital mic on DMIC1 is uses.
Add a quirk with these settings for this tablet.
--- sound/soc/intel/boards/bytcr_rt5640.c | 12 ++++++++++++ 1 file changed, 12 insertions(+)
sound/soc/intel/boards/bytcr_rt5640.c +12 -0
@@ -533,6 +533,18 @@ static int byt_rt5640_aif1_hw_params(struct snd_pcm_substream *substream,/* Please keep this list alphabetically sorted */ static const struct dmi_system_id byt_rt5640_quirk_table[] = { + {/* Acer Iconia One 7 B1-750 */ + .matches = { +DMI_EXACT_MATCH (DMI_SYS_VENDOR ,"Insyde" ), +DMI_EXACT_MATCH (DMI_PRODUCT_NAME ,"VESPA2" ), + }, + .driver_data = (void *)(BYT_RT5640_DMIC1_MAP | +BYT_RT5640_JD_SRC_JD1_IN4P | +BYT_RT5640_OVCD_TH_1500UA | +BYT_RT5640_OVCD_SF_0P75 | +BYT_RT5640_SSP0_AIF1 | +BYT_RT5640_MCLK_EN ), + }, {/* Acer Iconia Tab 8 W1-810 */ .matches = {DMI_EXACT_MATCH (DMI_SYS_VENDOR ,"Acer" ),
Signature · 1 line
2.39.2
Sasha Levin
maintainerPATCH 8/15 ASoC: da7213.c: add missing pm_runtime_disable()
In reply to Sasha LevinFrom: Duy Nguyen <[email protected]>
[ Upstream commit 44378cd113e5f15bb0a89f5ac5a0e687b52feb90 ]
da7213.c is missing pm_runtime_disable(), thus we will get below error when rmmod -> insmod.
$ rmmod snd-soc-da7213.ko $ insmod snd-soc-da7213.ko da7213 0-001a: Unbalanced pm_runtime_enable!"
[Kuninori adjusted to latest upstream]
--- sound/soc/codecs/da7213.c | 6 ++++++ 1 file changed, 6 insertions(+)
sound/soc/codecs/da7213.c +6 -0
@@ -1996,6 +1996,11 @@ static int da7213_i2c_probe(struct i2c_client *i2c)return ret; } +static void da7213_i2c_remove (struct i2c_client *i2c) +{ +pm_runtime_disable (&i2c->dev); +} +static int __maybe_unused da7213_runtime_suspend (struct device *dev) {struct da7213_priv *da7213 =dev_get_drvdata (dev);
@@ -2039,6 +2044,7 @@ static struct i2c_driver da7213_i2c_driver = { .pm = &da7213_pm, }, .probe_new = da7213_i2c_probe, + .remove = da7213_i2c_remove, .id_table = da7213_i2c_id, };
Signature · 1 line
2.39.2
Sasha Levin
maintainerPATCH 6/15 iio: adc: palmas_gpadc: fix NULL dereference on rmmod
In reply to Sasha LevinFrom: Patrik Dahlström <[email protected]>
[ Upstream commit 49f76c499d38bf67803438eee88c8300d0f6ce09 ]
Calling dev_to_iio_dev() on a platform device pointer is undefined and will make adc NULL.
--- drivers/iio/adc/palmas_gpadc.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/iio/adc/palmas_gpadc.c +1 -1
@@ -639,7 +639,7 @@ static int palmas_gpadc_probe(struct platform_device *pdev)static int palmas_gpadc_remove (struct platform_device *pdev) { -struct iio_dev *indio_dev =dev_to_iio_dev (&pdev->dev); +struct iio_dev *indio_dev =dev_get_drvdata (&pdev->dev);struct palmas_gpadc *adc =iio_priv (indio_dev);if (adc->wakeup1_enable || adc->wakeup2_enable)
Signature · 1 line
2.39.2
Sasha Levin
maintainerPATCH 10/15 selftests mount: Fix mount_setattr_test builds failed
In reply to Sasha LevinFrom: Anh Tuan Phan <[email protected]>
[ Upstream commit f1594bc676579133a3cd906d7d27733289edfb86 ]
When compiling selftests with target mount_setattr I encountered some errors with the below messages:mount_setattr_test.c: In function ‘mount_setattr_thread’:
mount_setattr_test.c:343:16: error: variable ‘attr’ has initializer but incomplete type
343 | struct mount_attr attr = {
| ^~~~~~~~~~These errors might be because of linux/mount.h is not included. This patch resolves that issue.
--- tools/testing/selftests/mount_setattr/mount_setattr_test.c | 1 + 1 file changed, 1 insertion(+)
tools/testing/selftests/mount_setattr/mount_setattr_test.c +1 -0
@@ -18,6 +18,7 @@#include <grp.h> #include <stdbool.h> #include <stdarg.h> +#include <linux/mount.h> #include "../kselftest_harness.h"
Signature · 1 line
2.39.2
Sasha Levin
maintainerPATCH 11/15 scsi: mpi3mr: Handle soft reset in progress fault code (0xF002)
In reply to Sasha LevinFrom: Ranjan Kumar <[email protected]>
[ Upstream commit a3d27dfdcfc27ac3f46de5391bb6d24f04af7941 ]
The driver is exiting from the fault watchdog thread if it sees the 0xF002 (Soft reset in progress) fault code.
If the driver initiates the soft reset, then the driver restarts the watchdog at the end of the soft reset completion. However, if the soft reset is initiated by the firmware asynchronously, then the driver will never restart the watchdog and never re-initialize the controller after the asynchronous soft reset completion.
--- drivers/scsi/mpi3mr/mpi3mr_fw.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/scsi/mpi3mr/mpi3mr_fw.c +1 -1
@@ -2526,7 +2526,7 @@ static void mpi3mr_watchdog_work(struct work_struct *work) mrioc->unrecoverable =1 ; goto schedule_work;case MPI3_SYSIF_FAULT_CODE_SOFT_RESET_IN_PROGRESS : -return ; + goto schedule_work;case MPI3_SYSIF_FAULT_CODE_CI_ACTIVATION_RESET : reset_reason =MPI3MR_RESET_FROM_CIACTIV_FAULT ;break ;
Signature · 1 line
2.39.2
Sasha Levin
maintainerPATCH 12/15 net: sfp: add quirk enabling 2500Base-x for HG MXPD-483II
In reply to Sasha LevinFrom: Daniel Golle <[email protected]>
[ Upstream commit ad651d68cee75e9ac20002254c4e5d09ee67a84b ]
The HG MXPD-483II 1310nm SFP module is meant to operate with 2500Base-X, however, in their EEPROM they incorrectly specify:
Transceiver type : Ethernet: 1000BASE-LX
...
BR, Nominal : 2600MBd
Use sfp_quirk_2500basex for this module to allow 2500Base-X mode anyway.
https://forum.banana-pi.org/t/bpi-r3-sfp-module-compatibility/14573/60
--- drivers/net/phy/sfp.c | 4 ++++ 1 file changed, 4 insertions(+)
drivers/net/phy/sfp.c +4 -0
@@ -389,6 +389,10 @@ static const struct sfp_quirk sfp_quirks[] = {SFP_QUIRK_F ("HALNy" ,"HL-GSFP" , sfp_fixup_halny_gsfp), +// HG MXPD-483II-F 2.5G supports 2500Base-X, but incorrectly reports +// 2600MBd in their EERPOM +SFP_QUIRK_M ("HG GENUINE" ,"MXPD-483II" , sfp_quirk_2500basex), +// Huawei MA5671A can operate at 2500base-X, but report 1.2GBd NRZ in // their EEPROM SFP_QUIRK("HUAWEI", "MA5671A", sfp_quirk_2500basex,
Signature · 1 line
2.39.2
Sasha Levin
maintainerPATCH 13/15 platform/x86: thinkpad_acpi: Add missing T14s Gen1 type to s2idle quirk list
In reply to Sasha LevinFrom: Benjamin Asbach <[email protected]>
[ Upstream commit 9a469c6dfab38326f99f105386db84230be09ee3 ]
From the commit message adding the first s2idle quirks:
Quoted 7 lines
Lenovo laptops that contain NVME SSDs across a variety of generations have trouble resuming from suspend to idle when the IOMMU translation layer is active for the NVME storage device.
This generally manifests as a large resume delay or page faults. These delays and page faults occur as a result of a Lenovo BIOS specific SMI that runs during the
D3->D0transition on NVME devices.
Add the DMI ids for another variant of the T14s Gen1, which also needs the s2idle quirk.
--- drivers/platform/x86/thinkpad_acpi.c | 8 ++++++++ 1 file changed, 8 insertions(+)
drivers/platform/x86/thinkpad_acpi.c +8 -0
@@ -4481,6 +4481,14 @@ static const struct dmi_system_id fwbug_list[] __initconst = { DMI_MATCH(DMI_PRODUCT_NAME, "20UH"), } }, + { + .ident = "T14s Gen1 AMD", + .driver_data = &quirk_s2idle_bug, + .matches = { +DMI_MATCH (DMI_BOARD_VENDOR ,"LENOVO" ), + DMI_MATCH(DMI_PRODUCT_NAME, "20UJ"), + } + }, { .ident ="P14s Gen1 AMD" , .driver_data = &quirk_s2idle_bug,
Signature · 1 line
2.39.2
Sasha Levin
maintainerPATCH 15/15 x86/cpu: Add model number for Intel Arrow Lake processor
In reply to Sasha LevinFrom: Tony Luck <[email protected]>
[ Upstream commit 81515ecf155a38f3532bf5ddef88d651898df6be ]
Successor to Lunar Lake.
--- arch/x86/include/asm/intel-family.h | 2 ++ 1 file changed, 2 insertions(+)
arch/x86/include/asm/intel-family.h +2 -0
@@ -125,6 +125,8 @@#define INTEL_FAM6_LUNARLAKE_M 0xBD +#define INTEL_FAM6_ARROWLAKE 0xC6 +/* "Small Core" Processors (Atom/E-Core) */ #define INTEL_FAM6_ATOM_BONNELL 0x1C/* Diamondville, Pineview */
Signature · 1 line
2.39.2