blackbird-op-linux, branch v4.4.3-openpower2

Release 4.4.3-openpower2

2016-03-03T01:10:40+00:00

- ast: Switch SCU to VGA output on POST - scsi: ignore errors from scsi_dh_add_device() - mlx4: Set UAR page size to 4KB regardless of system page size Signed-off-by: Joel Stanley

net/mlx4_core: Set UAR page size to 4KB regardless of system page size

2016-03-03T01:10:05+00:00

problem description: The current code sets UAR page size equal to system page size. The ConnectX-3 and ConnectX-3 Pro HWs require minimum 128 UAR pages. The mlx4 kernel drivers are not loaded if there is less than 128 UAR pages. solution: Always set UAR page to 4KB. This allows more UAR pages if the OS has PAGE_SIZE larger than 4KB. For example, PowerPC kernel use 64KB system page size, with 4MB uar region, there are 4MB/2/64KB = 32 uars (half for uar, half for blueflame). This does not meet minimum 128 UAR pages requirement. With 4KB UAR page, there are 4MB/2/4KB = 512 uars which meet the minimum requirement. Note that only codes in mlx4_core that deal with firmware know that uar page size is 4KB. Codes that deal with usr page in cq and qp context (mlx4_ib, mlx4_en and part of mlx4_core) still have the same assumption that uar page size equals to system page size. Note that with this implementation, on 64KB system page size kernel, there are 16 uars per system page but only one uars is used. The other 15 uars are ignored because of the above assumption. Regarding SR-IOV, mlx4_core in hypervisor will set the uar page size to 4KB and mlx4_core code in virtual OS will obtain the uar page size from firmware. Regarding backward compatibility in SR-IOV, if hypervisor has this new code, the virtual OS must be updated. If hypervisor has old code, and the virtual OS has this new code, the new code will be backward compatible with the old code. If the uar size is big enough, this new code in VF continues to work with 64 KB uar page size (on PowerPc kernel). If the uar size does not meet 128 uars requirement, this new code not loaded in VF and print the same error message as the old code in Hypervisor. Signed-off-by: Huy Nguyen Reviewed-by: Yishai Hadas Signed-off-by: David S. Miller (cherry picked from commit 85743f1eb34548ba4b056d2f184a3d107a3b8917) Signed-off-by: Joel Stanley

scsi: ignore errors from scsi_dh_add_device()

2016-03-03T01:07:35+00:00

device handler initialisation might fail due to a number of reasons. But as device_handlers are optional this shouldn't cause us to disable the device entirely. So just ignore errors from scsi_dh_add_device(). Reviewed-by: Johannes Thumshirn Reviewed-by: Christoph Hellwig Signed-off-by: Hannes Reinecke Signed-off-by: Martin K. Petersen Signed-off-by: Joel Stanley

drivers/drm/ast: Switch SCU to VGA output on POST

2016-03-03T01:07:34+00:00

On AST BMC platforms, the BMC may be using the VGA device for UART mirroring. In this case, we need to switch the DAC output to VGA mode. Signed-off-by: Jeremy Kerr Signed-off-by: Joel Stanley

xhci: do not halt the secondary HCD

2016-02-28T23:04:14+00:00

We can't halt the secondary HCD, because it's also the primary HCD, which will cause problems if we have devices attached to the primary HCD, like a keyboard. Signed-off-by: Jeremy Kerr Signed-off-by: Joel Stanley

Revert "usb: xhci: stop everything on the first call to xhci_stop"

2016-02-28T23:04:13+00:00

This reverts commit 8c24d6d7b09deee3036ddc4f2b81b53b28c8f877. With this patch, the driver stops everything at the first call to xhci_stop, which is always for the secondary HCD when executing the .remove handler. We instead want to only stop when the primray HCD is shutting down. Signed-off-by: Joel Stanley

xhci: Use xhci_pci_remove for xhci device shutdown

2016-02-28T23:04:13+00:00

Signed-off-by: Jeremy Kerr

Linux 4.4.3

2016-02-25T20:01:36+00:00

modules: fix modparam async_probe request

2016-02-25T20:01:25+00:00

commit 4355efbd80482a961cae849281a8ef866e53d55c upstream. Commit f2411da746985 ("driver-core: add driver module asynchronous probe support") added async probe support, in two forms: * in-kernel driver specification annotation * generic async_probe module parameter (modprobe foo async_probe) To support the generic kernel parameter parse_args() was extended via commit ecc8617053e0 ("module: add extra argument for parse_params() callback") however commit failed to f2411da746985 failed to add the required argument. This causes a crash then whenever async_probe generic module parameter is used. This was overlooked when the form in which in-kernel async probe support was reworked a bit... Fix this as originally intended. Cc: Hannes Reinecke Cc: Dmitry Torokhov Signed-off-by: Luis R. Rodriguez Signed-off-by: Rusty Russell [minimized] Signed-off-by: Greg Kroah-Hartman

module: wrapper for symbol name.

2016-02-25T20:01:25+00:00

commit 2e7bac536106236104e9e339531ff0fcdb7b8147 upstream. This trivial wrapper adds clarity and makes the following patch smaller. Signed-off-by: Rusty Russell Signed-off-by: Greg Kroah-Hartman