mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <m.chehab@samsung.com>
To: Shuah Khan <shuah.kh@samsung.com>
Cc: ttmesterr@gmail.com, dheitmueller@kernellabs.com,
	cb.xiong@samsung.com, yongjun_wei@trendmicro.com.cn,
	linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] media: fix au0828 dvb suspend/resume to call dvb_frontend_suspend/resume
Date: Tue, 12 Aug 2014 08:36:51 -0300	[thread overview]
Message-ID: <20140812083651.3cfb079d.m.chehab@samsung.com> (raw)
In-Reply-To: <1407813235-30435-1-git-send-email-shuah.kh@samsung.com>

Hi Shuah,

Em Mon, 11 Aug 2014 21:13:55 -0600
Shuah Khan <shuah.kh@samsung.com> escreveu:

> au0828 doesn't resume correctly and TV tuning fails with
> xc_set_signal_source(0) failed message. Change au0828 dvb
> suspend and resume interfaces to suspend and resume frontend
> during suspend and resume respectively. au0828_dvb_suspend()
> calls dvb_frontend_suspend() which in turn invokes tuner ops
> sleep followed by fe ops sleep. au0828_dvb_resume() calls
> dvb_frontend_resume() which in turn calls fe ops ini follwed
> by tuner ops ini before waking up the frontend. With this change
> HVR950Q suspend and resume work when system gets suspended when
> digital function is tuned to a channel and with active TV stream,
> and after resume it went right back to active TV stream.
> 
> Signed-off-by: Shuah Khan <shuah.kh@samsung.com>
> ---
>  drivers/media/usb/au0828/au0828-dvb.c |   37 ++++++++++++++-------------------
>  1 file changed, 16 insertions(+), 21 deletions(-)
> 
> diff --git a/drivers/media/usb/au0828/au0828-dvb.c b/drivers/media/usb/au0828/au0828-dvb.c
> index 821f86e..50e7c82 100644
> --- a/drivers/media/usb/au0828/au0828-dvb.c
> +++ b/drivers/media/usb/au0828/au0828-dvb.c
> @@ -619,35 +619,30 @@ int au0828_dvb_register(struct au0828_dev *dev)
>  
>  void au0828_dvb_suspend(struct au0828_dev *dev)
>  {
> -	struct au0828_dvb *dvb = &dev->dvb;
> -
> -	if (dvb->frontend && dev->urb_streaming) {
> -		pr_info("stopping DVB\n");
> +	struct au0828_dvb *dvb;
> +	int rc;
>  
> -		cancel_work_sync(&dev->restart_streaming);

The restart streaming delayed work still needs to be canceled if
active. This work can be active while DVB is streaming, to workaround
on a chipset bug.

The best is to first call cancel the pending URBs and stop_urb_transfer(),
in order to avoid race conditions.

> +	if (dev == NULL)
> +		return;

In this specific device driver, I think that this condition will never
happen:

	$ git grep "dev = NULL" drivers/media/usb/au0828/au0828*
	drivers/media/usb/au0828/au0828-core.c: dev->usbdev = NULL;

>  
> -		/* Stop transport */
> -		mutex_lock(&dvb->lock);
> -		stop_urb_transfer(dev);

My understanding is that we still need to cancel the pending URBs before
suspending, in order to stop the DMA engine.

> -		au0828_stop_transport(dev, 1);
> -		mutex_unlock(&dvb->lock);
> -		dev->need_urb_start = 1;
> +	dvb = &dev->dvb;
> +	if (dvb->frontend) {
> +		rc = dvb_frontend_suspend(dvb->frontend);
> +		pr_info("au0828_dvb_suspend(): Suspending DVB fe %d\n", rc);
>  	}
>  }
>  
>  void au0828_dvb_resume(struct au0828_dev *dev)
>  {
> -	struct au0828_dvb *dvb = &dev->dvb;
> -
> -	if (dvb->frontend && dev->need_urb_start) {
> -		pr_info("resuming DVB\n");
> +	struct au0828_dvb *dvb;
> +	int rc;
>  
> -		au0828_set_frontend(dvb->frontend);
> +	if (dev == NULL)
> +		return;
>  
> -		/* Start transport */
> -		mutex_lock(&dvb->lock);
> -		au0828_start_transport(dev);
> -		start_urb_transfer(dev);
> -		mutex_unlock(&dvb->lock);

As we need to stop pending URB transfers and stop the DMA engine,
we still need the above code. We don't need to restart a pending
work, because what the pending work would be doing is to stop and
restart the transfer, and the suspend/resume code should do it already.

> +	dvb = &dev->dvb;
> +	if (dvb->frontend) {
> +		rc = dvb_frontend_resume(dvb->frontend);
> +		pr_info("au0828_dvb_resume(): Resuming DVB fe %d\n", rc);
>  	}
>  }

Regards,
Mauro

      reply	other threads:[~2014-08-12 11:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-12  3:13 Shuah Khan
2014-08-12 11:36 ` Mauro Carvalho Chehab [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=20140812083651.3cfb079d.m.chehab@samsung.com \
    --to=m.chehab@samsung.com \
    --cc=cb.xiong@samsung.com \
    --cc=dheitmueller@kernellabs.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=shuah.kh@samsung.com \
    --cc=ttmesterr@gmail.com \
    --cc=yongjun_wei@trendmicro.com.cn \
    /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®