summaryrefslogtreecommitdiffstats
path: root/Documentation
Commit message (Collapse)AuthorAgeFilesLines
* hwmon: (w83773g) Add documentationLei YU2018-01-171-0/+33
| | | | | | | | | Add documentation for the w83773g driver. OpenBMC-Staging-Count: 1 Signed-off-by: Lei YU <mine260309@gmail.com> Signed-off-by: Guenter Roeck <linux@roeck-us.net> Signed-off-by: Joel Stanley <joel@jms.id.au>
* hwmon: (pmbus/lm25066) Add support for TI LM5066IXo Wang2017-09-121-2/+7
| | | | | | | | | | | | The TI LM5066I hotswap controller is a more accurate version of the LM5066 device already supported. It has different measurement conversion coefficients than the LM5066, so it needs to be recognized as a different device. Signed-off-by: Xo Wang <xow@google.com> Signed-off-by: Guenter Roeck <linux@roeck-us.net> (cherry picked from commit 5783ec2e5c102a6a04d17e07bd9d008a464ed9bc) Signed-off-by: Joel Stanley <joel@jms.id.au>
* dt-bindings: leds: gpio: Add optional retain-state-shutdown propertyAndrew Jeffery2017-08-291-0/+3
| | | | | | | | | | | | | | On Baseboard Management Controller (BMC) systems it's sometimes necessary for a LED to retain its state across a BMC reset (which is independent of the host system state). Add a devicetree property to describe this behaviour. The property would typically be used in conjunction with 'default-state = "keep"'. Signed-off-by: Andrew Jeffery <andrew@aj.id.au> Acked-by: Pavel Machek <pavel@ucw.cz> Signed-off-by: Jacek Anaszewski <jacek.anaszewski@gmail.com> (cherry picked from commit 6fe7dcf33700a21a8e4441881fbb84384f3fe838) Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
* Documentation: hwmon: Document the IBM CFF power supplyEdward A. James2017-08-141-0/+54
| | | | | | | OpenBMC-Staging-Count: 1 Signed-off-by: Edward A. James <eajames@us.ibm.com> Reviewed-by: Andrew Jeffery <andrew@aj.id.au> Signed-off-by: Joel Stanley <joel@jms.id.au>
* dt-bindings: i2c: Document the IBM CCF power supply version 1Edward A. James2017-08-141-0/+21
| | | | | | OpenBMC-Staging-Count: 1 Signed-off-by: Edward A. James <eajames@us.ibm.com> Signed-off-by: Joel Stanley <joel@jms.id.au>
* Documentation: dt-bindings: aspeed-pwm-tacho cooling device.Mykola Kostenok2017-08-141-0/+9
| | | | | | | | | | | | | It's add support for cooling device creation to aspeed-pwm-tacho. Cooling device could be bound to a thermal zone for the thermal control. Signed-off-by: Mykola Kostenok <c_mykolak@mellanox.com> Acked-by: Rob Herring <robh@kernel.org> Signed-off-by: Guenter Roeck <linux@roeck-us.net> (cherry picked from commit 5e047541c1412f22d1c0950260da337ebc9bdb49) Signed-off-by: Joel Stanley <joel@jms.id.au>
* Documentation: dt-bindings: Document bindings for ASPEED AST2400/AST2500 PWM ↵Jaghathiswari Rankappagounder Natarajan2017-08-141-0/+68
| | | | | | | | | | | | | | | and Fan tach controller device driver This binding provides interface for adding values related to ASPEED AST2400/2500 PWM and Fan tach controller support. The PWM controller can support upto 8 PWM output ports. The Fan tach controller can support upto 16 tachometer inputs. Signed-off-by: Jaghathiswari Rankappagounder Natarajan <jaghu@google.com> Acked-by: Rob Herring <robh@kernel.org> Signed-off-by: Guenter Roeck <linux@roeck-us.net> (cherry picked from commit d702b353b9d3fccbeabba96ed530ffc87f303465) Signed-off-by: Joel Stanley <joel@jms.id.au>
* dt-bindings: fsi: Add optional property no-scan-on-initChristopher Bostic2017-08-081-0/+7
| | | | | | | | | | | | Add an optional FSI master property 'no-scan-on-init. This can be specified to indicate that a master should not be automatically scanned at init time. This is required in cases where a scan could interfere with another FSI master on the same bus. OpenBMC-Staging-Count: 1 Signed-off-by: Christopher Bostic <cbostic@linux.vnet.ibm.com> Signed-off-by: Joel Stanley <joel@jms.id.au>
* dt-bindings: max31785: Add use-stored-presence propertyAndrew Jeffery2017-08-011-0/+6
| | | | | | | | | | | It's a system design decision with regards to managing the default values of registers such as FAN_CONFIG_1_2. Do not assume the hardware is configured such as the fans are marked as installed, rather expose a devicetree property to inform the driver of whether it should treat the devicetree or the device state as canonical. Signed-off-by: Andrew Jeffery <andrew@aj.id.au> Signed-off-by: Joel Stanley <joel@jms.id.au>
* dt-bindings: watchdog: aspeed: External reset signal propertiesAndrew Jeffery2017-08-011-1/+9
| | | | | | | | | | | For the AST2500 and compatible watchdog controllers the external reset signal can be configured for push-pull or open-drain drive types, and in the case of open-drain driving, active low or high. OpenBMC-Staging-Count: 1 Signed-off-by: Andrew Jeffery <andrew@aj.id.au> Tested-by: Matt Spinler <mspinler@linux.vnet.ibm.com> Signed-off-by: Joel Stanley <joel@jms.id.au>
* drivers/serial: Add driver for Aspeed virtual UARTJeremy Kerr2017-07-312-0/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This change adds a driver for the 16550-based Aspeed virtual UART device. We use a similar process to the of_serial driver for device probe, but expose some VUART-specific functions through sysfs too. The VUART is two UART 'front ends' connected by their FIFO (no actual serial line in between). One is on the BMC side (management controller) and one is on the host CPU side. This driver is for the BMC side. The sysfs files allow the BMC userspace, which owns the system configuration policy, to specify at what IO port and interrupt number the host side will appear to the host on the Host <-> BMC LPC bus. It could be different on a different system (though most of them use 3f8/4). OpenPOWER host firmware doesn't like it when the host-side of the VUART's FIFO is not drained. This driver only disables host TX discard mode when the port is in use. We set the VUART enabled bit when we bind to the device, and clear it on unbind. We don't want to do this on open/release, as the host may be using this bit to configure serial output modes, which is independent of whether the devices has been opened by BMC userspace. Signed-off-by: Jeremy Kerr <jk@ozlabs.org> Signed-off-by: Joel Stanley <joel@jms.id.au> Acked-by: Rob Herring <robh@kernel.org> Reviewed-by: Benjamin Herrenschmidt <benh@kernel.crashing.org> Reviewed-by: Andy Shevchenko <andy.shevchenko@gmail.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> (cherry picked from commit 7fbcf3afe6e8e180bfc39fb3f41657fa6e4af55c) Signed-off-by: Joel Stanley <joel@jms.id.au>
* Revert "drivers/serial: Add driver for Aspeed virtual UART"Joel Stanley2017-07-311-1/+0
| | | | This reverts commit 969ba225f4bcd109e34ae9d6b40429a32e756ed4.
* dt-bindings: hwmon: pmbus: Add Maxim MAX31785 documentationAndrew Jeffery2017-07-281-0/+117
| | | | | | OpenBMC-Staging-Count: 1 Signed-off-by: Andrew Jeffery <andrew@aj.id.au> Signed-off-by: Joel Stanley <joel@jms.id.au>
* drivers/watchdog: Add optional ASPEED device tree propertiesChristopher Bostic2017-07-071-0/+35
| | | | | | | | | | | | | | | | | | | | | | | Describe device tree optional properties: * aspeed,reset-type = "cpu|soc|system|none" One of three different, mutually exclusive, values "cpu" : ARM CPU reset on signal "soc" : 'System on chip' reset "system" : Full system reset The value can also be set to "none" which indicates that no reset of any kind is to be done via this watchdog. This assumes another watchdog on the chip is to take care of resets. * aspeed,interrupt - Interrupt CPU on signal * aspeed,external-signal - Generate external signal (WDT1 and WDT2 only) * aspeed,alt-boot - Boot from alternate block on signal OpenBMC-Staging-Count: 1 Signed-off-by: Christopher Bostic <cbostic@linux.vnet.ibm.com> Signed-off-by: Joel Stanley <joel@jms.id.au>
* dt-bindings: timeriomem_rng: Add entropy quality propertyRick Altherr2017-07-071-0/+7
| | | | | | | Signed-off-by: Rick Altherr <raltherr@google.com> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au> (cherry picked from commit b14c53451719dc6ec8e6387e5be3be23294a6f1d) Signed-off-by: Joel Stanley <joel@jms.id.au>
* dt-bindings leds: add pca955xCédric Le Goater2017-06-161-0/+88
| | | | | | | | This adds the devicetree bindings for the PCA955x I2C LED blinkers. OpenBMC-Staging-Count: 1 Signed-off-by: Cédric Le Goater <clg@kaod.org> Signed-off-by: Joel Stanley <joel@jms.id.au>
* hwmon: Add support for MAX31785 intelligent fan controllerAndrew Jeffery2017-06-061-0/+44
| | | | | | | | | | | | | Add a basic driver for the MAX31785, focusing on the fan control features but ignoring the temperature and voltage monitoring features of the device. This driver supports all fan control modes and tachometer / PWM readback where applicable. Signed-off-by: Timothy Pearson <tpearson@raptorengineering.com> Signed-off-by: Andrew Jeffery <andrew@aj.id.au> Signed-off-by: Joel Stanley <joel@jms.id.au>
* serial: 8250_of: Add reset supportJoel Stanley2017-06-061-0/+1
| | | | | | | | | | | This adds the hooks for an optional reset controller in the 8250 device tree node. Signed-off-by: Joel Stanley <joel@jms.id.au> Reviewed-by: Philipp Zabel <p.zabel@pengutronix.de> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> (cherry picked from commit e2860e1f62f2e87d268403a749ba1f19663ef19f) Signed-off-by: Joel Stanley <joel@jms.id.au>
* drivers: hwmon: Support for ASPEED PWM/Fan tachJaghathiswari Rankappagounder Natarajan2017-06-061-0/+22
| | | | | | | | | | | | | | | | | The ASPEED AST2400/2500 PWM controller supports 8 PWM output ports. The ASPEED AST2400/2500 Fan tach controller supports 16 tachometer inputs. The device driver matches on the device tree node. The configuration values are read from the device tree and written to the respective registers. The driver provides a sysfs entries through which the user can configure the duty-cycle value (ranging from 0 to 100 percent) and read the fan tach rpm value. Signed-off-by: Jaghathiswari Rankappagounder Natarajan <jaghu@google.com> Signed-off-by: Guenter Roeck <linux@roeck-us.net> (cherry picked from commit 2d7a548a3eff382da5cd743670693b7657327714) Signed-off-by: Joel Stanley <joel@jms.id.au>
* mfd: dt: Add Aspeed Low Pin Count Controller bindingsAndrew Jeffery2017-06-051-0/+111
| | | | | | | | | | Signed-off-by: Andrew Jeffery <andrew@aj.id.au> Reviewed-by: Linus Walleij <linus.walleij@linaro.org> Reviewed-by: Joel Stanley <joel@jms.id.au> Acked-by: Rob Herring <robh@kernel.org> Signed-off-by: Lee Jones <lee.jones@linaro.org> (cherry picked from commit 3bca0e552f693a7d815d24d8fda1196f2c668074) Signed-off-by: Joel Stanley <joel@jms.id.au>
* Merge tag 'v4.10.17' into dev-4.10Joel Stanley2017-06-054-6/+9
|\ | | | | | | This is the 4.10.17 stable release
| * watchdog: s3c2410: Fix infinite interrupt in soft modeKrzysztof Kozlowski2017-04-121-4/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | [ Upstream commit 0b445549ea6f91ffea78a976fe89b932db6e077a ] In soft (no-reboot) mode, the driver self-pings watchdog upon expiration of an interrupt. However the interrupt itself was not cleared thus on first hit, the system enters infinite interrupt handling loop. On Odroid U3 (Exynos4412), when booted with s3c2410_wdt.soft_noboot=1 argument the console is flooded: # killall -9 watchdog [ 60.523760] s3c2410-wdt 10060000.watchdog: watchdog timer expired (irq) [ 60.536744] s3c2410-wdt 10060000.watchdog: watchdog timer expired (irq) Fix this by writing something to the WTCLRINT register to clear the interrupt. The register WTCLRINT however appeared in S3C6410 so a new watchdog quirk and flavor are needed. Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org> Reviewed-by: Guenter Roeck <linux@roeck-us.net> Signed-off-by: Guenter Roeck <linux@roeck-us.net> Signed-off-by: Sasha Levin <alexander.levin@verizon.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
| * usb: host: xhci-plat: enable BROKEN_PED quirk if platform requestedFelipe Balbi2017-04-121-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | [ Upstream commit 21939f003ad09355d9c975735750bb22aa37d8de ] In case 'quirk-broken-port-ped' property is passed in via device property, we should enable the corresponding BROKEN_PED quirk flag for XHCI core. [rogerq@ti.com] Updated code from platform data to device property and added DT binding. Signed-off-by: Felipe Balbi <balbi@ti.com> Signed-off-by: Roger Quadros <rogerq@ti.com> Signed-off-by: Mathias Nyman <mathias.nyman@linux.intel.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Signed-off-by: Sasha Levin <alexander.levin@verizon.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
| * Documentation: stable-kernel-rules: fix stable-tag formatJohan Hovold2017-04-121-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | commit cf903e9d3a97f89b224d2d07be37c0f160db8192 upstream. A patch documenting how to specify which kernels a particular fix should be backported to (seemingly) inadvertently added a minus sign after the kernel version. This particular stable-tag format had never been used prior to this patch, and was neither present when the patch in question was first submitted (it was added in v2 without any comment). Drop the minus sign to avoid any confusion. Fixes: fdc81b7910ad ("stable_kernel_rules: Add clause about specification of kernel versions to patch.") Signed-off-by: Johan Hovold <johan@kernel.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
| * dt-bindings: rng: clocks property on omap_rng not always mandatoryThomas Petazzoni2017-04-081-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | commit 74d1cf4897f919837efc4e34d800b996936eb38e upstream. Commit 52060836f79 ("dt-bindings: omap-rng: Document SafeXcel IP-76 device variant") update the omap_rng Device Tree binding to add support for the IP-76 variation of the IP. As part of this change, a "clocks" property was added, but is indicated as "Required", without indicated it's actually only required for some compatible strings. This commit fixes that, by explicitly stating that the clocks property is only required with the inside-secure,safexcel-eip76 compatible string. Fixes: 52060836f79 ("dt-bindings: omap-rng: Document SafeXcel IP-76 device variant") Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
* | dt-bindings: fsi: Add specification for FSI bussesJeremy Kerr2017-06-011-0/+144
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This change introduces a proposed layout for describing FSI busses in the device tree. While the bus is probe-able, we'd still like a method of describing subordinate (eg i2c) busses that are behind FSI devices. The FSI core will be responsible for matching probed slaves & engines to their device tree nodes, so the FSI device drivers' probe() functions will be passed a struct device with the appropriate of_node populated where a matching DT node is found. OpenBMC-Staging-Count: 1 Signed-off-by: Jeremy Kerr <jk@ozlabs.org> Acked-by: Rob Herring <robh@kernel.org> Signed-off-by: Joel Stanley <joel@jms.id.au>
* | ARM: dts: aspeed: Add Mellanox MSN machineMykola Kostenok2017-05-311-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | Initial introduction of Mellanox switches of MSNXXXX family equipped with Aspeed 2520 BMC SoC. This adds msn platform device tree file including the flash layout used by MSN machines. OpenBMC-Staging-Count: 1 Signed-off-by: Mykola Kostenok <c_mykolak@mellanox.com> Acked-by: Andrew Jeffery <andrew@aj.id.au> [joel: fixed redundant i2c aliases, tweaked commit message] Signed-off-by: Joel Stanley <joel@jms.id.au>
* | arm: dts: aspeed: Add IR35221 instances to dev treeChristopher Bostic2017-05-241-0/+1
| | | | | | | | | | | | | | Add IR35221 to i2c4 and i2c5 buses. Signed-off-by: Christopher Bostic <cbostic@linux.vnet.ibm.com> Signed-off-by: Joel Stanley <joel@jms.id.au>
* | hwmon: (pmbus) Add client driver for IR35221Samuel Mendoza-Jonas2017-05-021-0/+87
| | | | | | | | | | | | | | | | | | | | IR35221 is a Digital DC-DC Multiphase Converter Signed-off-by: Samuel Mendoza-Jonas <sam@mendozajonas.com> [groeck: Preserve alphabetic order in Kconfig] Signed-off-by: Guenter Roeck <linux@roeck-us.net> (cherry picked from commit 6eaaea144dc58b66712f8a4c6cbc4a90427e1365) Signed-off-by: Joel Stanley <joel@jms.id.au>
* | i2c: aspeed: added documentation for Aspeed I2C driverBrendan Higgins2017-04-271-0/+47
| | | | | | | | | | | | | | | | Added device tree binding documentation for Aspeed I2C busses. OpenBMC-Staging-Count: 1 Signed-off-by: Brendan Higgins <brendanhiggins@google.com> Signed-off-by: Joel Stanley <joel@jms.id.au>
* | irqchip/aspeed-i2c-ic: binding docs for Aspeed I2C Interrupt ControllerBrendan Higgins2017-04-271-0/+25
| | | | | | | | | | | | | | | | | | Added device tree binding documentation for Aspeed I2C Interrupt Controller. OpenBMC-Staging-Count: 1 Signed-off-by: Brendan Higgins <brendanhiggins@google.com> Signed-off-by: Joel Stanley <joel@jms.id.au>
* | ftgmac100: Document device-tree bindingBenjamin Herrenschmidt2017-04-271-0/+35
| | | | | | | | | | | | | | Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org> Signed-off-by: David S. Miller <davem@davemloft.net> (cherry picked from commit 88a286f7e9df643e211debe55a7aa206d2332763) Signed-off-by: Joel Stanley <joel@jms.id.au>
* | gpio: aspeed: dt: Add optional clocks propertyAndrew Jeffery2017-04-271-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | We need a reference to the HPLL to calculate debounce cycles. If the clocks property is not supplied in the GPIO node then the consumer should deny any debounce requests. Signed-off-by: Andrew Jeffery <andrew@aj.id.au> Acked-by: Rob Herring <robh@kernel.org> Signed-off-by: Linus Walleij <linus.walleij@linaro.org> (cherry picked from commit 9d7163f5167fa60e71071ab6dcb60da0f7230beb) Signed-off-by: Joel Stanley <joel@jms.id.au>
* | gpio: aspeed: dt: Fix description alignment in bindings documentAndrew Jeffery2017-04-271-1/+1
| | | | | | | | | | | | | | | | Signed-off-by: Andrew Jeffery <andrew@aj.id.au> Acked-by: Rob Herring <robh@kernel.org> Signed-off-by: Linus Walleij <linus.walleij@linaro.org> (cherry picked from commit cea956551f1f0edb2d64a0320785705e400ae5f1) Signed-off-by: Joel Stanley <joel@jms.id.au>
* | pinctrl: aspeed: Document pinconf in devicetree bindingsAndrew Jeffery2017-04-271-9/+31
| | | | | | | | | | | | | | | | | | Signed-off-by: Andrew Jeffery <andrew@aj.id.au> Acked-by: Rob Herring <robh@kernel.org> Acked-by: Joel Stanley <joel@jms.id.au> Signed-off-by: Linus Walleij <linus.walleij@linaro.org> (cherry picked from commit 6de2185bc70781efd8ec26ff45329b57288d1880) Signed-off-by: Joel Stanley <joel@jms.id.au>
* | pinctrl / gpio: Introduce .set_config() callback for GPIO chipsMika Westerberg2017-04-271-4/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Currently we already have two pin configuration related callbacks available for GPIO chips .set_single_ended() and .set_debounce(). In future we expect to have even more, which does not scale well if we need to add yet another callback to the GPIO chip structure for each possible configuration parameter. Better solution is to reuse what we already have available in the generic pinconf. To support this, we introduce a new .set_config() callback for GPIO chips. The callback takes a single packed pin configuration value as parameter. This can then be extended easily beyond what is currently supported by just adding new types to the generic pinconf enum. If the GPIO driver is backed up by a pinctrl driver the GPIO driver can just assign gpiochip_generic_config() (introduced in this patch) to .set_config and that will take care configuration requests are directed to the pinctrl driver. We then convert the existing drivers over .set_config() and finally remove the .set_single_ended() and .set_debounce() callbacks. Suggested-by: Linus Walleij <linus.walleij@linaro.org> Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com> Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com> Signed-off-by: Linus Walleij <linus.walleij@linaro.org> (cherry picked from commit 2956b5d94a76b596fa5057c2b3ca915cb27d7652) Signed-off-by: Joel Stanley <joel@jms.id.au>
* | drivers/fsi: Document FSI master sysfs files in ABIChris Bostic2017-04-271-0/+6
| | | | | | | | | | | | | | | | Add info for sysfs scan file in Documentaiton ABI/testing OpenBMC-Staging-Count: 1 Signed-off-by: Chris Bostic <cbostic@linux.vnet.ibm.com> Signed-off-by: Joel Stanley <joel@jms.id.au>
* | drivers/fsi: Add documentation for GPIO bindingsChris Bostic2017-04-271-0/+24
| | | | | | | | | | | | | | | | | | Add fsi master gpio device tree binding documentation OpenBMC-Staging-Count: 1 Signed-off-by: Chris Bostic <cbostic@linux.vnet.ibm.com> Acked-by: Rob Herring <robh@kernel.org> Signed-off-by: Joel Stanley <joel@jms.id.au>
* | Documentation: dt-bindings: Document bindings for Aspeed ADCRick Altherr2017-03-301-0/+20
| | | | | | | | | | | | | | OpenBMC-Staging-Count: 1 Signed-off-by: Rick Altherr <raltherr@google.com> Acked-by: Joel Stanley <joel@jms.id.au> Signed-off-by: Joel Stanley <joel@jms.id.au>
* | ipmi: bt-bmc: Add ast2500 compatible stringJoel Stanley2017-03-231-1/+3
| | | | | | | | | | | | | | | | The ast2500 SoCs contain the same IPMI BT device as the ast2400. OpenBMC-Staging-Count: 1 Reviewed-by: Cédric Le Goater <clg@kaod.org> Signed-off-by: Joel Stanley <joel@jms.id.au>
* | drivers/serial: Add driver for Aspeed virtual UARTJeremy Kerr2017-03-231-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This change adds a driver for the 16550-based Aspeed virtual UART device. We use a similar process to the of_serial driver for device probe, but expose some VUART-specific functions through sysfs too. If host TX discard mode is enabled, we don't see the LSR[RBR} bit getting set on new characters written on the host side. This makes the VUART a little useless. OpenPOWER firmware doesn't like it when the host-side of the VUART's FIFO is not drained. This change only disables host TX discard mode when the port is in use. We set the VUART enabled bit when we bind to the device, and clear it on unbind. We don't want to do this on open/release, as the host may be using this bit to configure serial output modes, which is independent of whether the devices has been opened by BMC userspace. OpenBMC-Staging-Count: 1 Signed-off-by: Jeremy Kerr <jk@ozlabs.org> Signed-off-by: Xo Wang <xow@google.com> Signed-off-by: Joel Stanley <joel@jms.id.au>
* | dt-bindings: mtd: add a common label property to all mtd devicesCédric Le Goater2017-03-231-0/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | This can be used to easily identify a specific chip on a system with multiple chips. Signed-off-by: Cédric Le Goater <clg@kaod.org> Acked-by: Boris Brezillon <boris.brezillon@free-electrons.com> Acked-by: Rob Herring <robh@kernel.org> Reviewed-by: Marek Vasut <marek.vasut@gmail.com> Signed-off-by: Brian Norris <computersforpeace@gmail.com> (cherry picked from commit 2bfc7452742617fe1182b742917e6e9032eae52c) Signed-off-by: Joel Stanley <joel@jms.id.au>
* | pinctrl: aspeed-g5: Add mux configuration for all pinsAndrew Jeffery2017-03-231-4/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The patch introducing the g5 pinctrl driver implemented a smattering of pins to flesh out the implementation of the core and provide bare-bones support for some OpenPOWER platforms and the AST2500 evaluation board. Now, update the bindings document to reflect the complete functionality and implement the necessary pin configuration tables in the driver. Signed-off-by: Andrew Jeffery <andrew@aj.id.au> Acked-by: Joel Stanley <joel@jms.id.au> Acked-by: Rob Herring <robh@kernel.org> Signed-off-by: Linus Walleij <linus.walleij@linaro.org> (cherry picked from commit f1337856dd88858bf58bd062306ccbfb63303085) Signed-off-by: Joel Stanley <joel@jms.id.au>
* | pinctrl: aspeed-g4: Add mux configuration for all pinsAndrew Jeffery2017-03-231-7/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The patch introducing the g4 pinctrl driver implemented a smattering of pins to flesh out the implementation of the core and provide bare-bones support for some OpenPOWER platforms. Now, update the bindings document to reflect the complete functionality and implement the necessary pin configuration tables in the driver. Cc: Timothy Pearson <tpearson@raptorengineering.com> Signed-off-by: Andrew Jeffery <andrew@aj.id.au> Acked-by: Joel Stanley <joel@jms.id.au> Acked-by: Rob Herring <robh@kernel.org> Signed-off-by: Linus Walleij <linus.walleij@linaro.org> (cherry picked from commit 6d329f14a75f3858a1254abca8b94d4fab556a9a) Signed-off-by: Joel Stanley <joel@jms.id.au>
* | pinctrl: aspeed: Read and write bits in LPC and GFX controllersAndrew Jeffery2017-03-231-9/+71
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The System Control Unit IP block in the Aspeed SoCs is typically where the pinmux configuration is found, but not always. A number of pins depend on state in one of LPC Host Control (LHC) or SoC Display Controller (GFX) IP blocks, so the Aspeed pinmux drivers should have the means to adjust these as necessary. We use syscon to cast a regmap over the GFX and LPC blocks, which is used as an arbitration layer between the relevant driver and the pinctrl subsystem. The regmaps are then exposed to the SoC-specific pinctrl drivers by phandles in the devicetree, and are selected during a mux request by querying a new 'ip' member in struct aspeed_sig_desc. Signed-off-by: Andrew Jeffery <andrew@aj.id.au> Reviewed-by: Joel Stanley <joel@jms.id.au> Acked-by: Rob Herring <robh@kernel.org> Signed-off-by: Linus Walleij <linus.walleij@linaro.org> (cherry picked from commit 7d29ed88acbbf00e2056634bd4c0172d55d2568c) Signed-off-by: Joel Stanley <joel@jms.id.au>
* | pinctrl: aspeed: dt: Fix compatibles for the System Control UnitAndrew Jeffery2017-03-231-3/+8
|/ | | | | | | | | | | | Reference the SoC-specific compatible string in the examples as required. Signed-off-by: Andrew Jeffery <andrew@aj.id.au> Acked-by: Joel Stanley <joel@jms.id.au> Acked-by: Rob Herring <robh@kernel.org> Signed-off-by: Linus Walleij <linus.walleij@linaro.org> (cherry picked from commit c95b0fec3cff0ba584fd2f9e71fd9001ad15381a) Signed-off-by: Joel Stanley <joel@jms.id.au>
* irqchip/gicv3-its: Add workaround for QDF2400 ITS erratum 0065Shanker Donthineni2017-03-221-21/+23
| | | | | | | | | | | | | | | | | | | | | commit 90922a2d03d84de36bf8a9979d62580102f31a92 upstream. On Qualcomm Datacenter Technologies QDF2400 SoCs, the ITS hardware implementation uses 16Bytes for Interrupt Translation Entry (ITE), but reports an incorrect value of 8Bytes in GITS_TYPER.ITTE_size. It might cause kernel memory corruption depending on the number of MSI(x) that are configured and the amount of memory that has been allocated for ITEs in its_create_device(). This patch fixes the potential memory corruption by setting the correct ITE size to 16Bytes. Cc: stable@vger.kernel.org Signed-off-by: Shanker Donthineni <shankerd@codeaurora.org> Signed-off-by: Marc Zyngier <marc.zyngier@arm.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
* x86/platform/goldfish: Prevent unconditional loadingThomas Gleixner2017-02-261-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | commit 47512cfd0d7a8bd6ab71d01cd89fca19eb2093eb upstream. The goldfish platform code registers the platform device unconditionally which causes havoc in several ways if the goldfish_pdev_bus driver is enabled: - Access to the hardcoded physical memory region, which is either not available or contains stuff which is completely unrelated. - Prevents that the interrupt of the serial port can be requested - In case of a spurious interrupt it goes into a infinite loop in the interrupt handler of the pdev_bus driver (which needs to be fixed seperately). Add a 'goldfish' command line option to make the registration opt-in when the platform is compiled in. I'm seriously grumpy about this engineering trainwreck, which has seven SOBs from Intel developers for 50 lines of code. And none of them figured out that this is broken. Impressive fail! Fixes: ddd70cf93d78 ("goldfish: platform device for x86") Reported-by: Gabriel C <nix.or.die@gmail.com> Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Acked-by: Linus Torvalds <torvalds@linux-foundation.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
* Merge tag 'media/v4.10-4' of ↵Linus Torvalds2017-02-141-6/+17
|\ | | | | | | | | | | | | | | | | | | | | | | git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media Pull media fixes from Mauro Carvalho Chehab: "A colorspace regression fix in V4L2 core and a CEC core bug that makes it discard valid messages" * tag 'media/v4.10-4' of git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media: [media] cec: initiator should be the same as the destination for, poll [media] videodev2.h: go back to limited range Y'CbCr for SRGB and, ADOBERGB
| * [media] videodev2.h: go back to limited range Y'CbCr for SRGB and, ADOBERGBHans Verkuil2017-02-131-6/+17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This reverts 'commit 7e0739cd9c40 ("[media] videodev2.h: fix sYCC/AdobeYCC default quantization range"). The problem is that many drivers can convert R'G'B' content (often from sensors) to Y'CbCr, but they all produce limited range Y'CbCr. To stay backwards compatible the default quantization range for sRGB and AdobeRGB Y'CbCr encoding should be limited range, not full range, even though the corresponding standards specify full range. Update the V4L2_MAP_QUANTIZATION_DEFAULT define accordingly and also update the documentation. Fixes: 7e0739cd9c40 ("[media] videodev2.h: fix sYCC/AdobeYCC default quantization range") Signed-off-by: Hans Verkuil <hans.verkuil@cisco.com> Cc: <stable@vger.kernel.org> # for v4.9 and up Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
OpenPOWER on IntegriCloud