From: Sylwester Nawrocki <s.nawrocki@samsung.com>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
Sachin Kamat <sachin.kamat@linaro.org>,
Kamil Debski <k.debski@samsung.com>
Subject: Re: Fw: [PATCH] [media] s5p-mfc: Remove unreachable code
Date: Tue, 25 Sep 2012 16:07:04 +0200 [thread overview]
Message-ID: <5061BA88.8010201@samsung.com> (raw)
In-Reply-To: <20120925102839.2a90ab26@redhat.com>
Hi Mauro, Sachin,
On 09/25/2012 03:28 PM, Mauro Carvalho Chehab wrote:
> Hi Sylwester,
>
> Please review.
I checked it with Kamil and it seems the code being removed
is required for proper driver operation. Thus please hold on
with this patch. We will prepare a different fix after testing.
Sachin, thanks for reporting that issue. The code below is needed
to make sure the MFC is fully suspended after s5p_mfc_suspend()
returns. The "return s5p_mfc_sleep(m_dev);" probably just needs
to be moved after the while loop.
> Thanks!
> Mauro
>
> Forwarded message:
>
> Date: Fri, 14 Sep 2012 14:50:17 +0530
> From: Sachin Kamat <sachin.kamat@linaro.org>
> To: linux-media@vger.kernel.org
> Cc: mchehab@infradead.org, s.nawrocki@samsung.com, k.debski@samsung.com, sachin.kamat@linaro.org, patches@linaro.org
> Subject: [PATCH] [media] s5p-mfc: Remove unreachable code
>
>
> Code after return statement never gets executed.
> Hence can be deleted.
>
> Signed-off-by: Sachin Kamat <sachin.kamat@linaro.org>
> ---
> drivers/media/platform/s5p-mfc/s5p_mfc.c | 21 +--------------------
> 1 files changed, 1 insertions(+), 20 deletions(-)
>
> diff --git a/drivers/media/platform/s5p-mfc/s5p_mfc.c b/drivers/media/platform/s5p-mfc/s5p_mfc.c
> index e3e616d..56876be 100644
> --- a/drivers/media/platform/s5p-mfc/s5p_mfc.c
> +++ b/drivers/media/platform/s5p-mfc/s5p_mfc.c
> @@ -1144,30 +1144,11 @@ static int s5p_mfc_suspend(struct device *dev)
> {
> struct platform_device *pdev = to_platform_device(dev);
> struct s5p_mfc_dev *m_dev = platform_get_drvdata(pdev);
> - int ret;
>
> if (m_dev->num_inst == 0)
> return 0;
> - return s5p_mfc_sleep(m_dev);
> - if (test_and_set_bit(0, &m_dev->enter_suspend) != 0) {
> - mfc_err("Error: going to suspend for a second time\n");
> - return -EIO;
> - }
>
> - /* Check if we're processing then wait if it necessary. */
> - while (test_and_set_bit(0, &m_dev->hw_lock) != 0) {
> - /* Try and lock the HW */
> - /* Wait on the interrupt waitqueue */
> - ret = wait_event_interruptible_timeout(m_dev->queue,
> - m_dev->int_cond || m_dev->ctx[m_dev->curr_ctx]->int_cond,
> - msecs_to_jiffies(MFC_INT_TIMEOUT));
> -
> - if (ret == 0) {
> - mfc_err("Waiting for hardware to finish timed out\n");
> - return -EIO;
> - }
> - }
> - return 0;
> + return s5p_mfc_sleep(m_dev);
> }
>
> static int s5p_mfc_resume(struct device *dev)
--
Thanks,
Sylwester
next prev parent reply other threads:[~2012-09-25 14:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-25 13:28 Fw: [PATCH] [media] s5p-mfc: Remove unreachable code Mauro Carvalho Chehab
2012-09-25 14:07 ` Sylwester Nawrocki [this message]
2012-09-25 15:25 ` Sachin Kamat
2012-09-25 15:55 ` Sylwester Nawrocki
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=5061BA88.8010201@samsung.com \
--to=s.nawrocki@samsung.com \
--cc=k.debski@samsung.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=sachin.kamat@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).