summaryrefslogtreecommitdiffstats
path: root/drivers/pinctrl
diff options
context:
space:
mode:
authorRafał Miłecki <rafal@milecki.pl>2018-12-18 16:57:44 +0100
committerLinus Walleij <linus.walleij@linaro.org>2018-12-21 11:44:06 +0100
commit2ae80900f239484069569380e1fc4340fd6e0089 (patch)
treeee05a19dd93c344246c0e7bf424ec7b5b817a3e0 /drivers/pinctrl
parent6ac5af6ec12dadca37dd86f93a4125f6a04ffb4c (diff)
downloadlinux-stable-2ae80900f239484069569380e1fc4340fd6e0089.tar.gz
linux-stable-2ae80900f239484069569380e1fc4340fd6e0089.tar.bz2
linux-stable-2ae80900f239484069569380e1fc4340fd6e0089.zip
dt-bindings: pinctrl: bcm4708-pinmux: rework binding to use syscon
As pointed by Rob, CRU is a kind of block that can't be guaranteed to have everything exposed as subnodes. It's a set of various registers that aren't tied to any single device. It could be described much more accurately as MFD (Multi-Function Device). Some hardware blocks may indeed want to access a register or two of the CRU which requires describing it as the "syscon". While at it replace exmple node name with the standard "pinctrl" (also pointed out by Rob). Signed-off-by: Rafał Miłecki <rafal@milecki.pl> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
Diffstat (limited to 'drivers/pinctrl')
0 files changed, 0 insertions, 0 deletions