From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Jorge Ramirez-Ortiz <jorge.ramirez@oss.qualcomm.com>,
vikash.garodia@oss.qualcomm.com,
dikshita.agarwal@oss.qualcomm.com, bod@kernel.org,
mchehab@kernel.org
Cc: linux-media@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] media: venus: assign unique bus_info strings for encoder and decoder
Date: Fri, 21 Nov 2025 20:22:13 +0100 [thread overview]
Message-ID: <249ccbbc-7990-43f0-b205-d5f33a1c9ad3@oss.qualcomm.com> (raw)
In-Reply-To: <20251121184306.218169-1-jorge.ramirez@oss.qualcomm.com>
On 11/21/25 7:43 PM, Jorge Ramirez-Ortiz wrote:
> The Venus encoder and decoder video devices currently report the same
> bus_info string ("platform:qcom-venus").
>
> Assign unique bus_info identifiers by appending ":dec" and ":enc" to the
> parent device name. With this change v4l2-ctl will display two separate
> logical devices
>
> Signed-off-by: Jorge Ramirez-Ortiz <jorge.ramirez@oss.qualcomm.com>
> ---
Perhaps that's a stupid question, but is there a reason they're
separate at all?
Konrad
next prev parent reply other threads:[~2025-11-21 19:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3FJhEomSdQ2CUrDJZaWiNVmSKYmUGylmoUUZc_15p0xnLmG_gydDxIyJDrUnemnatDXNOtQAqbWytjZ-xZAJ_w==@protonmail.internalid>
2025-11-21 18:43 ` Jorge Ramirez-Ortiz
2025-11-21 19:22 ` Konrad Dybcio [this message]
2025-11-25 12:55 ` Jorge Ramirez
2025-11-27 11:47 ` Konrad Dybcio
2025-11-27 17:11 ` Jorge Ramirez
2025-11-27 18:34 ` Konrad Dybcio
2025-11-22 16:17 ` Bryan O'Donoghue
2025-11-25 8:29 ` Dikshita Agarwal
2025-11-25 12:52 ` Jorge Ramirez
2025-11-25 13:09 ` Dikshita Agarwal
2025-11-25 21:19 ` Jorge Ramirez
2025-11-26 5:31 ` Dikshita Agarwal
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=249ccbbc-7990-43f0-b205-d5f33a1c9ad3@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=bod@kernel.org \
--cc=dikshita.agarwal@oss.qualcomm.com \
--cc=jorge.ramirez@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=vikash.garodia@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
all inboxes | Powered by JetHome®