BMC/Intel-BMC/linux.git/include/linux, branch dev-4.13

fsi/sbefifo: Add driver for the SBE FIFO

2018-05-25T05:41:57+00:00

This driver provides an in-kernel and a user API for accessing the command FIFO of the SBE (Self Boot Engine) of the POWER9 processor, via the FSI bus. It provides an in-kernel interface to submit command and receive responses, along with a helper to locate and analyse the response status block. It's a simple synchronous submit() type API. The user interface uses the write/read interface that an earlier version of this driver already provided, however it has some specific limitations in order to keep the driver simple and avoid using up a lot of kernel memory: - The user should perform a single write() with the command and a single read() to get the response (with a buffer big enough to hold the entire response). - On a write() the command is simply "stored" into a kernel buffer, it is submitted as one operation on the subsequent read(). This allows to have the code write directly from the FIFO into the user buffer and avoid hogging the SBE between the write() and read() syscall as it's critical that the SBE be freed asap to respond to the host. An extra write() will simply replace the previously written command. - A write of a single 4 bytes containing the value 0x52534554 in big endian will trigger a reset request. No read is necessary, the write() call will return when the reset has been acknowledged or times out. - The command is limited to 4K bytes. OpenBMC-Staging-Count: 1 Signed-off-by: Benjamin Herrenschmidt Signed-off-by: Joel Stanley

fsi: Remove old sbefifo driver

2018-05-25T05:41:46+00:00

And remporarily disable build of fsi-occ OpenBMC-Staging-Count: 1 Signed-off-by: Joel Stanley

Merge tag 'drm-for-v4.14' into dev-4.13

2018-04-19T02:00:20+00:00

This is the DRM tree that was merged into the mainline 4.14 kernel. The ASPEED GFX DRM driver requires functionaliy that was included in this tree, so we merge it back into the 4.13 OpenBMC tree. This should have no impact on other parts of the BMC. Signed-off-by: Joel Stanley

serial/8250: export serial8250_read_char

2018-04-05T13:18:55+00:00

Currently, we export serial8250_rx_chars, which does a whole bunch of reads from the 8250 data register, without any form of flow control between reads. An upcoming change to the aspeed vuart driver implements more fine-grained flow control in the interrupt handler, requiring character-at-a-time control over the rx path. This change exports serial8250_read_char to allow this. OpenBMC-Staging-Count: 1 Signed-off-by: Jeremy Kerr Tested-by: Eddie James Signed-off-by: Andrew Jeffery

serial: Introduce UPSTAT_SYNC_FIFO for synchronised FIFOs

2018-04-05T13:18:49+00:00

This change adds a flag to indicate that a UART is has an external means of synchronising its FIFO, without needing CTSRTS or XON/XOFF. This allows us to use the throttle/unthrottle callbacks, without having to claim other methods of flow control. OpenBMC-Staging-Count: 1 Signed-off-by: Jeremy Kerr Tested-by: Eddie James Signed-off-by: Andrew Jeffery

gpio: gpiolib: Generalise state persistence beyond sleep

2018-02-08T06:04:00+00:00

General support for state persistence is added to gpiolib with the introduction of a new pinconf parameter to propagate the request to hardware. The existing persistence support for sleep is adapted to include hardware support if the GPIO driver provides it. Persistence continues to be enabled by default; in-kernel consumers can opt out, but userspace (currently) does not have a choice. The *_SLEEP_MAY_LOSE_VALUE and *_SLEEP_MAINTAIN_VALUE symbols are renamed, dropping the SLEEP prefix to reflect that the concept is no longer sleep-specific. I feel that renaming to just *_MAY_LOSE_VALUE could initially be misinterpreted, so I've further changed the symbols to *_TRANSITORY and *_PERSISTENT to address this. The sysfs interface is modified only to keep consistency with the chardev interface in enforcing persistence for userspace exports. Signed-off-by: Andrew Jeffery Reviewed-by: Charles Keepax Acked-by: Rob Herring Signed-off-by: Linus Walleij (cherry picked from commit e10f72bf4b3e8885c1915a119141481e7fc45ca8) Signed-off-by: Joel Stanley

Merge tag 'v4.13.16' into dev-4.13

2017-11-28T07:41:55+00:00

This is the 4.13.16 stable release

leds: gpio: Allow LED to retain state at shutdown

2017-11-28T04:22:52+00:00

In some systems, such as Baseboard Management Controllers (BMCs), we want to retain the state of LEDs across a reboot of the BMC (whilst the host remains up). Implement support for the retain-state-shutdown devicetree property in leds-gpio. Signed-off-by: Andrew Jeffery Acked-by: Pavel Machek Tested-by: Brandon Wyman Signed-off-by: Jacek Anaszewski (cherry picked from commit f5808ac158f2b16b686a3d3c0879c5d6048aba14) Signed-off-by: Joel Stanley

drivers/fsi: occ: Add in-kernel API

2017-11-28T03:42:10+00:00

Add an in-kernel read/write API with exported functions. This is necessary for other drivers which want to directly interact with the OCC. Also add a child platform device node for the associated hwmon device. OpenBMC-Staging-Count: 2 Signed-off-by: Edward A. James Signed-off-by: Joel Stanley

drivers/fsi: sbefifo: Add in-kernel API

2017-11-28T03:42:09+00:00

Refactor the user interface of the SBEFIFO driver to allow for an in-kernel read/write API. Add exported functions for other drivers to call, and add an include file with those functions. Also parse the device tree for child nodes and create child platform devices accordingly. OpenBMC-Staging-Count: 2 Signed-off-by: Edward A. James Signed-off-by: Joel Stanley