summaryrefslogtreecommitdiff
path: root/block/blk-wbt.c
diff options
context:
space:
mode:
authorChen-Yu Tsai <wenst@chromium.org>2021-07-26 14:19:41 +0300
committerLinus Walleij <linus.walleij@linaro.org>2021-08-11 12:05:14 +0300
commit936c985478716b228f42f47c075d4ea10dfa98bb (patch)
tree3a64fa055d97b8e04fe75b3e6e233db51ce97073 /block/blk-wbt.c
parent379e28b5b36f523e5afd9c129505580024613e22 (diff)
downloadlinux-936c985478716b228f42f47c075d4ea10dfa98bb.tar.xz
dt-bindings: pinctrl: mt8195: Use real world values for drive-strength arguments
The original binding submission for MT8195 pinctrl described the possible drive strength values in micro-amps in its description, but then proceeded to list register values in its device tree binding constraints. However, the macros used with the Mediatek pinctrl bindings directly specify the drive strength in micro-amps, instead of hardware register values. The current driver implementation in Linux does convert the value from micro-amps to hardware register values. This implementation is also used with MT7622 and MT8183, which use real world values in their device trees. Given the above, it was likely an oversight to use the raw register values in the binding. Correct the values in the binding. Also drop the description since the binding combined with its parent, pinctrl/pincfg.yaml, the binding is now self-describing. Fixes: 7f7663899d94 ("dt-bindings: pinctrl: mt8195: add pinctrl file and binding document") Signed-off-by: Chen-Yu Tsai <wenst@chromium.org> Acked-by: Rob Herring <robh@kernel.org> Link: https://lore.kernel.org/r/20210726111941.1447057-1-wenst@chromium.org Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
Diffstat (limited to 'block/blk-wbt.c')
0 files changed, 0 insertions, 0 deletions