Sometimes the regulator is shared between several devices, if target rate
and target voltage are equal to initial rate and iniital voltage , the
min_uV and max_uV of regulator will be always equal to zero, other devices
may set a low voltage.
Change-Id: I561971844296ffcada823d741710aba808167e3f
Signed-off-by: Finley Xiao <finley.xiao@rock-chips.com>
Sometimes the regulator is shared between several devices, if target rate
and target voltage are equal to initial rate and iniital voltage , the
min_uV and max_uV of regulator will be always equal to zero, other devices
may set a low voltage.
Change-Id: Ibf82f335ce0739776286e3733be5415f84bf035b
Signed-off-by: Finley Xiao <finley.xiao@rock-chips.com>
If initial rate is greater than opp rate and initial voltage isn't qeual
to opp volatge, the opp voltage may too low for initial rate, so it's
inappropriate to update voltage when initial voltage isn't qeual to
opp volatge.
In order to solve this problem and consider that the regulator is shared
between several devices on some platforms, make the following two changes.
If the driver doesn't support to change frequency, the opp table should
contain an opp whose rate is geater than or equal to initial rate, so that
the voltage is enough for initial rate and the min_uV and max_uV of
regulator aren't equal to zero after update voltage.
If the driver supports to change frequency, let devfreq framework update
rate and voltage.
Change-Id: I4004f55f2cfd3b87f734844a0cdf8e9619d785d2
Signed-off-by: Finley Xiao <finley.xiao@rock-chips.com>
pmu_io_domains voltage is 1.8V for rk3399-tve1030g board
Change-Id: Iffba406ca1e88f346fc9e436b7b4ea4878b19e92
Signed-off-by: Bin Yang <yangbin@rock-chips.com>
Move rockchip_dmcfreq_vop_bandwidth_request and
rockchip_dmcfreq_vop_bandwidth_update from rockchip_drm_fb.h
to rockchip_dmc.h.
Change-Id: I5b023e44b46a6c613af71452a940d31feb9b2d97
Signed-off-by: Tao Huang <huangtao@rock-chips.com>
remove rockchip_pm_register_notify_to_dmc from rockchip_dmc.h
Change-Id: I9e78eaec2a88cfc06ac3d24f01870cd39c9d05ad
Signed-off-by: Tao Huang <huangtao@rock-chips.com>
The function rk8xx_is_enabled_wmsk_regmap is local to the source
and does not need to be in global scope, so make it static.
drivers/regulator/rk808-regulator.c:714:5: warning: no previous prototype for 'rk8xx_is_enabled_wmsk_regmap' [-Wmissing-prototypes]
Change-Id: Iad140bc1acba548caee1a333a9ed1f846ec06b27
Signed-off-by: Tao Huang <huangtao@rock-chips.com>
The regulator is shared between several devices on some platforms,
if cpu target rate is equal to initial rate, the min_uV and max_uV
of cpu regulator will be always equal to zero, other devices may
set a low voltage which can't meet cpu initial rate.
Change-Id: I97e4815a2422417cd9bd605c93138f5ffda9cc86
Signed-off-by: Finley Xiao <finley.xiao@rock-chips.com>
We need to separate the DAC and ADC configuaration independently.
Change-Id: If8a6673e1489fd34235510d51c8ab34fc91fac01
Signed-off-by: Xing Zheng <zhengxing@rock-chips.com>
fix the main warning:
drivers/video/rockchip/vpu/mpp_dev_h265e.c:501:5: warning: no
previous prototype for ‘rockchip_mpp_h265e_get_stream_header’
[-Wmissing-prototypes]
Change-Id: If6b0a23bb94d1827134270af107f0f8ac1ac30ac
Signed-off-by: Xinhuang Li <buluess.li@rock-chips.com>
Fix the following warning(s):
drivers/rk_nand/rk_nand_base.c:105:15: warning: no previous prototype for ‘rknad_dma_map_single’ [-Wmissing-prototypes]
drivers/rk_nand/rk_nand_base.c:117:6: warning: no previous prototype for ‘rknan_dma_unmap_single’ [-Wmissing-prototypes]
drivers/rk_nand/rk_nand_base.c:128:5: warning: no previous prototype for ‘rknan_flash_cs_init’ [-Wmissing-prototypes]
drivers/rk_nand/rk_nand_base.c:142:5: warning: no previous prototype for ‘rknand_get_boot_media’ [-Wmissing-prototypes
......
Change-Id: Iacd769790f97bb89f44fee7f4d24d315d0179399
Signed-off-by: Yifeng Zhao <zyf@rock-chips.com>
Fix the following warning(s):
drivers/soc/rockchip/rk_vendor_storage.c:15:5: warning: no previous prototype for ‘rk_vendor_read’ [-Wmissing-prototypes]
drivers/soc/rockchip/rk_vendor_storage.c:23:5: warning: no previous prototype for ‘rk_vendor_write’ [-Wmissing-prototypes]
drivers/soc/rockchip/rk_vendor_storage.c:31:5: warning: no previous prototype for ‘rk_vendor_register’ [-Wmissing-prototypes]
drivers/soc/rockchip/rk_vendor_storage.c:42:6: warning: no previous prototype for ‘is_rk_vendor_ready’ [-Wmissing-prototype
Change-Id: Ia264c96adac27ff1e639532b7bdfde464f54e637
Signed-off-by: Yifeng Zhao <zyf@rock-chips.com>
below code would cause endless loop when regulator is set 'always-on':
while (regulator_is_enabled(ldo_18) > 0)
regulator_disable(ldo_18);
Change-Id: Ia3b6f72969ada774a1cf6a46a20ec9b3efb841a0
Signed-off-by: Zhang Yunlong <dalon.zhang@rock-chips.com>
fix the warning:
drivers/video/rockchip/iep/hw_iep_reg.c:1284:6: warning: no
previous prototype for ‘iep_config_misc’ [-Wmissing-prototypes]
Change-Id: I56d0b775cdb62e4566d81b288fe373299b9bbc4c
Signed-off-by: Xinhuang Li <buluess.li@rock-chips.com>
Fix the following warning(s):
drivers/soc/rockchip/rockchip-system-status.c:24:5: warning: no previous prototype for rockchip_register_system_status_notifier [-Wmissing-prototypes]
drivers/soc/rockchip/rockchip-system-status.c:31:5: warning: no previous prototype for rockchip_unregister_system_status_notifier [-Wmissing-prototypes]
drivers/soc/rockchip/rockchip-system-status.c:46:6: warning: no previous prototype for rockchip_set_system_status [-Wmissing-prototypes]
drivers/soc/rockchip/rockchip-system-status.c:70:6: warning: no previous prototype for rockchip_clear_system_status [-Wmissing-prototypes]
drivers/soc/rockchip/rockchip-system-status.c:98:15: warning: no previous prototype for rockchip_get_system_status [-Wmissing-prototypes]
Change-Id: Ic3fb19a4a23f8f6c6833a7ebc573617c372d51bd
Signed-off-by: Tao Huang <huangtao@rock-chips.com>
We need unreigster device when we remove platform or
probe failed.
Change-Id: Ic43a9fcc540b404cee119c17c543d509b121e126
Signed-off-by: Xing Zheng <zhengxing@rock-chips.com>
Usually, the MCLK should be 256 times that of LRCLK,
the excessive mclk (@FS 16KHz and mclk 12.288MHz) may
cause frequency aliasing.
Change-Id: I2665c44dfcdfb51cc4708427782eb68b897c52c4
Signed-off-by: Xing Zheng <zhengxing@rock-chips.com>
drivers/gpu/drm/rockchip/inno_hdmi.c:767:5: warning: no previous
prototype for ‘inno_hdmi_audio_config_set’ [-Wmissing-prototypes]
Change-Id: I08596452ee4c4f63afc644d6808c2bb955f643ea
Signed-off-by: Zheng Yang <zhengyang@rock-chips.com>
Silence the sparse warning
clk/rockchip/clk.c:172:6: warning: symbol 'rockchip_fractional_approximation' was not declared. Should it be static?
Cc: Elaine Zhang <zhangqing@rock-chips.com>
Cc: Heiko Stuebner <heiko@sntech.de>
Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
(cherry picked from commit 1dfcfa721f)
Change-Id: I545f079ff61c6b65363442484cdedd9e01333160
As a second global reset, the GRF is not reset, the iomux and
pull of PWM pin is still keeping, but PWM controller is reset,
PWM pin goes into input mode. However, the pull is still none
changed in kernel, which can cause voltage problems, so should
always keep the PWM pin pull down mode, with 0~50 μA power
increase.
Change-Id: Ibbb9465f7c550d49d416bc3438c5199434df6eba
Signed-off-by: David Wu <david.wu@rock-chips.com>
Allow to use tunable delay before detecting card after card is inserted,
which either comes from firmware node, or comes from debounce value
passed on to mmc_gpiod_request_cd(). If the platform doesn't support
debounce, then we fall back to use the debounce period as the delay,
otherwise, it behaves the same as before that a HW debounce(if set) plus
a 200ms hardcode delay before detecting the card.
Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org>
Change-Id: Ib3ed4cbcdeb0986b584d7dc9057461888e554967
Signed-off-by: Shawn Lin <shawn.lin@rock-chips.com>
(cherry picked from commit 26288b77fd04ea54a84801b1c92c8da519986040
of https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git)
cd-gpios uses a fixed delay, 200ms, before detecting card after the card
is inserted. 200ms doesn't work for some platforms, so some host drivers
added their own properties for parsing that from DT, for instance,
dw_mmc and pxamci. That being said, it should also be tunable when using
cd-gpios.
Reviewed-by: Rob Herring <robh@kernel.org>
Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org>
Change-Id: I925ff27e7dca1289e3fca610ebfe0d4434ceb3de
Signed-off-by: Shawn Lin <shawn.lin@rock-chips.com>
(cherry picked from commit 9bc0607301adeb78884bbdc6e97991f4437fb0fe
of https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git)
Suddenly power loss test for F2FS file system，data will be
lost and the file system count not mount.
bug:
[ 6.372692] F2FS-fs (rknand_userdata): Found nat_bits in checkpoint
[ 6.563942] F2FS-fs (rknand_userdata): Failed to read root inode
[ 6.607687] F2FS-fs (rknand_userdata): Found nat_bits in checkpoint
[ 6.799042] F2FS-fs (rknand_userdata): Failed to read root inode
Change-Id: Ie3256631eba4388cef9edec31aea12bfd45bf4d4
Signed-off-by: Yifeng Zhao <zyf@rock-chips.com>
Each product needs to create a new driver code, even if
they are using the same TP chip. This creates a lot of
code redundant.
Change-Id: I3d7d9982d98deba0ea4067c9adb76fe2a09ab659
Signed-off-by: Bin Yang <yangbin@rock-chips.com>
The serial Flash controller on the rk3036 would request
two clock nodes.
Change-Id: Iaa50c4a25602a68241b0b9b2f186e4c7e55bc3da
Signed-off-by: Randy Li <randy.li@rock-chips.com>
1. rename callbacks to make them more clearly to be understood;
2. add description for intention;
Change-Id: Ic0e28aa98793495c01f531331e9d5dc816ee0820
Signed-off-by: Joseph Chen <chenjh@rock-chips.com>
The save dosc accuracy is not enough to cause the display soc
to be reduced by 1 when system reboot.
Change-Id: Iefd29a0ce16b9975be3d90260d1793ba322db303
Signed-off-by: shengfei Xu <xsf@rock-chips.com>
The cpu will block if the CONFIG_RANDOMIZE_BASE\rockchip-dmc\kpti
are enabled, and the kpti will reduced system performance.
Change-Id: Icd054a4a9cbbea20bd8f8c33a6db64c6fd304fd0
Signed-off-by: Weixin Zhou <zwx@rock-chips.com>
