talos-obmc-linux/drivers/pinctrl, branch dev-4.10

pinctrl: aspeed: Rework strap register write logic for the AST2500

2017-12-05T00:34:29+00:00

Yong Li found that writes to the AST2500 strapping register were not properly supported by the Aspeed pinctrl core and provided a patch to rectify the problem. Several revisions of the patch were posted and ultimately v4 should have been applied, however some unfortunate liberal application of tags on my part lead to confusion between v3[1] and v4[2]. Generate the diff between v3 and v4 to apply as a fixup patch. [1] http://patchwork.ozlabs.org/patch/801662/ [2] http://patchwork.ozlabs.org/patch/802946/ Cc: Yong Li Signed-off-by: Andrew Jeffery Signed-off-by: Linus Walleij (cherry picked from commit 5241bd16c7576de3cf189e3e40b01bd4fa10f803) Signed-off-by: Joel Stanley

pinctrl: aspeed: Fix ast2500 strap register write logic

2017-12-05T00:34:25+00:00

On AST2500, the hardware strap register(SCU70) only accepts write ‘1’, to clear it to ‘0’, must set bits(write ‘1’) to SCU7C Signed-off-by: Yong Li Reviewed-by: Andrew Jeffery Tested-by: Andrew Jeffery Signed-off-by: Linus Walleij (cherry picked from commit 1865af212dfa0819ca21c7e5c18c2a75202c1827) Signed-off-by: Joel Stanley

pinctrl: aspeed: Allow disabling Port D and Port E loopback mode

2017-12-05T00:30:52+00:00

Port D and port E GPIO loopback modes are commonly enabled via hardware straps for use with front-panel buttons. When the BMC is powered off or fails to boot, the front-panel buttons are directly connected to the host chipset via the loopback to allow direct power-on and reset control. Once the BMC has booted, the loopback mode must be disabled for the BMC to take over control of host power-on and reset. Disabling these loopback modes requires writing to the hardware strap register which violates the current design of assuming the system designer chose the strap settings for a specific reason and they should be treated as read-only. Only the two bits of the strap register related to these loopback modes are allowed to be written and comments have been added to explain why. Signed-off-by: Rick Altherr Acked-by: Joel Stanley Reviewed-by: Andrew Jeffery Signed-off-by: Linus Walleij (cherry picked from commit c825676b0823fd43a4d08bf865f81bb188b51db1) Signed-off-by: Joel Stanley

Merge tag 'v4.10.17' into dev-4.10

2017-06-05T02:24:15+00:00

This is the 4.10.17 stable release

pinctrl: aspeed: Fix unused-const-variable warnings

2017-04-27T06:09:58+00:00

Three video input signals suffered from a search/replace failure in some copied code. Signed-off-by: Andrew Jeffery Signed-off-by: Linus Walleij (cherry picked from commit 03ffb507c8c4998fa85d3efae70cb18085457263) Signed-off-by: Joel Stanley

pinctrl: aspeed: g5: Add pinconf support

2017-04-27T05:03:51+00:00

Testing for pinctrl-aspeed-g5 was performed on an AST2500EVB system, using the strategy outlined in the commit message for the change to the Aspeed pinctrl core. Signed-off-by: Andrew Jeffery Signed-off-by: Linus Walleij (cherry picked from commit d0639d39fe977608a60e45fb51e25c17661a7ec0) Signed-off-by: Joel Stanley

pinctrl: aspeed: g4: Add pinconf support

2017-04-27T05:03:50+00:00

Testing for pinctrl-aspeed-g4 was performed on an OpenPOWER Palmetto system, using the strategy outlined in the commit message for the change to the Aspeed pinctrl core. Signed-off-by: Andrew Jeffery Signed-off-by: Linus Walleij (cherry picked from commit 47b50b3743cd6a9c2a90372181cfc9ee5b10186d) Signed-off-by: Joel Stanley

pinctrl: aspeed: Add core pinconf support

2017-04-27T05:03:50+00:00

Several pinconf parameters have a fairly straight-forward mapping onto the Aspeed pin controller. These include management of pull-down bias, drive-strength, and some debounce configuration. Pin biasing largely is managed on a per-GPIO-bank basis, aside from the ADC and RMII/RGMII pins. As the bias configuration for each pin in a bank maps onto a single per-bank bit, configuration tables will be introduced to describe the ranges of pins and the supported pinconf parameter. The use of tables also helps with the sparse support of pinconf properties, and the fact that not all GPIO banks support biasing or drive-strength configuration. Further, as the pin controller uses a consistent approach for bias and drive strength configuration at the register level, a second table is defined for looking up the the bit-state required to enable or query the provided configuration. Testing for pinctrl-aspeed-g4 was performed on an OpenPOWER Palmetto system, and pinctrl-aspeed-g5 on an AST2500EVB as well as under QEMU. The test method was to set the appropriate bits via devmem and verify the result through the controller's pinconf-pins debugfs file. This simultaneously validates the get() path and half of the set() path. The remainder of the set() path was validated by configuring a handful of pins via the devicetree with the supported pinconf properties and verifying the appropriate registers were touched. Signed-off-by: Andrew Jeffery Signed-off-by: Linus Walleij (cherry picked from commit 7f354fd13877aae8abcd7b5a389cc85e3d2e4ed1) Signed-off-by: Joel Stanley

pinctrl / gpio: Introduce .set_config() callback for GPIO chips

2017-04-27T05:03:49+00:00

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 Signed-off-by: Mika Westerberg Reviewed-by: Andy Shevchenko Signed-off-by: Linus Walleij (cherry picked from commit 2956b5d94a76b596fa5057c2b3ca915cb27d7652) Signed-off-by: Joel Stanley

pinctrl: Allow configuration of pins from gpiolib based drivers

2017-04-27T05:03:48+00:00

When a GPIO driver is backed by a pinctrl driver the GPIO driver sometimes needs to call the pinctrl driver to configure certain things, like whether the pin is used as input or output. In addition to this there are other configurations applicable to GPIOs such as setting debounce time of the GPIO. To support this we introduce a new function pinctrl_gpio_set_config() that can be used by gpiolib based driver to pass configuration requests to the backing pinctrl driver. Signed-off-by: Mika Westerberg Reviewed-by: Andy Shevchenko Signed-off-by: Linus Walleij (cherry picked from commit 15381bc7c7f52d56f87c56dd7c948ad78704b852) Signed-off-by: Joel Stanley