From ad09c8ea858308a912b64a6b618e634c56436131 Mon Sep 17 00:00:00 2001 From: Deepak Katragadda Date: Mon, 3 Oct 2016 15:08:06 -0700 Subject: [PATCH] clk: msm: clock-osm: Fix for programming the APM threshold on MSMCOBALT The clock driver does not currently use the secure API to write the APM threshold value. This leads to the value being always left as 0. Fix the write. CRs-Fixed: 1074198 Change-Id: I61d8f930f7fe8c3539803a1e9b942095df0b0f86 Signed-off-by: Deepak Katragadda --- drivers/clk/msm/clock-osm.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/clk/msm/clock-osm.c b/drivers/clk/msm/clock-osm.c index c5ec2ed7318d..0d733f49f184 100644 --- a/drivers/clk/msm/clock-osm.c +++ b/drivers/clk/msm/clock-osm.c @@ -1882,8 +1882,8 @@ static void clk_osm_apm_vc_setup(struct clk_osm *c) } scm_io_write(c->pbases[OSM_BASE] + SEQ_REG(72), c->apm_crossover_vc); - clk_osm_write_reg(c, c->apm_threshold_vc, - SEQ_REG(15)); + scm_io_write(c->pbases[OSM_BASE] + SEQ_REG(15), + c->apm_threshold_vc); scm_io_write(c->pbases[OSM_BASE] + SEQ_REG(31), c->apm_threshold_vc != 0 ? c->apm_threshold_vc - 1 : 0xff);