From: xiaolei wang <xiaolei.wang@windriver.com>
To: Philipp Zabel <p.zabel@pengutronix.de>, mchehab@kernel.org
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] media: coda: Add system resume interface
Date: Thu, 13 Feb 2025 10:17:17 +0800 [thread overview]
Message-ID: <0a2719ce-3866-474f-8c84-fa1fff2a0fca@windriver.com> (raw)
In-Reply-To: <e2cd8a249820913562350c786116d91d447f437a.camel@pengutronix.de>
On 1/6/25 16:15, Philipp Zabel wrote:
> CAUTION: This email comes from a non Wind River email account!
> Do not click links or open attachments unless you recognize the sender and know the content is safe.
>
> On Sa, 2024-12-21 at 11:14 +0800, Xiaolei Wang wrote:
>> When the system goes into sleep mode, the dependent
>> power will be turned off, so when the system resumes,
>> coda_hw_init() needs to be called, otherwise it will
>> get 'CODA PIC_RUN timeout' after resuming.
>>
>> Signed-off-by: Xiaolei Wang <xiaolei.wang@windriver.com>
>> ---
>> drivers/media/platform/chips-media/coda/coda-common.c | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/drivers/media/platform/chips-media/coda/coda-common.c b/drivers/media/platform/chips-media/coda/coda-common.c
>> index 289a076c3bcc..e6e3f5ec24f6 100644
>> --- a/drivers/media/platform/chips-media/coda/coda-common.c
>> +++ b/drivers/media/platform/chips-media/coda/coda-common.c
>> @@ -3340,6 +3340,7 @@ static int coda_runtime_resume(struct device *dev)
>>
>> static const struct dev_pm_ops coda_pm_ops = {
>> SET_RUNTIME_PM_OPS(NULL, coda_runtime_resume, NULL)
>> + SET_SYSTEM_SLEEP_PM_OPS(pm_runtime_force_suspend, pm_runtime_force_resume)
>> };
>>
>> static struct platform_driver coda_driver = {
> Reviewed-by: Philipp Zabel <p.zabel@pengutronix.de>
Humble Ping...
thanks
xiaolei
>
> regards
> Philipp
prev parent reply other threads:[~2025-02-13 2:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-21 3:14 Xiaolei Wang
2025-01-06 8:15 ` Philipp Zabel
2025-02-13 2:17 ` xiaolei wang [this message]
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=0a2719ce-3866-474f-8c84-fa1fff2a0fca@windriver.com \
--to=xiaolei.wang@windriver.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=p.zabel@pengutronix.de \
/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
all inboxes | Powered by JetHome®