summaryrefslogtreecommitdiff
path: root/drivers/i2c/busses/i2c-brcmstb.c
diff options
context:
space:
mode:
authorBrian Norris <briannorris@chromium.org>2022-03-08 22:08:53 +0300
committerChanwoo Choi <cw00.choi@samsung.com>2022-04-14 01:18:11 +0300
commitb82acf8215c40fcb7d29e34aab17c51df58c4f40 (patch)
tree12b897cbf09c76a32558b46b79945c6645d13fb2 /drivers/i2c/busses/i2c-brcmstb.c
parent5f50c52f13f12d63699feaae54ee2b1e4aee5a86 (diff)
downloadlinux-b82acf8215c40fcb7d29e34aab17c51df58c4f40.tar.xz
PM / devfreq: rk3399_dmc: Drop excess timing properties
All of these properties are initialized by ARM Trusted Firmware, and have been since the early days of this chip. It's redundant (and possibly wrong) to do this here now. What's more, there seems to be some confusion about the units and some of the definitions of this timing struct: the DT docs say MHz for many of these, but downstream users were in Hz (and therefore, the ATF interface was Hz). Also, the in-driver usage for some of these (e.g., for comparing to target frequency) were in Hz too. So doubly wrong. We can avoid thinking about who got the right units by dropping the unnecessary code and properties. They are marked deprecated in the binding schema. Signed-off-by: Brian Norris <briannorris@chromium.org> Signed-off-by: Chanwoo Choi <cw00.choi@samsung.com>
Diffstat (limited to 'drivers/i2c/busses/i2c-brcmstb.c')
0 files changed, 0 insertions, 0 deletions