[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d45ae8a5-6890-4263-8aea-62575f71b3f2@oss.qualcomm.com>
Date: Wed, 14 Jan 2026 10:43:31 +0100
From: Konrad Dybcio <konrad.dybcio@....qualcomm.com>
To: Vladimir Zapolskiy <vladimir.zapolskiy@...aro.org>,
Wenmeng Liu <wenmeng.liu@....qualcomm.com>,
Robert Foss <rfoss@...nel.org>, Todor Tomov <todor.too@...il.com>,
Bryan O'Donoghue <bryan.odonoghue@...aro.org>,
Mauro Carvalho Chehab <mchehab@...nel.org>
Cc: linux-kernel@...r.kernel.org, linux-media@...r.kernel.org,
linux-arm-msm@...r.kernel.org
Subject: Re: [PATCH v8 1/3] media: qcom: camss: Add common TPG support
On 1/14/26 6:05 AM, Vladimir Zapolskiy wrote:
> Hi Wenmeng.
>
> On 1/14/26 05:04, Wenmeng Liu wrote:
>> Hi Vladimir,
[...]
>>>> +const char * const testgen_payload_modes[] = {
>>>> + "Disabled",
>>>> + "Incrementing",
>>>> + "Alternating 0x55/0xAA",
>>>> + "Reserved",
>>>> + "Reserved",
>>>> + "Pseudo-random Data",
>>>> + "User Specified",
>>>> + "Reserved",
>>>> + "Reserved",
>>>> + "Color bars",
>>>> + "Reserved"
>>>
>>> It makes little sense to mention the unsupported values, and then
>>> introduce enum tpg_testgen_mode to list the supported ones.
>>>
>> This is for ctrl menu, will do as follow:
>> static const char * const testgen_payload_modes[] = {
>> [TPG_PAYLOAD_MODE_DISABLED] = "Disabled",
>> [TPG_PAYLOAD_MODE_INCREMENTING] = "Incrementing",
>> [TPG_PAYLOAD_MODE_ALTERNATING_55_AA] = "Alternating 0x55/0xAA",
>> [TPG_PAYLOAD_MODE_RANDOM] = "Pseudo-random Data",
>> [TPG_PAYLOAD_MODE_USER_SPECIFIED] = "User Specified",
>> [TPG_PAYLOAD_MODE_COLOR_BARS] = "Color bars",
>> };
>>
>
> This is also not perfect, still userspace is misinformed about a number
> of possible TPG modes vs. a number of actually supported TPG modes.
If the values are really reserved (i.e. don't do anything (useful) today),
let's just throw an -EOPNOTSUPP if selected
Konrad
Powered by blists - more mailing lists