dv: do not use internal chip_id function by other modules [1/1]

dv: do not use internal chip_id function by other modules [1/1]

PD#SWPL-18367

Problem:
amcsc used the wrong chip_id function from dolby vision driver,
but at the time, the dv driver maybe did not probe. So got the
wrong chip id state.

Solution:
Using the common chip id function.

Verify:
Verifed by u212

Change-Id: If27e861a2c8d8a586448f33cbaa70a81cbe2370f
Signed-off-by: Brian Zhu <brian.zhu@amlogic.com>
(cherry picked from commit e58914e153138fc9655961a6ec67680e12699710)