From: Vikash Garodia <vikash.garodia@oss.qualcomm.com>
To: Nicolas Dufresne <nicolas@ndufresne.ca>,
Dikshita Agarwal <dikshita.agarwal@oss.qualcomm.com>,
Abhinav Kumar <abhinav.kumar@linux.dev>,
Bryan O'Donoghue <bod@kernel.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Cc: linux-arm-msm@vger.kernel.org, linux-media@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Vishnu Reddy <quic_bvisredd@quicinc.com>,
Bryan O'Donoghue <bryan.odonoghue@linaro.org>
Subject: Re: [PATCH v2 0/8] media: iris: add support for video codecs on Qcom kaanapali platform
Date: Wed, 22 Oct 2025 11:37:51 +0530 [thread overview]
Message-ID: <c3a468be-39b0-5c3d-e4d8-9e45f3f6ae22@oss.qualcomm.com> (raw)
In-Reply-To: <579c8667827cb1ac5778b48077f4f84e875b69da.camel@ndufresne.ca>
Hello Nicolas,
On 10/17/2025 8:06 PM, Nicolas Dufresne wrote:
> Hi Vikash,
>
> Le vendredi 17 octobre 2025 à 19:46 +0530, Vikash Garodia a
>> [ 350.438406] qcom-iris 2000000.video-codec: invalid plane
>> [ 350.447079] qcom-iris 2000000.video-codec: invalid plane
>> [ 350.458821] qcom-iris 2000000.video-codec: invalid plane
>> [ 350.465860] qcom-iris 2000000.video-codec: invalid plane
>
> Just a highlight, the driver should only print stuff on default log level if
> something is malfunctioning. uAPI miss-use should only be trace on loglevel
> manually enabled by the developers. Mind fixing this up while at it ? Hopefully
> this will be obvious to you next time you encounter it.
Agree, this specific log should not be part of default execution and more so
when this is not malfunctioning. I would remove this log as i see it can be dropped.
Regards,
Vikash
next prev parent reply other threads:[~2025-10-22 6:07 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-17 14:16 [PATCH v2 0/8] media: iris: add support for video codecs on Qcom kaanapali platform Vikash Garodia
2025-10-17 14:16 ` [PATCH v2 1/8] media: dt-bindings: qcom-kaanapali-iris: Add kaanapali video codec binding Vikash Garodia
2025-10-18 15:58 ` Krzysztof Kozlowski
2025-10-21 18:55 ` Vikash Garodia
2025-10-21 19:15 ` Krzysztof Kozlowski
2025-10-21 21:07 ` Vikash Garodia
2025-10-22 6:04 ` Krzysztof Kozlowski
2025-10-22 9:37 ` Dmitry Baryshkov
2025-10-22 14:51 ` Bryan O'Donoghue
2025-10-22 15:36 ` Konrad Dybcio
2025-10-22 16:28 ` Krzysztof Kozlowski
2025-11-06 14:50 ` Vikash Garodia
2025-10-17 14:16 ` [PATCH v2 2/8] media: iris: Add support for multiple clock sources Vikash Garodia
2025-10-21 23:06 ` Bryan O'Donoghue
2025-10-17 14:16 ` [PATCH v2 3/8] media: iris: Add support for multiple TZ content protection(CP) configs Vikash Garodia
2025-10-21 23:35 ` Bryan O'Donoghue
2025-10-17 14:16 ` [PATCH v2 4/8] media: iris: Introduce buffer size calculations for vpu4 Vikash Garodia
2025-10-21 23:25 ` Bryan O'Donoghue
2025-10-22 5:44 ` Vikash Garodia
2025-10-17 14:16 ` [PATCH v2 5/8] media: iris: Move vpu register defines to common header file Vikash Garodia
2025-10-21 23:27 ` Bryan O'Donoghue
2025-10-17 14:16 ` [PATCH v2 6/8] media: iris: Move vpu35 specific api to common to use for vpu4 Vikash Garodia
2025-10-21 23:29 ` Bryan O'Donoghue
2025-10-17 14:16 ` [PATCH v2 7/8] media: iris: Introduce vpu ops for vpu4 with necessary hooks Vikash Garodia
2025-10-17 14:16 ` [PATCH v2 8/8] media: iris: Add platform data for kaanapali Vikash Garodia
2025-10-21 23:39 ` Bryan O'Donoghue
2025-10-22 5:46 ` Vikash Garodia
2025-10-22 15:20 ` Bryan O'Donoghue
2025-10-17 14:36 ` [PATCH v2 0/8] media: iris: add support for video codecs on Qcom kaanapali platform Nicolas Dufresne
2025-10-22 6:07 ` Vikash Garodia [this message]
2025-11-10 7:45 ` Vikash Garodia
2025-10-22 17:26 ` Konrad Dybcio
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=c3a468be-39b0-5c3d-e4d8-9e45f3f6ae22@oss.qualcomm.com \
--to=vikash.garodia@oss.qualcomm.com \
--cc=abhinav.kumar@linux.dev \
--cc=bod@kernel.org \
--cc=bryan.odonoghue@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dikshita.agarwal@oss.qualcomm.com \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=krzk+dt@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=nicolas@ndufresne.ca \
--cc=p.zabel@pengutronix.de \
--cc=quic_bvisredd@quicinc.com \
--cc=robh@kernel.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