Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1725404

[PATCH] CHROMIUM: devfreq: rk3399: Clear edev->dev drvdata before enabling dfi

From Jeffy Chen <jeffy.chen@rock-chips.com>
Newsgroups linux.kernel
Subject [PATCH] CHROMIUM: devfreq: rk3399: Clear edev->dev drvdata before enabling dfi
Date 2017-09-02 02:00 +0200
Message-ID <ul40W-3Dx-9@gated-at.bofh.it> (permalink)
Organization linux.* mail to news gateway

Show all headers | View raw


Currently we are using edev->dev drvdata to get rk3399-dmc data, but
it would be inited to edev in devfreq_event_add_edev.

So we need to clear the edev->dev drvdata before enabling dfi, to
prevent dfi from getting the wrong rk3399-dmc data when the irq
triggered too early.

Signed-off-by: Jeffy Chen <jeffy.chen@rock-chips.com>
---

 drivers/devfreq/rk3399_dmc.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/devfreq/rk3399_dmc.c b/drivers/devfreq/rk3399_dmc.c
index 1b89ebbad02c..12f9f03f349f 100644
--- a/drivers/devfreq/rk3399_dmc.c
+++ b/drivers/devfreq/rk3399_dmc.c
@@ -429,6 +429,7 @@ static int rk3399_dmcfreq_probe(struct platform_device *pdev)
 
 	rk3399_devfreq_dmc_profile.initial_freq = data->rate;
 
+	platform_set_drvdata(pdev, NULL);
 	data->devfreq = devm_devfreq_add_device(dev,
 					   &rk3399_devfreq_dmc_profile,
 					   "simple_ondemand",
-- 
2.11.0

Back to linux.kernel | Previous | NextNext in thread | Find similar | Unroll thread


Thread

[PATCH] CHROMIUM: devfreq: rk3399: Clear edev->dev drvdata before enabling dfi Jeffy Chen <jeffy.chen@rock-chips.com> - 2017-09-02 02:00 +0200
  Re: [PATCH] CHROMIUM: devfreq: rk3399: Clear edev->dev drvdata  before enabling dfi Brian Norris <briannorris@chromium.org> - 2017-09-02 02:50 +0200
    Re: [PATCH] CHROMIUM: devfreq: rk3399: Clear edev->dev drvdata before  enabling dfi jeffy <jeffy.chen@rock-chips.com> - 2017-09-02 04:00 +0200

csiph-web