BMC/Intel-BMC/linux.git/drivers/soc, branch dev-5.8-intel

soc: aspeed: mctp: Export function used to read BDF

2021-02-04T13:16:07+00:00

Recently, aspeed-mctp driver functionality was extended to store BDF values for already discovered MCTP endpoints on PCIe bus. Let's expose kernel API to read BDF based on endpoint ID. Change-Id: I146e67a8c2f4f541b4c3065c18dcadf531f30670 Signed-off-by: Iwona Winiarska

Enable mailbox interrupts

2021-02-04T01:29:36+00:00

Support interrupt generation for both 16 and 32 mailbox registers. Tested: After applied this patch, write the mailbox registers from BIOS side, the misc manager can capture the new mailbox data. Change-Id: I4030b6df176a53656aea9cb68ee80b67add8ed14 Signed-off-by: Yong Li

fixup! soc: aspeed: mctp: Add IOCTL to register default client

2021-01-25T17:31:26+00:00

Remove temporary workaround to register first user space client as default client. Change-Id: I9e020be0815422c125f38713ce21a6ac3cdba1ad Signed-off-by: Andrzej Kacprowski

Move Aspeed eSPI driver to soc/aspeed tree

2021-01-14T23:18:04+00:00

This commit moves Aspeed eSPI driver from misc to soc/aspeed tree to make correct probing order for LPC and eSPI driver. Since LPC runs over eSPI, eSPI driver should be registered ahead of LPC driver. Signed-off-by: Jae Hyun Yoo Change-Id: I6c813c3e29ddb02c86e3266b9fc713a8b410169e

soc: aspeed: mctp: Register peci_mctp device

2021-01-11T23:22:20+00:00

Now that it is possible to send PECI frames via aspeed-mctp driver, let's add aspeed-peci-mctp node to allow bind peci-mctp-aspeed adapter driver. Change-Id: Ie511af2896a6626d7179cd9475ec9ef8c7309496 Signed-off-by: Iwona Winiarska

soc: aspeed: mctp: Fix TX hangs and optimize TX logic

2021-01-08T10:19:27+00:00

Currently driver submits 1 (or rarely more than 1) packet then waits until HW signals transmission completion before sending more packets. This logic requires interrupt after each packet, aspeed_mctp_tx_tasklet() is invoked twice per packet. New logic uses TX ring correctly, packets are added to the end of circular ring buffer. The driver does not have to wait for HW to complete transmission of enqueued packets before adding more packets to TX queue. Interrupt is generated only if TX ring if full. This change significantly improves packet transmission performance: PECI GetTemp command takes ~25us instead of ~30us. This change also fixes sporadic TX hangs during host reboot seen with current driver. Change-Id: Ia12f71eb048c10e7aa0dd3821206044698d0c7f9 Signed-off-by: Andrzej Kacprowski

soc: aspeed: mctp: Update source EID in TX packets

2021-01-08T10:19:27+00:00

If self EID is known then the driver updates source EID in MCTP header of sent packets. For MCTP control packets the source EID is not updated as it may disrupt MCTP discovery flow. Self EID is determined from list of known endpoints provided by ASPEED_MCTP_IOCTL_SET_EID_INFO IOCTL. Change-Id: I8d6d0aebac096859a55694d6d82540aea8264085 Signed-off-by: Andrzej Kacprowski

fixup! aspeed-mctp: Add EID information related ioctls

2021-01-08T08:17:14+00:00

Fix error when swapping two empty lists. Copy count in ASPEED_MCTP_GET_EID_INFO to userbuf instead of incorrectly returning it by value. Change-Id: I8549a3a988d1f44106582729b9a6eca650ded256 Signed-off-by: Karol Wachowski

fixup! soc: aspeed: mctp: Expose internal kernel API

2021-01-07T01:18:44+00:00

Fixed a missing error handling for case where wait_event_interruptible_timeout() returns -ERESTARTSYS. Renamed the exposed functions to be more consistent with their usage. Added dedicated function to flush client rx queue. Change-Id: I0fd1bfca926b34ae0f4dc18f07e453b3861a4c3e Signed-off-by: Iwona Winiarska

soc: aspeed: mctp: Fix RX hangs and RX packet misses

2020-12-21T11:09:42+00:00

Under even moderate traffic the driver can miss a lot of received packets and eventually stops receiving packets at all. There is an bug in AST2600 RX logic where HW does not wrap around RX read buffer pointer correctly. Current driver workaround for this bug resets RX HW read pointer to 0 whenever it reaches end of the RX buffer ring - this does not work properly if more than 1 packet is received while RX pointer is close to the end of the RX buffer ring - in such case HW can detect ring full condition and stop RX. The new workaround has different logic: it sets HW buffer count to 4n - 1 and updates driver maintained RX write pointer so it tracks HW read pointer to prevent hardware from stopping. Received packets are located by looking into RX data buffers rather that HW read pointer that contains incorrect value anyway. Driver never resets HW read pointer, HW is receiving packets without any interference form the driver. Also handle RX_CMD_NO_MORE_INT - if RX ring if full then HW will clear RX_CMD_READY bit and we need to re-enable it once we free some space in RX ring. Change-Id: I0a94fd43a91f17677e6df9da7bb71b3254543de0 Signed-off-by: Andrzej Kacprowski