Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1629515 > unrolled thread
| Started by | Linus Walleij <linus.walleij@linaro.org> |
|---|---|
| First post | 2017-04-24 15:00 +0200 |
| Last post | 2017-04-24 15:00 +0200 |
| Articles | 1 — 1 participant |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [PATCH v2 2/4] pinctrl: aspeed: Add core pinconf support Linus Walleij <linus.walleij@linaro.org> - 2017-04-24 15:00 +0200
| From | Linus Walleij <linus.walleij@linaro.org> |
|---|---|
| Date | 2017-04-24 15:00 +0200 |
| Subject | Re: [PATCH v2 2/4] pinctrl: aspeed: Add core pinconf support |
| Message-ID | <tzLKX-75O-25@gated-at.bofh.it> |
On Fri, Apr 7, 2017 at 2:57 PM, Andrew Jeffery <andrew@aj.id.au> wrote: > 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 <andrew@aj.id.au> Patch applied. Yours, Linus Waleij
Back to top | Article view | linux.kernel
csiph-web