From: Bryan O'Donoghue <bod@kernel.org>
To: Dikshita Agarwal <dikshita.agarwal@oss.qualcomm.com>,
Vikash Garodia <vikash.garodia@oss.qualcomm.com>,
Abhinav Kumar <abhinav.kumar@linux.dev>,
Bryan O'Donoghue <bod@kernel.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Hans Verkuil <hverkuil@kernel.org>,
Stefan Schmidt <stefan.schmidt@linaro.org>
Cc: linux-media@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/6] media: iris: Skip resolution set on first IPSC
Date: Thu, 25 Dec 2025 08:51:29 +0000 [thread overview]
Message-ID: <5bead89d-ede4-489a-b421-d38f1e7c91b7@kernel.org> (raw)
In-Reply-To: <20251224-iris-fixes-v1-2-5f79861700ec@oss.qualcomm.com>
On 24/12/2025 06:27, Dikshita Agarwal wrote:
> The resolution property is not supposed to be set during reconfig.
> Existing iris_drc_pending(inst) check is insufficient, as it doesn't
> cover the first port setting change.
>
> Extend the conditional check to also skip resolution setting when
> the instance is in IRIS_INST_SUB_FIRST_IPSC.
>
> Fixes: caf205548769 ("media: iris: Avoid updating frame size to firmware during reconfig")
> Signed-off-by: Dikshita Agarwal <dikshita.agarwal@oss.qualcomm.com>
> ---
> drivers/media/platform/qcom/iris/iris_hfi_gen1_command.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/media/platform/qcom/iris/iris_hfi_gen1_command.c b/drivers/media/platform/qcom/iris/iris_hfi_gen1_command.c
> index 52da7ef7bab08fb1cb2ac804ccc6e3c7f9677890..5087e51daa842515e9d62730680fb237bf274efa 100644
> --- a/drivers/media/platform/qcom/iris/iris_hfi_gen1_command.c
> +++ b/drivers/media/platform/qcom/iris/iris_hfi_gen1_command.c
> @@ -733,7 +733,7 @@ static int iris_hfi_gen1_set_resolution(struct iris_inst *inst, u32 plane)
> struct hfi_framesize fs;
> int ret;
>
> - if (!iris_drc_pending(inst)) {
> + if (!iris_drc_pending(inst) && !(inst->sub_state & IRIS_INST_SUB_FIRST_IPSC)) {
> fs.buffer_type = HFI_BUFFER_INPUT;
> fs.width = inst->fmt_src->fmt.pix_mp.width;
> fs.height = inst->fmt_src->fmt.pix_mp.height;
>
Take this on trust I guess.
Reviewed-by: Bryan O'Donoghue <bod@kernel.org>
---
bod
next prev parent reply other threads:[~2025-12-25 8:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-24 6:27 [PATCH 0/6] media: iris: misc fixes for fluster, seek and concurrency issues Dikshita Agarwal
2025-12-24 6:27 ` [PATCH 1/6] media: iris: Add buffer to list only after successful allocation Dikshita Agarwal
2025-12-25 8:49 ` Bryan O'Donoghue
2025-12-24 6:27 ` [PATCH 2/6] media: iris: Skip resolution set on first IPSC Dikshita Agarwal
2025-12-25 8:51 ` Bryan O'Donoghue [this message]
2025-12-24 6:27 ` [PATCH 3/6] media: iris: gen1: Destroy internal buffers after FW releases Dikshita Agarwal
2025-12-28 15:51 ` Bryan O'Donoghue
2025-12-24 6:27 ` [PATCH 4/6] Revert "media: iris: Add sanity check for stop streaming" Dikshita Agarwal
2025-12-28 15:53 ` Bryan O'Donoghue
2025-12-24 6:27 ` [PATCH 5/6] media: iris: gen2: Add sanity check for session stop Dikshita Agarwal
2025-12-28 15:55 ` Bryan O'Donoghue
2025-12-24 6:27 ` [PATCH 6/6] media: iris: Prevent output buffer queuing before stream-on completes Dikshita Agarwal
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=5bead89d-ede4-489a-b421-d38f1e7c91b7@kernel.org \
--to=bod@kernel.org \
--cc=abhinav.kumar@linux.dev \
--cc=dikshita.agarwal@oss.qualcomm.com \
--cc=hverkuil@kernel.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=stefan.schmidt@linaro.org \
--cc=vikash.garodia@oss.qualcomm.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