summaryrefslogtreecommitdiff
path: root/net
diff options
context:
space:
mode:
authorMasahiro Yamada <yamada.masahiro@socionext.com>2016-03-24 13:32:44 (GMT)
committerMasahiro Yamada <yamada.masahiro@socionext.com>2016-03-31 15:54:00 (GMT)
commit8cc92b996ddecd4c364d0bbb474c3569ebec55c7 (patch)
tree6a726da2b75e7e8f4a495519c19fde6a6c3ecdbb /net
parent510454db045143e374a7d64e6bb043799d0023d7 (diff)
downloadu-boot-fsl-qoriq-8cc92b996ddecd4c364d0bbb474c3569ebec55c7.tar.xz
pinctrl: uniphier: introduce capability flag
The core part of the UniPhier pinctrl driver needs to support a new capability for upcoming UniPhier ARMv8 SoCs. This sometimes happens because pinctrl drivers include really SoC-specific stuff. This commit intends to tidy up SoC-specific parameters of the existing drivers before adding new ones. Having flags would be better than adding new members every time a new SoC-specific capability comes up. At this time, there is one flag, UNIPHIER_PINCTRL_CAPS_DBGMUX_SEPARATE. This capability (I'd say rather quirk) was added for PH1-Pro4 and PH1-Pro5 as requirement from our customer. For those SoCs, one pin-mux setting is controlled by the combination of two separate registers; the LSB bits at register offset (8 * N) and the MSB bits at (8 * N + 4). Because it is impossible to update two separate registers atomically, the LOAD_PINCTRL register should be set in order to make the pin-mux settings really effective. Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Diffstat (limited to 'net')
0 files changed, 0 insertions, 0 deletions