linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Viresh Kumar <viresh.kumar@linaro.org>,
	Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
	Dmitry Osipenko <digetx@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
	Stanimir Varbanov <stanimir.varbanov@linaro.org>,
	Yangtao Li <tiny.windzz@gmail.com>
Subject: linux-next: manual merge of the opp tree with the v4l-dvb tree
Date: Tue, 23 Mar 2021 11:27:05 +1100	[thread overview]
Message-ID: <20210323112705.3094525d@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 2866 bytes --]

Hi all,

Today's linux-next merge of the opp tree got a conflict in:

  drivers/media/platform/qcom/venus/pm_helpers.c

between commit:

  08b1cf474b7f ("media: venus: core, venc, vdec: Fix probe dependency error")

from the v4l-dvb tree and commit:

  857219ae4043 ("media: venus: Convert to use resource-managed OPP API")

from the opp tree.

I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging.  You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.

-- 
Cheers,
Stephen Rothwell

diff --cc drivers/media/platform/qcom/venus/pm_helpers.c
index e349d01422c5,e61317220b9a..000000000000
--- a/drivers/media/platform/qcom/venus/pm_helpers.c
+++ b/drivers/media/platform/qcom/venus/pm_helpers.c
@@@ -750,12 -753,11 +750,11 @@@ static int venc_power_v4(struct device 
  	return ret;
  }
  
 -static int vcodec_domains_get(struct device *dev)
 +static int vcodec_domains_get(struct venus_core *core)
  {
  	int ret;
- 	struct opp_table *opp_table;
  	struct device **opp_virt_dev;
 -	struct venus_core *core = dev_get_drvdata(dev);
 +	struct device *dev = core->dev;
  	const struct venus_resources *res = core->res;
  	struct device *pd;
  	unsigned int i;
@@@ -826,13 -825,11 +821,11 @@@ skip_pmdomains
  
  	if (core->opp_dl_venus)
  		device_link_del(core->opp_dl_venus);
- 
- 	dev_pm_opp_detach_genpd(core->opp_table);
  }
  
 -static int core_get_v4(struct device *dev)
 +static int core_get_v4(struct venus_core *core)
  {
 -	struct venus_core *core = dev_get_drvdata(dev);
 +	struct device *dev = core->dev;
  	const struct venus_resources *res = core->res;
  	int ret;
  
@@@ -871,35 -867,24 +863,24 @@@
  		}
  	}
  
 -	ret = vcodec_domains_get(dev);
 +	ret = vcodec_domains_get(core);
- 	if (ret) {
- 		if (core->has_opp_table)
- 			dev_pm_opp_of_remove_table(dev);
- 		dev_pm_opp_put_clkname(core->opp_table);
+ 	if (ret)
  		return ret;
- 	}
  
  	return 0;
  }
  
 -static void core_put_v4(struct device *dev)
 +static void core_put_v4(struct venus_core *core)
  {
- 	struct device *dev = core->dev;
- 
  	if (legacy_binding)
  		return;
  
 -	vcodec_domains_put(dev);
 +	vcodec_domains_put(core);
- 
- 	if (core->has_opp_table)
- 		dev_pm_opp_of_remove_table(dev);
- 	dev_pm_opp_put_clkname(core->opp_table);
- 
  }
  
 -static int core_power_v4(struct device *dev, int on)
 +static int core_power_v4(struct venus_core *core, int on)
  {
 -	struct venus_core *core = dev_get_drvdata(dev);
 +	struct device *dev = core->dev;
  	struct device *pmctrl = core->pmdomains[0];
  	int ret = 0;
  

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2021-03-23  0:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-23  0:27 Stephen Rothwell [this message]
2021-03-24 14:49 ` linux-next: manual merge of the opp tree with the v4l-dvb tree Stanimir Varbanov
2021-03-25  4:25   ` Viresh Kumar
2021-03-25  8:14     ` Stanimir Varbanov
2021-03-25  9:10       ` Viresh Kumar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210323112705.3094525d@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=bryan.odonoghue@linaro.org \
    --cc=digetx@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mchehab+huawei@kernel.org \
    --cc=mchehab@kernel.org \
    --cc=stanimir.varbanov@linaro.org \
    --cc=tiny.windzz@gmail.com \
    --cc=viresh.kumar@linaro.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).