From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: "Milen Mitkov (Consultant)" <quic_mmitkov@quicinc.com>,
linux-media@vger.kernel.org, linux-arm-msm@vger.kernel.org,
robert.foss@linaro.org, akapatra@quicinc.com, jzala@quicinc.com,
todor.too@gmail.com
Cc: agross@kernel.org, konrad.dybcio@somainline.org,
mchehab@kernel.org, cgera@qti.qualcomm.com, gchinnab@quicinc.com,
ayasan@qti.qualcomm.com, laurent.pinchart@ideasonboard.com
Subject: Re: [PATCH v6 4/4] media: camss: sm8250: Pipeline starting and stopping for multiple virtual channels
Date: Mon, 5 Dec 2022 17:01:27 +0000 [thread overview]
Message-ID: <556407bc-8ff5-e929-9eff-aa7b4328f095@linaro.org> (raw)
In-Reply-To: <d1554eec-7f45-c513-f77c-7868943de2d4@quicinc.com>
On 05/12/2022 16:49, Milen Mitkov (Consultant) wrote:
>
> On 05/12/2022 18:43, Bryan O'Donoghue wrote:
>> On 05/12/2022 15:24, quic_mmitkov@quicinc.com wrote:
>>> media-ctl -v -d /dev/media0 -V '"imx577
>>> '22-001a'":0[fmt:SRGGB10/3840x2160 field:none]'
>>
>> I really like the improved commit log, thank you for that.
>>
>> SRGGB10/3840x2160 drivers/media/i2c/imx412.c that's not a supported
>> resolution.
>>
>> media-ctl -v -d /dev/media0 -V '"imx577
>> '22-001a'":0[fmt:SRGGB10/4056x3040 field:none]'
>>
>> ?
>>
>> ---
>> bod
>
>
> Hi Bryan,
>
> it's not a supported resolution with the current imx412/577 driver in
> upstream. We tested with a different driver (with proprietary Sony
> registers)
>
> that uses this resolution that generates 2 multiplexed streams. It would
> be impossible for pure upstream solution to test this driver with imx412
> right now.
>
> I couldn't have used the upstream supported resolution either, because
> it's of a sensor mode with only 1 stream and that would create the
> impression that anybody can just take this imx412 sensor and use the
> upstream driver to test the solution, but this is in fact not possible
> without register changes to the sensor driver itself.
>
> Regards,
>
> Milen
>
OK fair enough, I think you should make a more explicit statement about
the mapping of VC to RDI
Here's the real bit of salient information for whomever is trying to get
VCs working in the future
media-ctl -l '"msm_csid0":1->"msm_vfe0_rdi0":0[1]'
media-ctl -l '"msm_csid0":2->"msm_vfe0_rdi1":0[1]'
The first VC msm_csid0":1 always maps to RDI0 the second VC always maps
to RDI1
I think we should document that mapping clearly so that you don't have
to read or understand the code to know
media-ctl -l '"msm_csid0":1->"msm_vfe0_rdi1":0[1]' is an invalid mapping
and why that is.
---
bod
prev parent reply other threads:[~2022-12-05 17:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 15:24 [PATCH v6 0/4] media: camss: sm8250: Virtual channels support for SM8250 quic_mmitkov
2022-12-05 15:24 ` [PATCH v6 1/4] media: camss: sm8250: Virtual channels for CSID quic_mmitkov
2022-12-05 15:24 ` [PATCH v6 2/4] media: camss: vfe: Reserve VFE lines on stream start and link to CSID quic_mmitkov
2022-12-06 13:55 ` Bryan O'Donoghue
2022-12-05 15:24 ` [PATCH v6 3/4] media: camss: vfe-480: Multiple outputs support for SM8250 quic_mmitkov
2022-12-05 15:24 ` [PATCH v6 4/4] media: camss: sm8250: Pipeline starting and stopping for multiple virtual channels quic_mmitkov
2022-12-05 16:43 ` Bryan O'Donoghue
2022-12-05 16:49 ` Milen Mitkov (Consultant)
2022-12-05 17:01 ` Bryan O'Donoghue [this message]
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=556407bc-8ff5-e929-9eff-aa7b4328f095@linaro.org \
--to=bryan.odonoghue@linaro.org \
--cc=agross@kernel.org \
--cc=akapatra@quicinc.com \
--cc=ayasan@qti.qualcomm.com \
--cc=cgera@qti.qualcomm.com \
--cc=gchinnab@quicinc.com \
--cc=jzala@quicinc.com \
--cc=konrad.dybcio@somainline.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=quic_mmitkov@quicinc.com \
--cc=robert.foss@linaro.org \
--cc=todor.too@gmail.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