BMC/Intel-BMC/linux.git/drivers/misc, branch dev-5.7

Merge tag 'v5.7.10' into dev-5.7

2020-07-22T09:35:53+00:00

This is the 5.7.10 stable release Signed-off-by: Joel Stanley

misc: atmel-ssc: lock with mutex instead of spinlock

2020-07-22T07:34:24+00:00

commit b037d60a3b1d1227609fd858fa34321f41829911 upstream. Uninterruptible context is not needed in the driver and causes lockdep warning because of mutex taken in of_alias_get_id(). Convert the lock to mutex to avoid the issue. Cc: stable@vger.kernel.org Fixes: 099343c64e16 ("ARM: at91: atmel-ssc: add device tree support") Signed-off-by: Michał Mirosław Link: https://lore.kernel.org/r/50f0d7fa107f318296afb49477c3571e4d6978c5.1592998403.git.mirq-linux@rere.qmqm.pl Signed-off-by: Greg Kroah-Hartman

mei: bus: don't clean driver pointer

2020-07-22T07:34:21+00:00

commit e852c2c251ed9c23ae6e3efebc5ec49adb504207 upstream. It's not needed to set driver to NULL in mei_cl_device_remove() which is bus_type remove() handler as this is done anyway in __device_release_driver(). Actually this is causing an endless loop in driver_detach() on ubuntu patched kernel, while removing (rmmod) the mei_hdcp module. The reason list_empty(&drv->p->klist_devices.k_list) is always not-empty. as the check is always true in __device_release_driver() if (dev->driver != drv) return; The non upstream patch is causing this behavior, titled: 'vfio -- release device lock before userspace requests' Nevertheless the fix is correct also for the upstream. Link: https://patchwork.ozlabs.org/project/ubuntu-kernel/patch/20180912085046.3401-2-apw@canonical.com/ Cc: Cc: Andy Whitcroft Signed-off-by: Alexander Usyskin Signed-off-by: Tomas Winkler Link: https://lore.kernel.org/r/20200628225359.2185929-1-tomas.winkler@intel.com Signed-off-by: Greg Kroah-Hartman

habanalabs: Align protection bits configuration of all TPCs

2020-07-22T07:34:12+00:00

commit 79c823c57e69d9e584a5ee4ee6406eb3854393ae upstream. Align the protection bits configuration of all TPC cores to be as of TPC core 0. Fixes: a513f9a7eca5 ("habanalabs: make tpc registers secured") Signed-off-by: Tomer Tayar Reviewed-by: Oded Gabbay Signed-off-by: Oded Gabbay Signed-off-by: Greg Kroah-Hartman

Merge tag 'v5.7.7' into dev-5.7

2020-07-08T05:41:18+00:00

Linux 5.7.7 Signed-off-by: Joel Stanley

misc: Add ASPEED KCS driver for MCTP purposes

2020-07-08T04:32:04+00:00

IBM have developed a vendor-defined MCTP binding that utilises LPC IO and FW interfaces to exchange MCTP messages. A KCS device in the IO space is used to send single-byte control messages initialising the MCTP channel and exchanging ownership of data buffers. This driver exposes the KCS message stream to userspace, allowing an MCTP-capable application to manipulate the data exposed via the FW space. OpenBMC-Staging-Count: 2 Signed-off-by: Andrew Jeffery Signed-off-by: Joel Stanley

misc: mbox: add npcm7xx pci mailbox driver

2020-07-08T04:32:01+00:00

Add Nuvoton BMC NPCM7XX PCI Mailbox driver. OpenBMC-Staging-Count: 7 Signed-off-by: Tomer Maimon [v5.0: Fix access_ok for API change] Signed-off-by: Joel Stanley

misc: npcm7xx-lpc-bpc: add NPCM7xx BIOS post code driver

2020-07-08T04:32:01+00:00

Add NPCM7xx BIOS post code (BPC) driver, the BPC monitoring two I/O address written by the host on the LPC. OpenBMC-Staging-Count: 7 Signed-off-by: Tomer Maimon Signed-off-by: Joel Stanley

mei: me: add tiger lake point device ids for H platforms.

2020-06-30T19:35:54+00:00

commit 8c289ea064165237891a7b4be77b74d5cba8fa99 upstream. Add Tiger Lake device ids H for HECI1. TGH_H is also used in Tatlow SPS platform we need to disable the mei interface there. Cc: Signed-off-by: Alexander Usyskin Signed-off-by: Tomas Winkler Link: https://lore.kernel.org/r/20200619165121.2145330-7-tomas.winkler@intel.com Signed-off-by: Greg Kroah-Hartman

mei: me: disable mei interface on Mehlow server platforms

2020-06-30T19:35:54+00:00

commit f76d77f50b343bc7f7d01e4c2771d43fb074f617 upstream. For SPS firmware versions 5.0 and newer the way detection has changed. The detection is done now via PCI_CFG_HFS_3 register. To prevent conflict the previous method will get sps_4 suffix Disable both CNP_H and CNP_H_3 interfaces. CNP_H_3 requires a separate configuration as it doesn't support DMA. Cc: Signed-off-by: Tomas Winkler Link: https://lore.kernel.org/r/20200619165121.2145330-1-tomas.winkler@intel.com Signed-off-by: Greg Kroah-Hartman