diff options
author | Rafał Miłecki <rafal@milecki.pl> | 2021-10-08 23:59:36 +0300 |
---|---|---|
committer | Linus Walleij <linus.walleij@linaro.org> | 2021-10-14 02:09:06 +0300 |
commit | 0398adaec3419bdfa93baae70a3b696b4abdd7ad (patch) | |
tree | 3cba0e822cf3a31c7a34145ced7cf9b8467b2c66 /Documentation/admin-guide/spkguide.txt | |
parent | 64570fbc14f8d7cb3fe3995f20e26bc25ce4b2cc (diff) | |
download | linux-0398adaec3419bdfa93baae70a3b696b4abdd7ad.tar.xz |
Revert "dt-bindings: pinctrl: bcm4708-pinmux: rework binding to use syscon"
This reverts commit 2ae80900f239484069569380e1fc4340fd6e0089.
My rework was unneeded & wrong. It replaced a clear & correct "reg"
property usage with a custom "offset" one.
Back then I didn't understand how to properly handle CRU block binding.
I heard / read about syscon and tried to use it in a totally invalid
way. That change also missed Rob's review (obviously).
Northstar's pin controller is a simple consistent hardware block that
can be cleanly mapped using a 0x24 long reg space.
Since the rework commit there wasn't any follow up modifying in-kernel
DTS files to use the new binding. Broadcom also isn't known to use that
bugged binding. There is close to zero chance this revert may actually
cause problems / regressions.
This commit is a simple revert. Example binding may (should) be updated
/ cleaned up but that can be handled separately.
Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
Reviewed-by: Rob Herring <robh@kernel.org>
Link: https://lore.kernel.org/r/20211008205938.29925-1-zajec5@gmail.com
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
Diffstat (limited to 'Documentation/admin-guide/spkguide.txt')
0 files changed, 0 insertions, 0 deletions