From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Wenmeng Liu <wenmeng.liu@oss.qualcomm.com>,
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>
Cc: linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v4 3/3] media: qcom: camss: tpg: Add TPG support for SA8775P and QCS8300
Date: Wed, 8 Oct 2025 12:50:57 +0200 [thread overview]
Message-ID: <eb90f34c-4b63-4696-abf5-1d412d7bf263@oss.qualcomm.com> (raw)
In-Reply-To: <20250925-camss_tpg-v4-3-d2eb099902c8@oss.qualcomm.com>
On 9/25/25 2:32 AM, Wenmeng Liu wrote:
> Add support for TPG found on SA8775P and QCS8300.
>
> Signed-off-by: Wenmeng Liu <wenmeng.liu@oss.qualcomm.com>
> ---
[...]
> @@ -4350,6 +4413,7 @@ static const struct camss_resources msm8916_resources = {
> .ispif_res = &ispif_res_8x16,
> .vfe_res = vfe_res_8x16,
> .csiphy_num = ARRAY_SIZE(csiphy_res_8x16),
> + .tpg_num = 0,
Uninitialized fields of partially-initialized structs default to zero,
i.e. drop all lines like this
Konrad
next prev parent reply other threads:[~2025-10-08 10:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-25 0:31 [PATCH v4 0/3] media: qcom: camss: Add sa8775p/qcs8300 camss TPG support Wenmeng Liu
2025-09-25 0:31 ` [PATCH v4 1/3] media: qcom: camss: Add support for TPG common Wenmeng Liu
2025-10-07 10:44 ` Konrad Dybcio
2025-10-16 12:55 ` Wenmeng Liu
2025-09-25 0:32 ` [PATCH v4 2/3] media: qcom: camss: Add link " Wenmeng Liu
2025-09-25 0:32 ` [PATCH v4 3/3] media: qcom: camss: tpg: Add TPG support for SA8775P and QCS8300 Wenmeng Liu
2025-09-26 6:08 ` kernel test robot
2025-10-08 10:50 ` Konrad Dybcio [this message]
2025-10-16 12:56 ` Wenmeng Liu
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=eb90f34c-4b63-4696-abf5-1d412d7bf263@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=bryan.odonoghue@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=todor.too@gmail.com \
--cc=vladimir.zapolskiy@linaro.org \
--cc=wenmeng.liu@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