From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
Cc: rfoss@kernel.org, todor.too@gmail.com, agross@kernel.org,
andersson@kernel.org, konrad.dybcio@linaro.org,
mchehab@kernel.org, hverkuil-cisco@xs4all.nl,
sakari.ailus@linux.intel.com, andrey.konovalov@linaro.org,
linux-media@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v2 4/9] media: qcom: camss: Fix VFE-17x vfe_disable_output()
Date: Mon, 28 Aug 2023 20:15:41 +0300 [thread overview]
Message-ID: <20230828171541.GY14596@pendragon.ideasonboard.com> (raw)
In-Reply-To: <20230822200626.1931129-5-bryan.odonoghue@linaro.org>
Hi Bryan,
Thank you for the patch.
On Tue, Aug 22, 2023 at 09:06:21PM +0100, Bryan O'Donoghue wrote:
> There are two problems with the current vfe_disable_output() routine.
>
> Firstly we rightly use a spinlock to protect output->gen2.active_num
> everywhere except for in the IDLE timeout path of vfe_disable_output().
> Even if that is not racy "in practice" somehow it is by happenstance not
> by design.
>
> Secondly we do not get consistent behaviour from this routine. On
> sc8280xp 50% of the time I get "VFE idle timeout - resetting". In this
> case the subsequent capture will succeed. The other 50% of the time, we
> don't hit the idle timeout, never do the VFE reset and subsequent
> captures stall indefinitely.
>
> Rewrite the vfe_disable_output() routine to
>
> - Quiesce write masters with vfe_wm_stop()
> - Set active_num = 0
>
> remembering to hold the spinlock when we do so followed by
>
> - Reset the VFE
>
> Testing on sc8280xp and sdm845 shows this to be a valid fix.
>
> Fixes: 7319cdf189bb ("media: camss: Add support for VFE hardware version Titan 170")
> Cc: stable@vger.kernel.org
> Signed-off-by: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
I can't comment on the validity of the fix, but nothing shocks me in the
patch, so I'm fine with it.
> ---
> .../media/platform/qcom/camss/camss-vfe-170.c | 19 +++----------------
> 1 file changed, 3 insertions(+), 16 deletions(-)
>
> diff --git a/drivers/media/platform/qcom/camss/camss-vfe-170.c b/drivers/media/platform/qcom/camss/camss-vfe-170.c
> index 02494c89da91c..ae9137633c301 100644
> --- a/drivers/media/platform/qcom/camss/camss-vfe-170.c
> +++ b/drivers/media/platform/qcom/camss/camss-vfe-170.c
> @@ -500,28 +500,15 @@ static int vfe_disable_output(struct vfe_line *line)
> struct vfe_output *output = &line->output;
> unsigned long flags;
> unsigned int i;
> - bool done;
> - int timeout = 0;
> -
> - do {
> - spin_lock_irqsave(&vfe->output_lock, flags);
> - done = !output->gen2.active_num;
> - spin_unlock_irqrestore(&vfe->output_lock, flags);
> - usleep_range(10000, 20000);
Now that you don't sleep anymore, I think you can drop the inclusion of
linux/delay.h.
> -
> - if (timeout++ == 100) {
> - dev_err(vfe->camss->dev, "VFE idle timeout - resetting\n");
> - vfe_reset(vfe);
> - output->gen2.active_num = 0;
> - return 0;
> - }
> - } while (!done);
>
> spin_lock_irqsave(&vfe->output_lock, flags);
> for (i = 0; i < output->wm_num; i++)
> vfe_wm_stop(vfe, output->wm_idx[i]);
> + output->gen2.active_num = 0;
> spin_unlock_irqrestore(&vfe->output_lock, flags);
>
> + vfe_reset(vfe);
> +
> return 0;
This function could become void, especially given that its only caller
doesn't check the return value.
> }
>
> --
> 2.41.0
>
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2023-08-28 17:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 20:06 [PATCH v2 0/9] media: qcom: camss: Bugfix series Bryan O'Donoghue
2023-08-22 20:06 ` [PATCH v2 1/9] media: qcom: camss: Fix pm_domain_on sequence in probe Bryan O'Donoghue
2023-08-28 17:00 ` Laurent Pinchart
2023-08-22 20:06 ` [PATCH v2 2/9] media: qcom: camss: Fix V4L2 async notifier error path Bryan O'Donoghue
2023-08-28 17:05 ` Laurent Pinchart
2023-08-29 10:17 ` Bryan O'Donoghue
2023-08-22 20:06 ` [PATCH v2 3/9] media: qcom: camss: Fix vfe_get() error jump Bryan O'Donoghue
2023-08-28 17:10 ` Laurent Pinchart
2023-08-22 20:06 ` [PATCH v2 4/9] media: qcom: camss: Fix VFE-17x vfe_disable_output() Bryan O'Donoghue
2023-08-28 17:15 ` Laurent Pinchart [this message]
2023-08-22 20:06 ` [PATCH v2 5/9] media: qcom: camss: Fix VFE-480 vfe_disable_output() Bryan O'Donoghue
2023-08-28 17:17 ` Laurent Pinchart
2023-08-29 16:13 ` Bryan O'Donoghue
2023-08-22 20:06 ` [PATCH v2 6/9] media: qcom: camss: Fix missing vfe_lite clocks check Bryan O'Donoghue
2023-08-28 17:18 ` Laurent Pinchart
2023-08-22 20:06 ` [PATCH v2 7/9] media: qcom: camss: Fix invalid clock enable bit disjunction Bryan O'Donoghue
2023-08-28 17:19 ` Laurent Pinchart
2023-08-22 20:06 ` [PATCH v2 8/9] media: qcom: camss: Fix set CSI2_RX_CFG1_VC_MODE when VC is greater than 3 Bryan O'Donoghue
2023-08-28 17:22 ` Laurent Pinchart
2023-08-22 20:06 ` [PATCH v2 9/9] media: qcom: camss: Fix csid-gen2 for test pattern generator Bryan O'Donoghue
2023-08-28 17:27 ` Laurent Pinchart
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=20230828171541.GY14596@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=andrey.konovalov@linaro.org \
--cc=bryan.odonoghue@linaro.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=konrad.dybcio@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=rfoss@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=stable@vger.kernel.org \
--cc=todor.too@gmail.com \
/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