Changelog in Linux kernel 6.10.12

 
accel: Use XArray instead of IDR for minors [+ + +]
Author: Michał Winiarski <michal.winiarski@intel.com>
Date:   Fri Aug 23 18:30:47 2024 +0200

    accel: Use XArray instead of IDR for minors
    
    [ Upstream commit 45c4d994b82b08f0ce5eb50f8da29379c92a391e ]
    
    Accel minor management is based on DRM (and is also using struct
    drm_minor internally), since DRM is using XArray for minors, it makes
    sense to also convert accel.
    As the two implementations are identical (only difference being the
    underlying xarray), move the accel_minor_* functionality to DRM.
    
    Signed-off-by: Michał Winiarski <michal.winiarski@intel.com>
    Acked-by: James Zhu <James.Zhu@amd.com>
    Acked-by: Christian König <christian.koenig@amd.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20240823163048.2676257-3-michal.winiarski@intel.com
    Signed-off-by: Christian König <christian.koenig@amd.com>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 
ALSA: hda/realtek - Fixed ALC256 headphone no sound [+ + +]
Author: Kailang Yang <kailang@realtek.com>
Date:   Thu Aug 22 10:54:19 2024 +0800

    ALSA: hda/realtek - Fixed ALC256 headphone no sound
    
    [ Upstream commit 9b82ff1362f50914c8292902e07be98a9f59d33d ]
    
    Dell platform, plug headphone or headset, it had a chance to get no
    sound from headphone.
    Replace depop procedure will solve this issue.
    
    Signed-off-by: Kailang Yang <kailang@realtek.com>
    Link: https://lore.kernel.org/bb8e2de30d294dc287944efa0667685a@realtek.com
    Signed-off-by: Takashi Iwai <tiwai@suse.de>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

ALSA: hda/realtek - FIxed ALC285 headphone no sound [+ + +]
Author: Kailang Yang <kailang@realtek.com>
Date:   Thu Aug 22 16:46:56 2024 +0800

    ALSA: hda/realtek - FIxed ALC285 headphone no sound
    
    [ Upstream commit 1fa7b099d60ad64f559bd3b8e3f0d94b2e015514 ]
    
    Dell platform with ALC215 ALC285 ALC289 ALC225 ALC295 ALC299, plug
    headphone or headset.
    It had a chance to get no sound from headphone.
    Replace depop procedure will solve this issue.
    
    Signed-off-by: Kailang Yang <kailang@realtek.com>
    Link: https://lore.kernel.org/d0de1b03fd174520945dde216d765223@realtek.com
    Signed-off-by: Takashi Iwai <tiwai@suse.de>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

ALSA: hda: add HDMI codec ID for Intel PTL [+ + +]
Author: Kai Vehmanen <kai.vehmanen@linux.intel.com>
Date:   Fri Aug 30 15:24:58 2024 +0800

    ALSA: hda: add HDMI codec ID for Intel PTL
    
    [ Upstream commit e9481d9b83f8d9b3251aa428b02d8eba89d839ff ]
    
    Add HDMI codec ID for Intel Panther Lake platform.
    
    Signed-off-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>
    Reviewed-by: Péter Ujfalusi <peter.ujfalusi@linux.intel.com>
    Reviewed-by: Ranjani Sridharan <ranjani.sridharan@linux.intel.com>
    Signed-off-by: Bard Liao <yung-chuan.liao@linux.intel.com>
    Link: https://patch.msgid.link/20240830072458.110831-1-yung-chuan.liao@linux.intel.com
    Signed-off-by: Takashi Iwai <tiwai@suse.de>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 
ASoC: allow module autoloading for table board_ids [+ + +]
Author: Hongbo Li <lihongbo22@huawei.com>
Date:   Wed Aug 21 14:19:55 2024 +0800

    ASoC: allow module autoloading for table board_ids
    
    [ Upstream commit 5f7c98b7519a3a847d9182bd99d57ea250032ca1 ]
    
    Add MODULE_DEVICE_TABLE(), so modules could be properly
    autoloaded based on the alias from platform_device_id table.
    
    Signed-off-by: Hongbo Li <lihongbo22@huawei.com>
    Link: https://patch.msgid.link/20240821061955.2273782-3-lihongbo22@huawei.com
    Signed-off-by: Mark Brown <broonie@kernel.org>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

ASoC: allow module autoloading for table db1200_pids [+ + +]
Author: Hongbo Li <lihongbo22@huawei.com>
Date:   Wed Aug 21 14:19:54 2024 +0800

    ASoC: allow module autoloading for table db1200_pids
    
    [ Upstream commit 0e9fdab1e8df490354562187cdbb8dec643eae2c ]
    
    Add MODULE_DEVICE_TABLE(), so modules could be properly
    autoloaded based on the alias from platform_device_id table.
    
    Signed-off-by: Hongbo Li <lihongbo22@huawei.com>
    Link: https://patch.msgid.link/20240821061955.2273782-2-lihongbo22@huawei.com
    Signed-off-by: Mark Brown <broonie@kernel.org>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

ASoC: amd: yc: Add a quirk for MSI Bravo 17 (D7VEK) [+ + +]
Author: Markuss Broks <markuss.broks@gmail.com>
Date:   Thu Aug 29 16:03:05 2024 +0300

    ASoC: amd: yc: Add a quirk for MSI Bravo 17 (D7VEK)
    
    [ Upstream commit 283844c35529300c8e10f7a263e35e3c5d3580ac ]
    
    MSI Bravo 17 (D7VEK), like other laptops from the family,
    has broken ACPI tables and needs a quirk for internal mic
    to work.
    
    Signed-off-by: Markuss Broks <markuss.broks@gmail.com>
    Link: https://patch.msgid.link/20240829130313.338508-1-markuss.broks@gmail.com
    Signed-off-by: Mark Brown <broonie@kernel.org>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

ASoC: fix module autoloading [+ + +]
Author: Liao Chen <liaochen4@huawei.com>
Date:   Mon Aug 26 08:49:24 2024 +0000

    ASoC: fix module autoloading
    
    [ Upstream commit 6ba20539ac6b12ea757b3bfe11adf8de1672d7b8 ]
    
    Add MODULE_DEVICE_TABLE(), so modules could be properly autoloaded
    based on the alias from of_device_id table.
    
    Signed-off-by: Liao Chen <liaochen4@huawei.com>
    Link: https://patch.msgid.link/20240826084924.368387-5-liaochen4@huawei.com
    Signed-off-by: Mark Brown <broonie@kernel.org>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

ASoC: google: fix module autoloading [+ + +]
Author: Liao Chen <liaochen4@huawei.com>
Date:   Mon Aug 26 08:49:22 2024 +0000

    ASoC: google: fix module autoloading
    
    [ Upstream commit 8e1bb4a41aa78d6105e59186af3dcd545fc66e70 ]
    
    Add MODULE_DEVICE_TABLE(), so modules could be properly autoloaded
    based on the alias from of_device_id table.
    
    Signed-off-by: Liao Chen <liaochen4@huawei.com>
    Link: https://patch.msgid.link/20240826084924.368387-3-liaochen4@huawei.com
    Signed-off-by: Mark Brown <broonie@kernel.org>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

ASoC: intel: fix module autoloading [+ + +]
Author: Liao Chen <liaochen4@huawei.com>
Date:   Mon Aug 26 08:49:21 2024 +0000

    ASoC: intel: fix module autoloading
    
    [ Upstream commit ae61a3391088d29aa8605c9f2db84295ab993a49 ]
    
    Add MODULE_DEVICE_TABLE(), so modules could be properly autoloaded
    based on the alias from of_device_id table.
    
    Signed-off-by: Liao Chen <liaochen4@huawei.com>
    Link: https://patch.msgid.link/20240826084924.368387-2-liaochen4@huawei.com
    Signed-off-by: Mark Brown <broonie@kernel.org>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

ASoC: Intel: soc-acpi-cht: Make Lenovo Yoga Tab 3 X90F DMI match less strict [+ + +]
Author: Hans de Goede <hdegoede@redhat.com>
Date:   Fri Aug 23 09:43:05 2024 +0200

    ASoC: Intel: soc-acpi-cht: Make Lenovo Yoga Tab 3 X90F DMI match less strict
    
    [ Upstream commit 839a4ec06f75cec8fec2cc5fc14e921d0c3f7369 ]
    
    There are 2G and 4G RAM versions of the Lenovo Yoga Tab 3 X90F and it
    turns out that the 2G version has a DMI product name of
    "CHERRYVIEW D1 PLATFORM" where as the 4G version has
    "CHERRYVIEW C0 PLATFORM". The sys-vendor + product-version check are
    unique enough that the product-name check is not necessary.
    
    Drop the product-name check so that the existing DMI match for the 4G
    RAM version also matches the 2G RAM version.
    
    Signed-off-by: Hans de Goede <hdegoede@redhat.com>
    Reviewed-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
    Link: https://patch.msgid.link/20240823074305.16873-1-hdegoede@redhat.com
    Signed-off-by: Mark Brown <broonie@kernel.org>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

ASoC: mediatek: mt8188-mt6359: Modify key [+ + +]
Author: Zhang Yi <zhangyi@everest-semi.com>
Date:   Fri Aug 16 19:49:21 2024 +0800

    ASoC: mediatek: mt8188-mt6359: Modify key
    
    [ Upstream commit 5325b96769a5b282e330023e1d0881018e89e266 ]
    
    In order to get the correct keys when using the ES8326.We will associate
    SND_JACK_BTN_1 to KEY_VOLUMEUP and SND_JACK_BTN_2 to KEY_VOLUMEDOWN
    when the ES8326 flag is recognized.
    
    Signed-off-by: Zhang Yi <zhangyi@everest-semi.com>
    Link: https://patch.msgid.link/20240816114921.48913-1-zhangyi@everest-semi.com
    Signed-off-by: Mark Brown <broonie@kernel.org>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

ASoC: mediatek: mt8188: Mark AFE_DAC_CON0 register as volatile [+ + +]
Author: YR Yang <yr.yang@mediatek.com>
Date:   Thu Aug 1 16:43:26 2024 +0800

    ASoC: mediatek: mt8188: Mark AFE_DAC_CON0 register as volatile
    
    [ Upstream commit ff9f065318e17a1a97981d9e535fcfc6ce5d5614 ]
    
    Add AFE Control Register 0 to the volatile_register.
    AFE_DAC_CON0 can be modified by both the SOF and ALSA drivers.
    If this register is read and written in cache mode, the cached value
    might not reflect the actual value when the register is modified by
    another driver. It can cause playback or capture failures. Therefore,
    it is necessary to add AFE_DAC_CON0 to the list of volatile registers.
    
    Signed-off-by: YR Yang <yr.yang@mediatek.com>
    Reviewed-by: Fei Shao <fshao@chromium.org>
    Reviewed-by: Trevor Wu <trevor.wu@mediatek.com>
    Link: https://patch.msgid.link/20240801084326.1472-1-yr.yang@mediatek.com
    Signed-off-by: Mark Brown <broonie@kernel.org>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

ASoC: SOF: mediatek: Add missing board compatible [+ + +]
Author: Albert Jakieła <jakiela@google.com>
Date:   Fri Aug 9 13:56:27 2024 +0000

    ASoC: SOF: mediatek: Add missing board compatible
    
    [ Upstream commit c0196faaa927321a63e680427e075734ee656e42 ]
    
    Add Google Dojo compatible.
    
    Signed-off-by: Albert Jakieła <jakiela@google.com>
    Reviewed-by: Chen-Yu Tsai <wenst@chromium.org>
    Link: https://patch.msgid.link/20240809135627.544429-1-jakiela@google.com
    Signed-off-by: Mark Brown <broonie@kernel.org>
    Signed-off-by: Sasha Levin <sashal@kernel.org>
ASoC: tda7419: fix module autoloading [+ + +]
Author: Liao Chen <liaochen4@huawei.com>
Date:   Mon Aug 26 08:49:23 2024 +0000

    ASoC: tda7419: fix module autoloading
    
    [ Upstream commit 934b44589da9aa300201a00fe139c5c54f421563 ]
    
    Add MODULE_DEVICE_TABLE(), so modules could be properly autoloaded
    based on the alias from of_device_id table.
    
    Signed-off-by: Liao Chen <liaochen4@huawei.com>
    Link: https://patch.msgid.link/20240826084924.368387-4-liaochen4@huawei.com
    Signed-off-by: Mark Brown <broonie@kernel.org>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 
Bluetooth: btintel_pcie: Allocate memory for driver private data [+ + +]
Author: Kiran K <kiran.k@intel.com>
Date:   Thu Sep 12 16:21:00 2024 +0530

    Bluetooth: btintel_pcie: Allocate memory for driver private data
    
    commit 7ffaa200251871980af12e57649ad57c70bf0f43 upstream.
    
    Fix driver not allocating memory for struct btintel_data which is used
    to store internal data.
    
    Fixes: 6e65a09f9275 ("Bluetooth: btintel_pcie: Add *setup* function to download firmware")
    Signed-off-by: Kiran K <kiran.k@intel.com>
    Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
    Cc: Thomas Leroy <thomas.leroy@suse.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

 
can: m_can: Limit coalescing to peripheral instances [+ + +]
Author: Markus Schneider-Pargmann <msp@baylibre.com>
Date:   Mon Aug 5 20:30:47 2024 +0200

    can: m_can: Limit coalescing to peripheral instances
    
    [ Upstream commit e443d15b949952ee039b731d5c35bcbafa300024 ]
    
    The use of coalescing for non-peripheral chips in the current
    implementation is limited to non-existing. Disable the possibility to
    set coalescing through ethtool.
    
    Signed-off-by: Markus Schneider-Pargmann <msp@baylibre.com>
    Link: https://lore.kernel.org/all/20240805183047.305630-8-msp@baylibre.com
    Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

can: mcp251xfd: mcp251xfd_ring_init(): check TX-coalescing configuration [+ + +]
Author: Marc Kleine-Budde <mkl@pengutronix.de>
Date:   Fri Jul 5 17:24:42 2024 +0200

    can: mcp251xfd: mcp251xfd_ring_init(): check TX-coalescing configuration
    
    [ Upstream commit ac2b81eb8b2d104033560daea886ee84531e3d0a ]
    
    When changing the interface from CAN-CC to CAN-FD mode the old
    coalescing parameters are re-used. This might cause problem, as the
    configured parameters are too big for CAN-FD mode.
    
    During testing an invalid TX coalescing configuration has been seen.
    The problem should be been fixed in the previous patch, but add a
    safeguard here to ensure that the number of TEF coalescing buffers (if
    configured) is exactly the half of all TEF buffers.
    
    Link: https://lore.kernel.org/all/20240805-mcp251xfd-fix-ringconfig-v1-2-72086f0ca5ee@pengutronix.de
    Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

can: mcp251xfd: move mcp251xfd_timestamp_start()/stop() into mcp251xfd_chip_start/stop() [+ + +]
Author: Marc Kleine-Budde <mkl@pengutronix.de>
Date:   Wed Jan 11 12:10:04 2023 +0100

    can: mcp251xfd: move mcp251xfd_timestamp_start()/stop() into mcp251xfd_chip_start/stop()
    
    commit a7801540f325d104de5065850a003f1d9bdc6ad3 upstream.
    
    The mcp251xfd wakes up from Low Power or Sleep Mode when SPI activity
    is detected. To avoid this, make sure that the timestamp worker is
    stopped before shutting down the chip.
    
    Split the starting of the timestamp worker out of
    mcp251xfd_timestamp_init() into the separate function
    mcp251xfd_timestamp_start().
    
    Call mcp251xfd_timestamp_init() before mcp251xfd_chip_start(), move
    mcp251xfd_timestamp_start() to mcp251xfd_chip_start(). In this way,
    mcp251xfd_timestamp_stop() can be called unconditionally by
    mcp251xfd_chip_stop().
    
    Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

can: mcp251xfd: properly indent labels [+ + +]
Author: Marc Kleine-Budde <mkl@pengutronix.de>
Date:   Thu Apr 25 10:14:45 2024 +0200

    can: mcp251xfd: properly indent labels
    
    commit 51b2a721612236335ddec4f3fb5f59e72a204f3a upstream.
    
    To fix the coding style, remove the whitespace in front of labels.
    
    Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

 
clk: qcom: gcc-sm8650: Don't use shared clk_ops for QUPs [+ + +]
Author: Neil Armstrong <neil.armstrong@linaro.org>
Date:   Thu Aug 29 10:44:30 2024 +0200

    clk: qcom: gcc-sm8650: Don't use shared clk_ops for QUPs
    
    [ Upstream commit aa2eb2c4356affa2799efd95a4ee2d239ca630f8 ]
    
    The QUPs aren't shared in a way that requires parking the RCG at an
    always on parent in case some other entity turns on the clk. The
    hardware is capable of setting a new frequency itself with the DFS mode,
    so parking is unnecessary. Furthermore, there aren't any GDSCs for these
    devices, so there isn't a possibility of the GDSC turning on the clks
    for housekeeping purposes.
    
    Like for the SM8550 GCC QUP clocks at [1], do not use shared clk_ops for QUPs.
    
    [1] https://lore.kernel.org/all/20240827231237.1014813-3-swboyd@chromium.org/
    
    Signed-off-by: Neil Armstrong <neil.armstrong@linaro.org>
    Link: https://lore.kernel.org/r/20240829-topic-sm8650-upstream-fix-qup-clk-rcg-shared-v1-1-7ecdbc672187@linaro.org
    Signed-off-by: Stephen Boyd <sboyd@kernel.org>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 
drm/amd/pm: fix the pp_dpm_pcie issue on smu v14.0.2/3 [+ + +]
Author: Kenneth Feng <kenneth.feng@amd.com>
Date:   Fri Sep 6 20:46:54 2024 +0800

    drm/amd/pm: fix the pp_dpm_pcie issue on smu v14.0.2/3
    
    [ Upstream commit 7a0982523cf3ff00f35b210fc3405c528a2ce7af ]
    
    fix the pp_dpm_pcie issue on smu v14.0.2/3 as below:
    0: 2.5GT/s, x4 250Mhz
    1: 8.0GT/s, x4 616Mhz *
    2: 8.0GT/s, x4 1143Mhz *
    the middle level can be removed since it is always skipped on
    smu v14.0.2/3
    
    Signed-off-by: Kenneth Feng <kenneth.feng@amd.com>
    Acked-by: Alex Deucher <alexander.deucher@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
    (cherry picked from commit fedf6db3ea9dc5eda0b78cfbbb8f7a88b97e5b24)
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 
drm: Expand max DRM device number to full MINORBITS [+ + +]
Author: Michał Winiarski <michal.winiarski@intel.com>
Date:   Fri Aug 23 18:30:48 2024 +0200

    drm: Expand max DRM device number to full MINORBITS
    
    [ Upstream commit 071d583e01c88272f6ff216d4f867f8f35e94d7d ]
    
    Having a limit of 64 DRM devices is not good enough for modern world
    where we have multi-GPU servers, SR-IOV virtual functions and virtual
    devices used for testing.
    Let's utilize full minor range for DRM devices.
    To avoid regressing the existing userspace, we're still maintaining the
    numbering scheme where 0-63 is used for primary, 64-127 is reserved
    (formerly for control) and 128-191 is used for render.
    For minors >= 192, we're allocating minors dynamically on a first-come,
    first-served basis.
    
    Signed-off-by: Michał Winiarski <michal.winiarski@intel.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20240823163048.2676257-4-michal.winiarski@intel.com
    Acked-by: James Zhu <James.Zhu@amd.com>
    Acked-by: Christian König <christian.koenig@amd.com>
    Signed-off-by: Christian König <christian.koenig@amd.com>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

drm: komeda: Fix an issue related to normalized zpos [+ + +]
Author: hongchi.peng <hongchi.peng@siengine.com>
Date:   Mon Aug 26 10:45:17 2024 +0800

    drm: komeda: Fix an issue related to normalized zpos
    
    [ Upstream commit 258905cb9a6414be5c9ca4aa20ef855f8dc894d4 ]
    
    We use komeda_crtc_normalize_zpos to normalize zpos of affected planes
    to their blending zorder in CU. If there's only one slave plane in
    affected planes and its layer_split property is enabled, order++ for
    its split layer, so that when calculating the normalized_zpos
    of master planes, the split layer of the slave plane is included, but
    the max_slave_zorder does not include the split layer and keep zero
    because there's only one slave plane in affacted planes, although we
    actually use two slave layers in this commit.
    
    In most cases, this bug does not result in a commit failure, but assume
    the following situation:
        slave_layer 0: zpos = 0, layer split enabled, normalized_zpos =
        0;(use slave_layer 2 as its split layer)
        master_layer 0: zpos = 2, layer_split enabled, normalized_zpos =
        2;(use master_layer 2 as its split layer)
        master_layer 1: zpos = 4, normalized_zpos = 4;
        master_layer 3: zpos = 5, normalized_zpos = 5;
        kcrtc_st->max_slave_zorder = 0;
    When we use master_layer 3 as a input of CU in function
    komeda_compiz_set_input and check it with function
    komeda_component_check_input, the parameter idx is equal to
    normailzed_zpos minus max_slave_zorder, the value of idx is 5
    and is euqal to CU's max_active_inputs, so that
    komeda_component_check_input returns a -EINVAL value.
    
    To fix the bug described above, when calculating the max_slave_zorder
    with the layer_split enabled, count the split layer in this calculation
    directly.
    
    Signed-off-by: hongchi.peng <hongchi.peng@siengine.com>
    Acked-by: Liviu Dudau <liviu.dudau@arm.com>
    Signed-off-by: Liviu Dudau <liviu.dudau@arm.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20240826024517.3739-1-hongchi.peng@siengine.com
    Signed-off-by: Sasha Levin <sashal@kernel.org>

drm: Use XArray instead of IDR for minors [+ + +]
Author: Michał Winiarski <michal.winiarski@intel.com>
Date:   Fri Aug 23 18:30:46 2024 +0200

    drm: Use XArray instead of IDR for minors
    
    [ Upstream commit 5fbca8b48b3050ae7fb611a8b09af60012ed6de1 ]
    
    IDR is deprecated, and since XArray manages its own state with internal
    locking, it simplifies the locking on DRM side.
    Additionally, don't use the IRQ-safe variant, since operating on drm
    minor is not done in IRQ context.
    
    Suggested-by: Matthew Wilcox <willy@infradead.org>
    Signed-off-by: Michał Winiarski <michal.winiarski@intel.com>
    Acked-by: James Zhu <James.Zhu@amd.com>
    Acked-by: Christian König <christian.koenig@amd.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20240823163048.2676257-2-michal.winiarski@intel.com
    Signed-off-by: Christian König <christian.koenig@amd.com>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 
hwmon: (asus-ec-sensors) remove VRM temp X570-E GAMING [+ + +]
Author: Ross Brown <true.robot.ross@gmail.com>
Date:   Tue Jul 30 08:21:42 2024 +0200

    hwmon: (asus-ec-sensors) remove VRM temp X570-E GAMING
    
    [ Upstream commit 9efaebc0072b8e95505544bf385c20ee8a29d799 ]
    
    X570-E GAMING does not have VRM temperature sensor.
    
    Signed-off-by: Ross Brown <true.robot.ross@gmail.com>
    Signed-off-by: Eugene Shalygin <eugene.shalygin@gmail.com>
    Link: https://lore.kernel.org/r/20240730062320.5188-2-eugene.shalygin@gmail.com
    Signed-off-by: Guenter Roeck <linux@roeck-us.net>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 
ice: check for XDP rings instead of bpf program when unconfiguring [+ + +]
Author: Larysa Zaremba <larysa.zaremba@intel.com>
Date:   Fri Aug 23 11:59:28 2024 +0200

    ice: check for XDP rings instead of bpf program when unconfiguring
    
    [ Upstream commit f50c68763436bc8f805712a7c5ceaf58cfcf5f07 ]
    
    If VSI rebuild is pending, .ndo_bpf() can attach/detach the XDP program on
    VSI without applying new ring configuration. When unconfiguring the VSI, we
    can encounter the state in which there is an XDP program but no XDP rings
    to destroy or there will be XDP rings that need to be destroyed, but no XDP
    program to indicate their presence.
    
    When unconfiguring, rely on the presence of XDP rings rather then XDP
    program, as they better represent the current state that has to be
    destroyed.
    
    Reviewed-by: Wojciech Drewek <wojciech.drewek@intel.com>
    Reviewed-by: Jacob Keller <jacob.e.keller@intel.com>
    Tested-by: Chandan Kumar Rout <chandanx.rout@intel.com>
    Acked-by: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
    Signed-off-by: Larysa Zaremba <larysa.zaremba@intel.com>
    Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 
Linux: Linux 6.10.12 [+ + +]
Author: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Date:   Mon Sep 30 16:29:34 2024 +0200

    Linux 6.10.12
    
    Link: https://lore.kernel.org/r/20240927121718.789211866@linuxfoundation.org
    Tested-by: Allen Pais <apais@linux.microsoft.com>
    Tested-by: Peter Schneider <pschneider1968@googlemail.com>
    Tested-by: Jon Hunter <jonathanh@nvidia.com>
    Tested-by: Florian Fainelli <florian.fainelli@broadcom.com>
    Tested-by: Salvatore Bonaccorso <carnil@debian.org>
    Tested-by: Linux Kernel Functional Testing <lkft@linaro.org>
    Tested-by: Shuah Khan <skhan@linuxfoundation.org>
    Tested-by: Ron Economos <re@w6rz.net>
    Tested-by: Kexy Biscuit <kexybiscuit@aosc.io>
    Tested-by: kernelci.org bot <bot@kernelci.org>
    Tested-by: Pavel Machek (CIP) <pavel@denx.de>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

 
LoongArch: Define ARCH_IRQ_INIT_FLAGS as IRQ_NOPROBE [+ + +]
Author: Huacai Chen <chenhuacai@kernel.org>
Date:   Mon Aug 26 23:11:32 2024 +0800

    LoongArch: Define ARCH_IRQ_INIT_FLAGS as IRQ_NOPROBE
    
    [ Upstream commit 274ea3563e5ab9f468c15bfb9d2492803a66d9be ]
    
    Currently we call irq_set_noprobe() in a loop for all IRQs, but indeed
    it only works for IRQs below NR_IRQS_LEGACY because at init_IRQ() only
    legacy interrupts have been allocated.
    
    Instead, we can define ARCH_IRQ_INIT_FLAGS as IRQ_NOPROBE in asm/hwirq.h
    and the core will automatically set the flag for all interrupts.
    
    Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
    Signed-off-by: Huacai Chen <chenhuacai@loongson.cn>
    Signed-off-by: Tianyang Zhang <zhangtianyang@loongson.cn>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

LoongArch: KVM: Invalidate guest steal time address on vCPU reset [+ + +]
Author: Bibo Mao <maobibo@loongson.cn>
Date:   Mon Aug 26 23:11:32 2024 +0800

    LoongArch: KVM: Invalidate guest steal time address on vCPU reset
    
    [ Upstream commit 4956e07f05e239b274d042618a250c9fa3e92629 ]
    
    If ParaVirt steal time feature is enabled, there is a percpu gpa address
    passed from guest vCPU and host modifies guest memory space with this gpa
    address. When vCPU is reset normally, it will notify host and invalidate
    gpa address.
    
    However if VM is crashed and VMM reboots VM forcely, the vCPU reboot
    notification callback will not be called in VM. Host needs invalidate
    the gpa address, else host will modify guest memory during VM reboots.
    Here it is invalidated from the vCPU KVM_REG_LOONGARCH_VCPU_RESET ioctl
    interface.
    
    Also funciton kvm_reset_timer() is removed at vCPU reset stage, since SW
    emulated timer is only used in vCPU block state. When a vCPU is removed
    from the block waiting queue, kvm_restore_timer() is called and SW timer
    is cancelled. And the timer register is also cleared at VMM when a vCPU
    is reset.
    
    Signed-off-by: Bibo Mao <maobibo@loongson.cn>
    Signed-off-by: Huacai Chen <chenhuacai@loongson.cn>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 
microblaze: don't treat zero reserved memory regions as error [+ + +]
Author: Mike Rapoport <rppt@kernel.org>
Date:   Mon Jul 29 08:33:27 2024 +0300

    microblaze: don't treat zero reserved memory regions as error
    
    [ Upstream commit 0075df288dd8a7abfe03b3766176c393063591dd ]
    
    Before commit 721f4a6526da ("mm/memblock: remove empty dummy entry") the
    check for non-zero of memblock.reserved.cnt in mmu_init() would always
    be true either because  memblock.reserved.cnt is initialized to 1 or
    because there were memory reservations earlier.
    
    The removal of dummy empty entry in memblock caused this check to fail
    because now memblock.reserved.cnt is initialized to 0.
    
    Remove the check for non-zero of memblock.reserved.cnt because it's
    perfectly fine to have an empty memblock.reserved array that early in
    boot.
    
    Reported-by: Guenter Roeck <linux@roeck-us.net>
    Signed-off-by: Mike Rapoport <rppt@kernel.org>
    Reviewed-by: Wei Yang <richard.weiyang@gmail.com>
    Tested-by: Guenter Roeck <linux@roeck-us.net>
    Link: https://lore.kernel.org/r/20240729053327.4091459-1-rppt@kernel.org
    Signed-off-by: Guenter Roeck <linux@roeck-us.net>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 
net: ftgmac100: Ensure tx descriptor updates are visible [+ + +]
Author: Jacky Chou <jacky_chou@aspeedtech.com>
Date:   Thu Aug 22 15:30:06 2024 +0800

    net: ftgmac100: Ensure tx descriptor updates are visible
    
    [ Upstream commit 4186c8d9e6af57bab0687b299df10ebd47534a0a ]
    
    The driver must ensure TX descriptor updates are visible
    before updating TX pointer and TX clear pointer.
    
    This resolves TX hangs observed on AST2600 when running
    iperf3.
    
    Signed-off-by: Jacky Chou <jacky_chou@aspeedtech.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 
netfilter: nft_socket: Fix a NULL vs IS_ERR() bug in nft_socket_cgroup_subtree_level() [+ + +]
Author: Dan Carpenter <dan.carpenter@linaro.org>
Date:   Sat Sep 14 12:56:51 2024 +0300

    netfilter: nft_socket: Fix a NULL vs IS_ERR() bug in nft_socket_cgroup_subtree_level()
    
    commit 7052622fccb1efb850c6b55de477f65d03525a30 upstream.
    
    The cgroup_get_from_path() function never returns NULL, it returns error
    pointers.  Update the error handling to match.
    
    Fixes: 7f3287db6543 ("netfilter: nft_socket: make cgroupsv2 matching work with namespaces")
    Signed-off-by: Dan Carpenter <dan.carpenter@linaro.org>
    Acked-by: Florian Westphal <fw@strlen.de>
    Acked-by: Pablo Neira Ayuso <pablo@netfilter.org>
    Link: https://patch.msgid.link/bbc0c4e0-05cc-4f44-8797-2f4b3920a820@stanley.mountain
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

netfilter: nft_socket: make cgroupsv2 matching work with namespaces [+ + +]
Author: Florian Westphal <fw@strlen.de>
Date:   Sat Sep 7 16:07:49 2024 +0200

    netfilter: nft_socket: make cgroupsv2 matching work with namespaces
    
    commit 7f3287db654395f9c5ddd246325ff7889f550286 upstream.
    
    When running in container environmment, /sys/fs/cgroup/ might not be
    the real root node of the sk-attached cgroup.
    
    Example:
    
    In container:
    % stat /sys//fs/cgroup/
    Device: 0,21    Inode: 2214  ..
    % stat /sys/fs/cgroup/foo
    Device: 0,21    Inode: 2264  ..
    
    The expectation would be for:
    
      nft add rule .. socket cgroupv2 level 1 "foo" counter
    
    to match traffic from a process that got added to "foo" via
    "echo $pid > /sys/fs/cgroup/foo/cgroup.procs".
    
    However, 'level 3' is needed to make this work.
    
    Seen from initial namespace, the complete hierarchy is:
    
    % stat /sys/fs/cgroup/system.slice/docker-.../foo
      Device: 0,21    Inode: 2264 ..
    
    i.e. hierarchy is
    0    1               2              3
    / -> system.slice -> docker-1... -> foo
    
    ... but the container doesn't know that its "/" is the "docker-1.."
    cgroup.  Current code will retrieve the 'system.slice' cgroup node
    and store its kn->id in the destination register, so compare with
    2264 ("foo" cgroup id) will not match.
    
    Fetch "/" cgroup from ->init() and add its level to the level we try to
    extract.  cgroup root-level is 0 for the init-namespace or the level
    of the ancestor that is exposed as the cgroup root inside the container.
    
    In the above case, cgrp->level of "/" resolved in the container is 2
    (docker-1...scope/) and request for 'level 1' will get adjusted
    to fetch the actual level (3).
    
    v2: use CONFIG_SOCK_CGROUP_DATA, eval function depends on it.
        (kernel test robot)
    
    Cc: cgroups@vger.kernel.org
    Fixes: e0bb96db96f8 ("netfilter: nft_socket: add support for cgroupsv2")
    Reported-by: Nadia Pinaeva <n.m.pinaeva@gmail.com>
    Signed-off-by: Florian Westphal <fw@strlen.de>
    Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

 
nvme-pci: qdepth 1 quirk [+ + +]
Author: Keith Busch <kbusch@kernel.org>
Date:   Wed Sep 11 10:39:59 2024 -0700

    nvme-pci: qdepth 1 quirk
    
    commit 83bdfcbdbe5d901c5fa432decf12e1725a840a56 upstream.
    
    Another device has been reported to be unreliable if we have more than
    one outstanding command. In this new case, data corruption may occur.
    Since we have two devices now needing this quirky behavior, make a
    generic quirk flag.
    
    The same Apple quirk is clearly not "temporary", so update the comment
    while moving it.
    
    Link: https://lore.kernel.org/linux-nvme/191d810a4e3.fcc6066c765804.973611676137075390@collabora.com/
    Reported-by: Robert Beckett <bob.beckett@collabora.com>
    Reviewed-by: Christoph Hellwig hch@lst.de>
    Signed-off-by: Keith Busch <kbusch@kernel.org>
    Cc: "Gagniuc, Alexandru" <alexandru.gagniuc@hp.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

 
ocfs2: add bounds checking to ocfs2_xattr_find_entry() [+ + +]
Author: Ferry Meng <mengferry@linux.alibaba.com>
Date:   Mon May 20 10:40:23 2024 +0800

    ocfs2: add bounds checking to ocfs2_xattr_find_entry()
    
    [ Upstream commit 9e3041fecdc8f78a5900c3aa51d3d756e73264d6 ]
    
    Add a paranoia check to make sure it doesn't stray beyond valid memory
    region containing ocfs2 xattr entries when scanning for a match.  It will
    prevent out-of-bound access in case of crafted images.
    
    Link: https://lkml.kernel.org/r/20240520024024.1976129-1-joseph.qi@linux.alibaba.com
    Signed-off-by: Ferry Meng <mengferry@linux.alibaba.com>
    Signed-off-by: Joseph Qi <joseph.qi@linux.alibaba.com>
    Reported-by: lei lu <llfamsec@gmail.com>
    Reviewed-by: Joseph Qi <joseph.qi@linux.alibaba.com>
    Cc: Mark Fasheh <mark@fasheh.com>
    Cc: Joel Becker <jlbec@evilplan.org>
    Cc: Junxiao Bi <junxiao.bi@oracle.com>
    Cc: Changwei Ge <gechangwei@live.cn>
    Cc: Gang He <ghe@suse.com>
    Cc: Jun Piao <piaojun@huawei.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Stable-dep-of: af77c4fc1871 ("ocfs2: strict bound check before memcmp in ocfs2_xattr_find_entry()")
    Signed-off-by: Sasha Levin <sashal@kernel.org>

ocfs2: strict bound check before memcmp in ocfs2_xattr_find_entry() [+ + +]
Author: Ferry Meng <mengferry@linux.alibaba.com>
Date:   Mon May 20 10:40:24 2024 +0800

    ocfs2: strict bound check before memcmp in ocfs2_xattr_find_entry()
    
    [ Upstream commit af77c4fc1871847b528d58b7fdafb4aa1f6a9262 ]
    
    xattr in ocfs2 maybe 'non-indexed', which saved with additional space
    requested.  It's better to check if the memory is out of bound before
    memcmp, although this possibility mainly comes from crafted poisonous
    images.
    
    Link: https://lkml.kernel.org/r/20240520024024.1976129-2-joseph.qi@linux.alibaba.com
    Signed-off-by: Ferry Meng <mengferry@linux.alibaba.com>
    Signed-off-by: Joseph Qi <joseph.qi@linux.alibaba.com>
    Reported-by: lei lu <llfamsec@gmail.com>
    Reviewed-by: Joseph Qi <joseph.qi@linux.alibaba.com>
    Cc: Changwei Ge <gechangwei@live.cn>
    Cc: Gang He <ghe@suse.com>
    Cc: Joel Becker <jlbec@evilplan.org>
    Cc: Jun Piao <piaojun@huawei.com>
    Cc: Junxiao Bi <junxiao.bi@oracle.com>
    Cc: Mark Fasheh <mark@fasheh.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 
pinctrl: at91: make it work with current gpiolib [+ + +]
Author: Thomas Blocher <thomas.blocher@ek-dev.de>
Date:   Wed Jul 31 01:16:26 2024 +0200

    pinctrl: at91: make it work with current gpiolib
    
    [ Upstream commit 752f387faaae0ae2e84d3f496922524785e77d60 ]
    
    pinctrl-at91 currently does not support the gpio-groups devicetree
    property and has no pin-range.
    Because of this at91 gpios stopped working since patch
    commit 2ab73c6d8323fa1e ("gpio: Support GPIO controllers without pin-ranges")
    This was discussed in the patches
    commit fc328a7d1fcce263 ("gpio: Revert regression in sysfs-gpio (gpiolib.c)")
    commit 56e337f2cf132632 ("Revert "gpio: Revert regression in sysfs-gpio (gpiolib.c)"")
    
    As a workaround manually set pin-range via gpiochip_add_pin_range() until
    a) pinctrl-at91 is reworked to support devicetree gpio-groups
    b) another solution as mentioned in
    commit 56e337f2cf132632 ("Revert "gpio: Revert regression in sysfs-gpio (gpiolib.c)"")
    is found
    
    Signed-off-by: Thomas Blocher <thomas.blocher@ek-dev.de>
    Link: https://lore.kernel.org/5b992862-355d-f0de-cd3d-ff99e67a4ff1@ek-dev.de
    Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 
platform/x86/amd: pmf: Make ASUS GA403 quirk generic [+ + +]
Author: Luke D. Jones <luke@ljones.dev>
Date:   Sat Aug 31 12:39:05 2024 +1200

    platform/x86/amd: pmf: Make ASUS GA403 quirk generic
    
    [ Upstream commit d34af755a533271f39cc7d86e49c0e74fde63a37 ]
    
    The original quirk should match to GA403U so that the full
    range of GA403U models can benefit.
    
    Signed-off-by: Luke D. Jones <luke@ljones.dev>
    Link: https://lore.kernel.org/r/20240831003905.1060977-1-luke@ljones.dev
    Reviewed-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
    Signed-off-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 
platform/x86: asus-wmi: Fix spurious rfkill on UX8406MA [+ + +]
Author: Mathieu Fenniak <mathieu@fenniak.net>
Date:   Fri Aug 23 15:56:28 2024 +0200

    platform/x86: asus-wmi: Fix spurious rfkill on UX8406MA
    
    [ Upstream commit 9286dfd5735b9cceb6a14bdf15e13400ccb60fe7 ]
    
    The Asus Zenbook Duo (UX8406MA) has a keyboard which can be
    placed on the laptop to connect it via USB, or can be removed from the
    laptop to reveal a hidden secondary display in which case the keyboard
    operates via Bluetooth.
    
    When it is placed on the secondary display to connect via USB, it emits
    a keypress for a wireless disable. This causes the rfkill system to be
    activated disconnecting the current wifi connection, which doesn't
    reflect the user's true intention.
    
    Detect this hardware and suppress any wireless switches from the
    keyboard; this keyboard does not have a wireless toggle capability so
    these presses are always spurious.
    
    Signed-off-by: Mathieu Fenniak <mathieu@fenniak.net>
    Reviewed-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
    Link: https://lore.kernel.org/r/20240823135630.128447-1-mathieu@fenniak.net
    Signed-off-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

platform/x86: x86-android-tablets: Make Lenovo Yoga Tab 3 X90F DMI match less strict [+ + +]
Author: Hans de Goede <hdegoede@redhat.com>
Date:   Sun Aug 25 15:24:15 2024 +0200

    platform/x86: x86-android-tablets: Make Lenovo Yoga Tab 3 X90F DMI match less strict
    
    [ Upstream commit a3379eca24a7da5118a7d090da6f8eb8611acac8 ]
    
    There are 2G and 4G RAM versions of the Lenovo Yoga Tab 3 X90F and it
    turns out that the 2G version has a DMI product name of
    "CHERRYVIEW D1 PLATFORM" where as the 4G version has
    "CHERRYVIEW C0 PLATFORM". The sys-vendor + product-version check are
    unique enough that the product-name check is not necessary.
    
    Drop the product-name check so that the existing DMI match for the 4G
    RAM version also matches the 2G RAM version.
    
    Signed-off-by: Hans de Goede <hdegoede@redhat.com>
    Link: https://lore.kernel.org/r/20240825132415.8307-1-hdegoede@redhat.com
    Reviewed-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
    Signed-off-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 
powercap/intel_rapl: Add support for AMD family 1Ah [+ + +]
Author: Dhananjay Ugwekar <Dhananjay.Ugwekar@amd.com>
Date:   Fri Jul 19 10:12:35 2024 +0000

    powercap/intel_rapl: Add support for AMD family 1Ah
    
    [ Upstream commit 166df51097a258a14fe9e946e2157f3b75eeb3c2 ]
    
    AMD Family 1Ah's RAPL MSRs are identical to Family 19h's,
    extend Family 19h's support to Family 1Ah.
    
    Signed-off-by: Dhananjay Ugwekar <Dhananjay.Ugwekar@amd.com>
    Reviewed-by: Gautham R. Shenoy <gautham.shenoy@amd.com>
    Link: https://patch.msgid.link/20240719101234.50827-1-Dhananjay.Ugwekar@amd.com
    Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

powercap/intel_rapl: Fix the energy-pkg event for AMD CPUs [+ + +]
Author: Dhananjay Ugwekar <Dhananjay.Ugwekar@amd.com>
Date:   Tue Jul 30 04:49:19 2024 +0000

    powercap/intel_rapl: Fix the energy-pkg event for AMD CPUs
    
    [ Upstream commit 26096aed255fbac9501718174dbb24c935d8854e ]
    
    After commit ("x86/cpu/topology: Add support for the AMD 0x80000026 leaf"),
    on AMD processors that support extended CPUID leaf 0x80000026, the
    topology_logical_die_id() macros, no longer returns package id, instead it
    returns the CCD (Core Complex Die) id. This leads to the energy-pkg
    event scope to be modified to CCD instead of package.
    
    For more historical context, please refer to commit 32fb480e0a2c
    ("powercap/intel_rapl: Support multi-die/package"), which initially changed
    the RAPL scope from package to die for all systems, as Intel systems
    with Die enumeration have RAPL scope as die, and those without die
    enumeration are not affected. So, all systems(Intel, AMD, Hygon), worked
    correctly with topology_logical_die_id() until recently, but this changed
    after the "0x80000026 leaf" commit mentioned above.
    
    Future multi-die Intel systems will have package scope RAPL counters,
    but they will be using TPMI RAPL interface, which is not affected by
    this change.
    
    Replacing topology_logical_die_id() with topology_physical_package_id()
    conditionally only for AMD and Hygon fixes the energy-pkg event.
    
    On an AMD 2 socket 8 CCD Zen4 server:
    
    Before:
    
    linux$ ls /sys/class/powercap/
    intel-rapl      intel-rapl:4    intel-rapl:8:0  intel-rapl:d
    intel-rapl:0    intel-rapl:4:0  intel-rapl:9    intel-rapl:d:0
    intel-rapl:0:0  intel-rapl:5    intel-rapl:9:0  intel-rapl:e
    intel-rapl:1    intel-rapl:5:0  intel-rapl:a    intel-rapl:e:0
    intel-rapl:1:0  intel-rapl:6    intel-rapl:a:0  intel-rapl:f
    intel-rapl:2    intel-rapl:6:0  intel-rapl:b    intel-rapl:f:0
    intel-rapl:2:0  intel-rapl:7    intel-rapl:b:0
    intel-rapl:3    intel-rapl:7:0  intel-rapl:c
    intel-rapl:3:0  intel-rapl:8    intel-rapl:c:0
    
    After:
    
    linux$ ls /sys/class/powercap/
    intel-rapl  intel-rapl:0  intel-rapl:0:0  intel-rapl:1  intel-rapl:1:0
    
    Only one sysfs entry per-event per-package is created after this change.
    
    Fixes: 63edbaa48a57 ("x86/cpu/topology: Add support for the AMD 0x80000026 leaf")
    Reported-by: Michael Larabel <michael@michaellarabel.com>
    Signed-off-by: Dhananjay Ugwekar <Dhananjay.Ugwekar@amd.com>
    Reviewed-by: Zhang Rui <rui.zhang@intel.com>
    Link: https://patch.msgid.link/20240730044917.4680-3-Dhananjay.Ugwekar@amd.com
    Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 
powercap: intel_rapl: Change an error pointer to NULL [+ + +]
Author: Dan Carpenter <dan.carpenter@linaro.org>
Date:   Fri Aug 23 15:51:36 2024 +0300

    powercap: intel_rapl: Change an error pointer to NULL
    
    commit 6b08b4ee5e60d8789aeb87250f718ef14bebb90e upstream.
    
    The rapl_find_package_domain_cpuslocked() function is supposed to
    return NULL on error.
    
    This new error patch returns ERR_PTR(-EINVAL) but none of the callers
    check for that so it would lead to an Oops.
    
    Fixes: 26096aed255f ("powercap/intel_rapl: Fix the energy-pkg event for AMD CPUs")
    Signed-off-by: Dan Carpenter <dan.carpenter@linaro.org>
    Link: https://patch.msgid.link/fa719c6a-8d3b-4cca-9b43-bcd477ff6655@stanley.mountain
    Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

 
scsi: lpfc: Fix overflow build issue [+ + +]
Author: Sherry Yang <sherry.yang@oracle.com>
Date:   Tue Aug 20 23:51:31 2024 -0700

    scsi: lpfc: Fix overflow build issue
    
    [ Upstream commit 3417c9574e368f0330637505f00d3814ca8854d2 ]
    
    Build failed while enabling "CONFIG_GCOV_KERNEL=y" and
    "CONFIG_GCOV_PROFILE_ALL=y" with following error:
    
    BUILDSTDERR: drivers/scsi/lpfc/lpfc_bsg.c: In function 'lpfc_get_cgnbuf_info':
    BUILDSTDERR: ./include/linux/fortify-string.h:114:33: error: '__builtin_memcpy' accessing 18446744073709551615 bytes at offsets 0 and 0 overlaps 9223372036854775807 bytes at offset -9223372036854775808 [-Werror=restrict]
    BUILDSTDERR:   114 | #define __underlying_memcpy     __builtin_memcpy
    BUILDSTDERR:       |                                 ^
    BUILDSTDERR: ./include/linux/fortify-string.h:637:9: note: in expansion of macro '__underlying_memcpy'
    BUILDSTDERR:   637 |         __underlying_##op(p, q, __fortify_size);                        \
    BUILDSTDERR:       |         ^~~~~~~~~~~~~
    BUILDSTDERR: ./include/linux/fortify-string.h:682:26: note: in expansion of macro '__fortify_memcpy_chk'
    BUILDSTDERR:   682 | #define memcpy(p, q, s)  __fortify_memcpy_chk(p, q, s,                  \
    BUILDSTDERR:       |                          ^~~~~~~~~~~~~~~~~~~~
    BUILDSTDERR: drivers/scsi/lpfc/lpfc_bsg.c:5468:9: note: in expansion of macro 'memcpy'
    BUILDSTDERR:  5468 |         memcpy(cgn_buff, cp, cinfosz);
    BUILDSTDERR:       |         ^~~~~~
    
    This happens from the commit 06bb7fc0feee ("kbuild: turn on -Wrestrict by
    default"). Address this issue by using size_t type.
    
    Signed-off-by: Sherry Yang <sherry.yang@oracle.com>
    Link: https://lore.kernel.org/r/20240821065131.1180791-1-sherry.yang@oracle.com
    Reviewed-by: Justin Tee <justin.tee@broadcom.com>
    Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 
smb: client: fix hang in wait_for_response() for negproto [+ + +]
Author: Paulo Alcantara <pc@manguebit.com>
Date:   Sat Aug 31 21:40:28 2024 -0300

    smb: client: fix hang in wait_for_response() for negproto
    
    [ Upstream commit 7ccc1465465d78e6411b7bd730d06e7435802b5c ]
    
    Call cifs_reconnect() to wake up processes waiting on negotiate
    protocol to handle the case where server abruptly shut down and had no
    chance to properly close the socket.
    
    Simple reproducer:
    
      ssh 192.168.2.100 pkill -STOP smbd
      mount.cifs //192.168.2.100/test /mnt -o ... [never returns]
    
    Cc: Rickard Andersson <rickaran@axis.com>
    Signed-off-by: Paulo Alcantara (Red Hat) <pc@manguebit.com>
    Signed-off-by: Steve French <stfrench@microsoft.com>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 
spi: bcm63xx: Enable module autoloading [+ + +]
Author: Liao Chen <liaochen4@huawei.com>
Date:   Sat Aug 31 09:42:31 2024 +0000

    spi: bcm63xx: Enable module autoloading
    
    [ Upstream commit 709df70a20e990d262c473ad9899314039e8ec82 ]
    
    Add MODULE_DEVICE_TABLE(), so modules could be properly autoloaded based
    on the alias from of_device_id table.
    
    Signed-off-by: Liao Chen <liaochen4@huawei.com>
    Link: https://patch.msgid.link/20240831094231.795024-1-liaochen4@huawei.com
    Signed-off-by: Mark Brown <broonie@kernel.org>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

spi: spidev: Add an entry for elgin,jg10309-01 [+ + +]
Author: Fabio Estevam <festevam@gmail.com>
Date:   Wed Aug 28 15:00:56 2024 -0300

    spi: spidev: Add an entry for elgin,jg10309-01
    
    [ Upstream commit 5f3eee1eef5d0edd23d8ac0974f56283649a1512 ]
    
    The rv1108-elgin-r1 board has an LCD controlled via SPI in userspace.
    The marking on the LCD is JG10309-01.
    
    Add the "elgin,jg10309-01" compatible string.
    
    Signed-off-by: Fabio Estevam <festevam@gmail.com>
    Reviewed-by: Heiko Stuebner <heiko@sntech.de>
    Link: https://patch.msgid.link/20240828180057.3167190-2-festevam@gmail.com
    Signed-off-by: Mark Brown <broonie@kernel.org>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

spi: spidev: Add missing spi_device_id for jg10309-01 [+ + +]
Author: Geert Uytterhoeven <geert+renesas@glider.be>
Date:   Tue Sep 3 14:32:27 2024 +0200

    spi: spidev: Add missing spi_device_id for jg10309-01
    
    [ Upstream commit 5478a4f7b94414def7b56d2f18bc2ed9b0f3f1f2 ]
    
    When the of_device_id entry for "elgin,jg10309-01" was added, the
    corresponding spi_device_id was forgotten, causing a warning message
    during boot-up:
    
        SPI driver spidev has no spi_device_id for elgin,jg10309-01
    
    Fix module autoloading and shut up the warning by adding the missing
    entry.
    
    Fixes: 5f3eee1eef5d0edd ("spi: spidev: Add an entry for elgin,jg10309-01")
    Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
    Link: https://patch.msgid.link/54bbb9d8a8db7e52d13e266f2d4a9bcd8b42a98a.1725366625.git.geert+renesas@glider.be
    Signed-off-by: Mark Brown <broonie@kernel.org>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 
tools: hv: rm .*.cmd when make clean [+ + +]
Author: zhang jiao <zhangjiao2@cmss.chinamobile.com>
Date:   Mon Sep 2 12:21:03 2024 +0800

    tools: hv: rm .*.cmd when make clean
    
    [ Upstream commit 5e5cc1eb65256e6017e3deec04f9806f2f317853 ]
    
    rm .*.cmd when make clean
    
    Signed-off-by: zhang jiao <zhangjiao2@cmss.chinamobile.com>
    Reviewed-by: Saurabh Sengar <ssengar@linux.microsoft.com>
    Link: https://lore.kernel.org/r/20240902042103.5867-1-zhangjiao2@cmss.chinamobile.com
    Signed-off-by: Wei Liu <wei.liu@kernel.org>
    Message-ID: <20240902042103.5867-1-zhangjiao2@cmss.chinamobile.com>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 
USB: serial: pl2303: add device id for Macrosilicon MS3020 [+ + +]
Author: Junhao Xie <bigfoot@classfun.cn>
Date:   Tue Sep 3 23:06:38 2024 +0800

    USB: serial: pl2303: add device id for Macrosilicon MS3020
    
    commit 7d47d22444bb7dc1b6d768904a22070ef35e1fc0 upstream.
    
    Add the device id for the Macrosilicon MS3020 which is a
    PL2303HXN based device.
    
    Signed-off-by: Junhao Xie <bigfoot@classfun.cn>
    Cc: stable@vger.kernel.org
    Signed-off-by: Johan Hovold <johan@kernel.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

USB: usbtmc: prevent kernel-usb-infoleak [+ + +]
Author: Edward Adam Davis <eadavis@qq.com>
Date:   Sun Sep 8 17:17:41 2024 +0800

    USB: usbtmc: prevent kernel-usb-infoleak
    
    commit 625fa77151f00c1bd00d34d60d6f2e710b3f9aad upstream.
    
    The syzbot reported a kernel-usb-infoleak in usbtmc_write,
    we need to clear the structure before filling fields.
    
    Fixes: 4ddc645f40e9 ("usb: usbtmc: Add ioctl for vendor specific write")
    Reported-and-tested-by: syzbot+9d34f80f841e948c3fdb@syzkaller.appspotmail.com
    Closes: https://syzkaller.appspot.com/bug?extid=9d34f80f841e948c3fdb
    Signed-off-by: Edward Adam Davis <eadavis@qq.com>
    Cc: stable <stable@kernel.org>
    Link: https://lore.kernel.org/r/tencent_9649AA6EC56EDECCA8A7D106C792D1C66B06@qq.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

 
wifi: iwlwifi: clear trans->state earlier upon error [+ + +]
Author: Emmanuel Grumbach <emmanuel.grumbach@intel.com>
Date:   Sun Aug 25 19:17:01 2024 +0300

    wifi: iwlwifi: clear trans->state earlier upon error
    
    [ Upstream commit 094513f8a2fbddee51b055d8035f995551f98fce ]
    
    When the firmware crashes, we first told the op_mode and only then,
    changed the transport's state. This is a problem if the op_mode's
    nic_error() handler needs to send a host command: it'll see that the
    transport's state still reflects that the firmware is alive.
    
    Today, this has no consequences since we set the STATUS_FW_ERROR bit and
    that will prevent sending host commands. iwl_fw_dbg_stop_restart_recording
    looks at this bit to know not to send a host command for example.
    
    To fix the hibernation, we needed to reset the firmware without having
    an error and checking STATUS_FW_ERROR to see whether the firmware is
    alive will no longer hold, so this change is necessary as well.
    
    Change the flow a bit.
    Change trans->state before calling the op_mode's nic_error() method and
    check trans->state instead of STATUS_FW_ERROR. This will keep the
    current behavior of iwl_fw_dbg_stop_restart_recording upon firmware
    error, and it'll allow us to call iwl_fw_dbg_stop_restart_recording
    safely even if STATUS_FW_ERROR is clear, but yet, the firmware is not
    alive.
    
    Signed-off-by: Emmanuel Grumbach <emmanuel.grumbach@intel.com>
    Signed-off-by: Miri Korenblit <miriam.rachel.korenblit@intel.com>
    Link: https://patch.msgid.link/20240825191257.9d7427fbdfd7.Ia056ca57029a382c921d6f7b6a6b28fc480f2f22@changeid
    [I missed this was a dependency for the hibernation fix, changed
     the commit message a bit accordingly]
    Signed-off-by: Johannes Berg <johannes.berg@intel.com>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

wifi: iwlwifi: lower message level for FW buffer destination [+ + +]
Author: Benjamin Berg <benjamin.berg@intel.com>
Date:   Sun Aug 25 19:17:13 2024 +0300

    wifi: iwlwifi: lower message level for FW buffer destination
    
    [ Upstream commit f8a129c1e10256c785164ed5efa5d17d45fbd81b ]
    
    An invalid buffer destination is not a problem for the driver and it
    does not make sense to report it with the KERN_ERR message level. As
    such, change the message to use IWL_DEBUG_FW.
    
    Reported-by: Len Brown <lenb@kernel.org>
    Closes: https://lore.kernel.org/r/CAJvTdKkcxJss=DM2sxgv_MR5BeZ4_OC-3ad6tA40TYH2yqHCWw@mail.gmail.com
    Signed-off-by: Benjamin Berg <benjamin.berg@intel.com>
    Signed-off-by: Miri Korenblit <miriam.rachel.korenblit@intel.com>
    Link: https://patch.msgid.link/20240825191257.20abf78f05bc.Ifbcecc2ae9fb40b9698302507dcba8b922c8d856@changeid
    Signed-off-by: Johannes Berg <johannes.berg@intel.com>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

wifi: iwlwifi: mvm: don't wait for tx queues if firmware is dead [+ + +]
Author: Emmanuel Grumbach <emmanuel.grumbach@intel.com>
Date:   Sun Aug 25 19:17:04 2024 +0300

    wifi: iwlwifi: mvm: don't wait for tx queues if firmware is dead
    
    [ Upstream commit 3a84454f5204718ca5b4ad2c1f0bf2031e2403d1 ]
    
    There is a WARNING in iwl_trans_wait_tx_queues_empty() (that was
    recently converted from just a message), that can be hit if we
    wait for TX queues to become empty after firmware died. Clearly,
    we can't expect anything from the firmware after it's declared dead.
    
    Don't call iwl_trans_wait_tx_queues_empty() in this case. While it could
    be a good idea to stop the flow earlier, the flush functions do some
    maintenance work that is not related to the firmware, so keep that part
    of the code running even when the firmware is not running.
    
    Signed-off-by: Emmanuel Grumbach <emmanuel.grumbach@intel.com>
    Signed-off-by: Miri Korenblit <miriam.rachel.korenblit@intel.com>
    Link: https://patch.msgid.link/20240825191257.a7cbd794cee9.I44a739fbd4ffcc46b83844dd1c7b2eb0c7b270f6@changeid
    [edit commit message]
    Signed-off-by: Johannes Berg <johannes.berg@intel.com>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

wifi: iwlwifi: mvm: fix iwl_mvm_max_scan_ie_fw_cmd_room() [+ + +]
Author: Daniel Gabay <daniel.gabay@intel.com>
Date:   Sun Aug 25 19:17:06 2024 +0300

    wifi: iwlwifi: mvm: fix iwl_mvm_max_scan_ie_fw_cmd_room()
    
    [ Upstream commit 916a5d9c5354c426220a0a6533a5e8ea1287d6ea ]
    
    Driver creates also the WFA TPC element, consider that in the
    calculation.
    
    Signed-off-by: Daniel Gabay <daniel.gabay@intel.com>
    Reviewed-by: Ilan Peer <ilan.peer@intel.com>
    Signed-off-by: Miri Korenblit <miriam.rachel.korenblit@intel.com>
    Link: https://patch.msgid.link/20240825191257.e710ce446b7f.I2715c6742e9c3d160e2ba41bc4b35de370d2ce34@changeid
    Signed-off-by: Johannes Berg <johannes.berg@intel.com>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

wifi: iwlwifi: mvm: fix iwl_mvm_scan_fits() calculation [+ + +]
Author: Daniel Gabay <daniel.gabay@intel.com>
Date:   Sun Aug 25 19:17:05 2024 +0300

    wifi: iwlwifi: mvm: fix iwl_mvm_scan_fits() calculation
    
    [ Upstream commit d44162280899c3fc2c6700e21e491e71c3c96e3d ]
    
    The calculation should consider also the 6GHz IE's len, fix that.
    In addition, in iwl_mvm_sched_scan_start() the scan_fits helper is
    called only in case non_psc_incldued is true, but it should be called
    regardless, fix that as well.
    
    Signed-off-by: Daniel Gabay <daniel.gabay@intel.com>
    Reviewed-by: Ilan Peer <ilan.peer@intel.com>
    Signed-off-by: Miri Korenblit <miriam.rachel.korenblit@intel.com>
    Link: https://patch.msgid.link/20240825191257.7db825442fd2.I99f4d6587709de02072fd57957ec7472331c6b1d@changeid
    Signed-off-by: Johannes Berg <johannes.berg@intel.com>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

wifi: iwlwifi: mvm: pause TCM when the firmware is stopped [+ + +]
Author: Emmanuel Grumbach <emmanuel.grumbach@intel.com>
Date:   Sun Aug 25 19:17:10 2024 +0300

    wifi: iwlwifi: mvm: pause TCM when the firmware is stopped
    
    [ Upstream commit 0668ebc8c2282ca1e7eb96092a347baefffb5fe7 ]
    
    Not doing so will make us send a host command to the transport while the
    firmware is not alive, which will trigger a WARNING.
    
    bad state = 0
    WARNING: CPU: 2 PID: 17434 at drivers/net/wireless/intel/iwlwifi/iwl-trans.c:115 iwl_trans_send_cmd+0x1cb/0x1e0 [iwlwifi]
    RIP: 0010:iwl_trans_send_cmd+0x1cb/0x1e0 [iwlwifi]
    Call Trace:
     <TASK>
     iwl_mvm_send_cmd+0x40/0xc0 [iwlmvm]
     iwl_mvm_config_scan+0x198/0x260 [iwlmvm]
     iwl_mvm_recalc_tcm+0x730/0x11d0 [iwlmvm]
     iwl_mvm_tcm_work+0x1d/0x30 [iwlmvm]
     process_one_work+0x29e/0x640
     worker_thread+0x2df/0x690
     ? rescuer_thread+0x540/0x540
     kthread+0x192/0x1e0
     ? set_kthread_struct+0x90/0x90
     ret_from_fork+0x22/0x30
    
    Signed-off-by: Emmanuel Grumbach <emmanuel.grumbach@intel.com>
    Signed-off-by: Miri Korenblit <miriam.rachel.korenblit@intel.com>
    Link: https://patch.msgid.link/20240825191257.5abe71ca1b6b.I97a968cb8be1f24f94652d9b110ecbf6af73f89e@changeid
    Signed-off-by: Johannes Berg <johannes.berg@intel.com>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

wifi: mac80211: free skb on error path in ieee80211_beacon_get_ap() [+ + +]
Author: Dmitry Antipov <dmantipov@yandex.ru>
Date:   Mon Aug 5 17:20:35 2024 +0300

    wifi: mac80211: free skb on error path in ieee80211_beacon_get_ap()
    
    [ Upstream commit 786c5be9ac29a39b6f37f1fdd2ea59d0fe35d525 ]
    
    In 'ieee80211_beacon_get_ap()', free allocated skb in case of error
    returned by 'ieee80211_beacon_protect()'. Compile tested only.
    
    Signed-off-by: Dmitry Antipov <dmantipov@yandex.ru>
    Link: https://patch.msgid.link/20240805142035.227847-1-dmantipov@yandex.ru
    Signed-off-by: Johannes Berg <johannes.berg@intel.com>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 
x86/hyperv: Set X86_FEATURE_TSC_KNOWN_FREQ when Hyper-V provides frequency [+ + +]
Author: Michael Kelley <mhklinux@outlook.com>
Date:   Wed Jun 5 19:55:59 2024 -0700

    x86/hyperv: Set X86_FEATURE_TSC_KNOWN_FREQ when Hyper-V provides frequency
    
    [ Upstream commit 8fcc514809de41153b43ccbe1a0cdf7f72b78e7e ]
    
    A Linux guest on Hyper-V gets the TSC frequency from a synthetic MSR, if
    available. In this case, set X86_FEATURE_TSC_KNOWN_FREQ so that Linux
    doesn't unnecessarily do refined TSC calibration when setting up the TSC
    clocksource.
    
    With this change, a message such as this is no longer output during boot
    when the TSC is used as the clocksource:
    
    [    1.115141] tsc: Refined TSC clocksource calibration: 2918.408 MHz
    
    Furthermore, the guest and host will have exactly the same view of the
    TSC frequency, which is important for features such as the TSC deadline
    timer that are emulated by the Hyper-V host.
    
    Signed-off-by: Michael Kelley <mhklinux@outlook.com>
    Reviewed-by: Roman Kisel <romank@linux.microsoft.com>
    Link: https://lore.kernel.org/r/20240606025559.1631-1-mhklinux@outlook.com
    Signed-off-by: Wei Liu <wei.liu@kernel.org>
    Message-ID: <20240606025559.1631-1-mhklinux@outlook.com>
    Signed-off-by: Sasha Levin <sashal@kernel.org>