From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
Stanimir Varbanov <stanimir.k.varbanov@gmail.com>,
Vikash Garodia <quic_vgarodia@quicinc.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: quic_renjiang@quicinc.com, quic_vnagar@quicinc.com,
quic_dikshita@quicinc.com, konradybcio@kernel.org,
linux-media@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org,
Stanimir Varbanov <stanimir.varbanov@linaro.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH 1/3] media: venus: Add support for static video encoder/decoder declarations
Date: Thu, 28 Nov 2024 22:14:16 +0000 [thread overview]
Message-ID: <95ec73c9-da38-4888-9e00-4458b5a7661c@linaro.org> (raw)
In-Reply-To: <7d344377-f1cf-400e-a9c4-442123dcf4ab@oss.qualcomm.com>
On 28/11/2024 20:02, Konrad Dybcio wrote:
> On 27.11.2024 2:34 AM, Bryan O'Donoghue wrote:
>> Add resource structure data and probe() logic to support static
>> declarations of encoder and decoder.
>>
>> Right now we rely on video encoder/decoder selection happening in the dtb
>> but, this goes against the remit of device tree which is supposed to
>> describe hardware, not select functional logic in Linux drivers.
>>
>> Provide two strings in the venus resource structure enc_nodename and
>> dec_nodename.
>>
>> When set the venus driver will create an OF entry in-memory consistent
>> with:
>>
>> dec_nodename {
>> compat = "video-decoder";
>> };
>>
>> and/or
>>
>> enc_nodename {
>> compat = "video-encoder";
>> };
>>
>> This will allow us to reuse the existing driver scheme of relying on compat
>> names maintaining compatibility with old dtb files.
>>
>> dec_nodename can be "video-decoder" or "video0"
>> enc_nodename can be "video-encoder" or "video1"
>>
>> Signed-off-by: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
>> ---
>
> Bryan,
>
> I'm still not sure if keeping the logic behind this makes sense at all.
>
> Could we not just call platform_device_register_data() with a static
> configuration of 1 core being enc and the other dec?
That's another way to do this. One reason I wrote this series to
continue to rely on the existing compat= method though is it stuck in my
mind that we have some dependency ordering logic in at the moment.
For example:
commit 08b1cf474b7f72750adebe0f0a35f8e9a3eb75f6
Author: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
Date: Fri Feb 5 19:11:49 2021 +0100
And the other reason is the prototype platform_device_register_* looks
like more surgery and ultimately more validation / potential for bugs.
Since this driver is supposed to be moving to maintenance mode, I didn't
want to do a more major rewrite of the probe() and remove() paths.
---
bod
next prev parent reply other threads:[~2024-11-28 22:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-27 1:34 [PATCH 0/3] media: venus: Provide support for selecting encoder/decoder from in-driver Bryan O'Donoghue
2024-11-27 1:34 ` [PATCH 1/3] media: venus: Add support for static video encoder/decoder declarations Bryan O'Donoghue
2024-11-27 1:36 ` Bryan O'Donoghue
2024-11-28 20:02 ` Konrad Dybcio
2024-11-28 22:14 ` Bryan O'Donoghue [this message]
2024-11-28 22:34 ` Bryan O'Donoghue
2024-11-29 11:23 ` Konrad Dybcio
2024-11-29 11:41 ` Bryan O'Donoghue
2024-11-27 1:34 ` [PATCH 2/3] media: venus: Populate video encoder/decoder nodename entries Bryan O'Donoghue
2024-11-27 1:34 ` [PATCH 3/3] media: dt-bindings: qcom-venus: Deprecate video-decoder and video-encoder where applicable Bryan O'Donoghue
2024-11-27 9:03 ` Krzysztof Kozlowski
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=95ec73c9-da38-4888-9e00-4458b5a7661c@linaro.org \
--to=bryan.odonoghue@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--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=quic_dikshita@quicinc.com \
--cc=quic_renjiang@quicinc.com \
--cc=quic_vgarodia@quicinc.com \
--cc=quic_vnagar@quicinc.com \
--cc=robh@kernel.org \
--cc=stanimir.k.varbanov@gmail.com \
--cc=stanimir.varbanov@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
all inboxes | Powered by JetHome®