From: Wenmeng Liu <wenmeng.liu@oss.qualcomm.com>
To: Loic Poulain <loic.poulain@oss.qualcomm.com>
Cc: Robert Foss <rfoss@kernel.org>, Todor Tomov <todor.too@gmail.com>,
Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Hans Verkuil <hverkuil@kernel.org>,
Gjorgji Rosikopulos <quic_grosikop@quicinc.com>,
Radoslav Tsvetkov <quic_rtsvetko@quicinc.com>,
linux-media@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] media: qcom: camss: vfe: fix PIX subdev naming on VFE lite
Date: Tue, 24 Mar 2026 21:10:01 +0800 [thread overview]
Message-ID: <93624dae-71c0-45ac-9aca-7175d8771a32@oss.qualcomm.com> (raw)
In-Reply-To: <CAFEp6-39tUEBqX_FWLdohE2jenoj1ot18Gnhi4Aop9hukGoGQw@mail.gmail.com>
On 3/23/2026 5:55 PM, Loic Poulain wrote:
> On Mon, Mar 23, 2026 at 3:13 AM Wenmeng Liu
> <wenmeng.liu@oss.qualcomm.com> wrote:
>>
>>
>>
>> On 3/19/2026 10:44 PM, Loic Poulain wrote:
>>> On Thu, Mar 19, 2026 at 10:11 AM Wenmeng Liu
>>> <wenmeng.liu@oss.qualcomm.com> wrote:
>>>>
>>>> VFE lite hardware does not provide a functional PIX path, but after
>>>> the per sub-device type resource changes the PIX subdev name is still
>>>> assigned unconditionally.
>>>>
>>>> Only assign the PIX subdev name on non-lite VFE variants to avoid
>>>> exposing a misleading device name.
>>>>
>>>> Fixes: ae44829a4a97 ("media: qcom: camss: Add per sub-device type resources")
>>>> Signed-off-by: Wenmeng Liu <wenmeng.liu@oss.qualcomm.com>
>>>> ---
>>>> drivers/media/platform/qcom/camss/camss-vfe.c | 2 +-
>>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>>
>>>> diff --git a/drivers/media/platform/qcom/camss/camss-vfe.c b/drivers/media/platform/qcom/camss/camss-vfe.c
>>>> index 5baf0e3d4bc461df28d8dcf97a98dec04fa17ceb..2ee4f9ae0ab50e22f916736f1d1664767bdb6a36 100644
>>>> --- a/drivers/media/platform/qcom/camss/camss-vfe.c
>>>> +++ b/drivers/media/platform/qcom/camss/camss-vfe.c
>>>> @@ -2053,7 +2053,7 @@ int msm_vfe_register_entities(struct vfe_device *vfe,
>>>> v4l2_subdev_init(sd, &vfe_v4l2_ops);
>>>> sd->internal_ops = &vfe_v4l2_internal_ops;
>>>> sd->flags |= V4L2_SUBDEV_FL_HAS_DEVNODE;
>>>> - if (i == VFE_LINE_PIX)
>>>> + if (i == VFE_LINE_PIX && vfe->res->is_lite == false)
>>>> snprintf(sd->name, ARRAY_SIZE(sd->name), "%s%d_%s",
>>>> MSM_VFE_NAME, vfe->id, "pix");
>>>
>>> So the PIX path will be called RDI? Doesn’t that seem misleading as well?
>> when i == VFE_LINE_PIX and vfe->res->is_lite == false then vfe name is
>> pix, not rdi.
>
> I mean when is_lite==true, we're going to name the PIX(lite) path RDI,
> whereas it's not a raw dump interface, I guess pix-lite includes minimal
> processing engine.
For VFE Lite, only RDI paths are supported. There is no PIX output.
Thanks,
Wenmeng
next prev parent reply other threads:[~2026-03-24 13:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-19 9:09 [PATCH] media: qcom: camss: vfe: fix PIX subdev naming on VFE lite Wenmeng Liu
2026-03-19 10:13 ` Bryan O'Donoghue
2026-03-19 14:44 ` Loic Poulain
2026-03-23 2:13 ` Wenmeng Liu
2026-03-23 9:55 ` Loic Poulain
2026-03-24 13:10 ` Wenmeng Liu [this message]
2026-03-24 14:09 ` Loic Poulain
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=93624dae-71c0-45ac-9aca-7175d8771a32@oss.qualcomm.com \
--to=wenmeng.liu@oss.qualcomm.com \
--cc=bryan.odonoghue@linaro.org \
--cc=hverkuil@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=loic.poulain@oss.qualcomm.com \
--cc=mchehab@kernel.org \
--cc=quic_grosikop@quicinc.com \
--cc=quic_rtsvetko@quicinc.com \
--cc=rfoss@kernel.org \
--cc=todor.too@gmail.com \
--cc=vladimir.zapolskiy@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