summaryrefslogtreecommitdiffstats
path: root/drivers/mfd
diff options
context:
space:
mode:
authorGabriel Somlo <gsomlo@gmail.com>2021-01-12 12:31:44 -0500
committerStafford Horne <shorne@gmail.com>2021-01-14 09:52:54 +0900
commit4f70d150294b3ddfbe4be7130ca53898cd5b91be (patch)
treeae8e087a2f74bacfda26c3f3de814f9083a9eab0 /drivers/mfd
parent51f109228308a87c7f2583360e54acfc567203da (diff)
downloadlinux-stable-4f70d150294b3ddfbe4be7130ca53898cd5b91be.tar.gz
linux-stable-4f70d150294b3ddfbe4be7130ca53898cd5b91be.tar.bz2
linux-stable-4f70d150294b3ddfbe4be7130ca53898cd5b91be.zip
drivers/soc/litex: make 'litex_[set|get]_reg()' methods private
The 'litex_[set|get]_reg()' methods use the 'reg_size' parameter to specify the width of the LiteX CSR (MMIO) register being accessed. Since 'u64' is the widest data being supported, the value of 'reg_size' MUST be between 1 and sizeof(u64), which SHOULD be checked at runtime if these methods are publicly available for use by other LiteX device drivers. At the same time, none of the existing (or foreseeable) LiteX device drivers have a need to access registers whose size is unknown during compilation. As such, all LiteX device drivers should use fixed-width accessor methods such as 'litex_[write|read][8|16|32|64]()'. This patch renames 'litex_[set|get]_reg()' to '_litex_[set|get]_reg()', indicating that they should NOT be directly called from outside of the 'include/linux/litex.h' header file. Signed-off-by: Gabriel Somlo <gsomlo@gmail.com> Signed-off-by: Stafford Horne <shorne@gmail.com>
Diffstat (limited to 'drivers/mfd')
0 files changed, 0 insertions, 0 deletions