From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
rfoss@kernel.org, todor.too@gmail.com, agross@kernel.org,
andersson@kernel.org, mchehab@kernel.org,
hverkuil-cisco@xs4all.nl, laurent.pinchart@ideasonboard.com,
sakari.ailus@linux.intel.com, andrey.konovalov@linaro.org
Cc: linux-media@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v1 9/9] media: qcom: camss: Fix csid-gen2 for test pattern generator
Date: Tue, 22 Aug 2023 18:38:57 +0200 [thread overview]
Message-ID: <4f271226-c45a-42a8-95ff-8ec008ce7e72@linaro.org> (raw)
In-Reply-To: <20230822161620.1915110-10-bryan.odonoghue@linaro.org>
On 22.08.2023 18:16, Bryan O'Donoghue wrote:
> From: Andrey Konovalov <andrey.konovalov@linaro.org>
>
> In the current driver csid Test Pattern Generator (TPG) doesn't work.
> This change:
> - fixes writing frame width and height values into CSID_TPG_DT_n_CFG_0
> - fixes the shift by one between test_pattern control value and the
> actual pattern.
> So that TPG starts working, but with the below limitations:
> - only test_pattern=9 works as it should
> - test_pattern=8 and test_pattern=7 produce black frame (all zeroes)
> - the rest of test_pattern's don't work (yavta doesn't get the data)
> - regardless of the CFA pattern set by 'media-ctl -V' the actual pixel
> order is always the same (RGGB for any RAW8 or RAW10P format in
> 4608x2592 resolution).
>
> Tested with:
>
> RAW10P format, VC0:
> media-ctl -V '"msm_csid0":0[fmt:SRGGB10/4608x2592 field:none]'
> media-ctl -V '"msm_vfe0_rdi0":0[fmt:SRGGB10/4608x2592 field:none]'
> media-ctl -l '"msm_csid0":1->"msm_vfe0_rdi0":0[1]'
> v4l2-ctl -d /dev/v4l-subdev6 -c test_pattern=9
> yavta -B capture-mplane --capture=3 -n 3 -f SRGGB10P -s 4608x2592 /dev/video0
>
> RAW10P format, VC1:
> media-ctl -V '"msm_csid0":2[fmt:SRGGB10/4608x2592 field:none]'
> media-ctl -V '"msm_vfe0_rdi1":0[fmt:SRGGB10/4608x2592 field:none]'
> media-ctl -l '"msm_csid0":2->"msm_vfe0_rdi1":0[1]'
> v4l2-ctl -d /dev/v4l-subdev6 -c test_pattern=9
> yavta -B capture-mplane --capture=3 -n 3 -f SRGGB10P -s 4608x2592 /dev/video1
>
> RAW8 format, VC0:
> media-ctl --reset
> media-ctl -V '"msm_csid0":0[fmt:SRGGB8/4608x2592 field:none]'
> media-ctl -V '"msm_vfe0_rdi0":0[fmt:SRGGB8/4608x2592 field:none]'
> media-ctl -l '"msm_csid0":1->"msm_vfe0_rdi0":0[1]'
> yavta -B capture-mplane --capture=3 -n 3 -f SRGGB8 -s 4608x2592 /dev/video0
>
> Fixes: eebe6d00e9bf ("media: camss: Add support for CSID hardware version Titan 170")
> Cc: stable@vger.kernel.org
> Signed-off-by: Andrey Konovalov <andrey.konovalov@linaro.org>
> Signed-off-by: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
> ---
That's a whole lot to unroll..
[...]
> if (tg->enabled) {
> - /* Config Test Generator */
> - vc = 0xa;
> -
Which part does this hunk correlate to?
> /* configure one DT, infinite frames */
> val = vc << TPG_VC_CFG0_VC_NUM;
> val |= INTELEAVING_MODE_ONE_SHOT << TPG_VC_CFG0_LINE_INTERLEAVING_MODE;
> @@ -370,14 +367,14 @@ static void __csid_configure_stream(struct csid_device *csid, u8 enable, u8 vc)
>
> writel_relaxed(0x12345678, csid->base + CSID_TPG_LFSR_SEED);
>
> - val = input_format->height & 0x1fff << TPG_DT_n_CFG_0_FRAME_HEIGHT;
> - val |= input_format->width & 0x1fff << TPG_DT_n_CFG_0_FRAME_WIDTH;
> + val = (input_format->height & 0x1fff) << TPG_DT_n_CFG_0_FRAME_HEIGHT;
> + val |= (input_format->width & 0x1fff) << TPG_DT_n_CFG_0_FRAME_WIDTH;
> writel_relaxed(val, csid->base + CSID_TPG_DT_n_CFG_0(0));
This screams necessity for FIELD_PREP/GET! Could you please convert
it in another series if you have time for it?
Konrad
next prev parent reply other threads:[~2023-08-22 16:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 16:16 [PATCH v1 0/9] media: qcom: camss: Bugfix series Bryan O'Donoghue
2023-08-22 16:16 ` [PATCH v1 1/9] media: qcom: camss: Fix pm_domain_on sequence in probe Bryan O'Donoghue
2023-08-22 16:16 ` [PATCH v1 2/9] media: qcom: camss: Fix V4L2 async notifier error path Bryan O'Donoghue
2023-08-22 16:16 ` [PATCH v1 3/9] media: qcom: camss: Fix vfe_get() error jump Bryan O'Donoghue
2023-08-22 16:16 ` [PATCH v1 4/9] media: qcom: camss: Fix VFE-17x vfe_disable_output() Bryan O'Donoghue
2023-08-22 16:16 ` [PATCH v1 5/9] media: qcom: camss: Fix VFE-480 vfe_disable_output() Bryan O'Donoghue
2023-08-22 16:16 ` [PATCH v1 6/9] media: qcom: camss: Fix missing vfe_lite clocks check Bryan O'Donoghue
2023-08-22 16:16 ` [PATCH v1 7/9] media: qcom: camss: Fix invalid clock enable bit disjunction Bryan O'Donoghue
2023-08-22 16:16 ` [PATCH v1 8/9] media: qcom: camss: Fix set CSI2_RX_CFG1_VC_MODE when VC is greater than 3 Bryan O'Donoghue
2023-08-22 16:32 ` Konrad Dybcio
2023-08-22 19:03 ` Bryan O'Donoghue
2023-08-22 19:03 ` Konrad Dybcio
2023-08-22 16:16 ` [PATCH v1 9/9] media: qcom: camss: Fix csid-gen2 for test pattern generator Bryan O'Donoghue
2023-08-22 16:38 ` Konrad Dybcio [this message]
2023-08-22 19:07 ` Bryan O'Donoghue
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=4f271226-c45a-42a8-95ff-8ec008ce7e72@linaro.org \
--to=konrad.dybcio@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=andrey.konovalov@linaro.org \
--cc=bryan.odonoghue@linaro.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=laurent.pinchart@ideasonboard.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=rfoss@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=stable@vger.kernel.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
all inboxes | Powered by JetHome®