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 <dkatraga@codeaurora.org>
This commit is contained in:
parent
c2fd04161e
commit
ad09c8ea85
1 changed files with 2 additions and 2 deletions
|
@ -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);
|
||||
|
|
Loading…
Add table
Reference in a new issue