- 10 Aug, 2023 40 commits
-
-
Alain Volmat authored
Avoid calling s_stream on each subdev until reaching the sensor and instead call s_stream on the source subdev only (which will in turn do whatever needed to start the stream). Signed-off-by:
Alain Volmat <alain.volmat@foss.st.com> Reviewed-by:
Hugues FRUCHET <hugues.fruchet@foss.st.com> Signed-off-by:
Hans Verkuil <hverkuil-cisco@xs4all.nl>
-
Alain Volmat authored
Cascade the s_stream call to the source subdev whenever the bridge streaming is enable / disabled. Signed-off-by:
Benjamin Mugnier <benjamin.mugnier@foss.st.com> Signed-off-by:
-
Paul Kocialkowski authored
The parts about fields that are returned typically comes after "Required fields" so it feels more consistent to name them "Returned fields". Signed-off-by:
Paul Kocialkowski <paul.kocialkowski@bootlin.com> Signed-off-by:
-
Paul Kocialkowski authored
An extra whitespace after the asterisks prevents bold syntax parsing and results in the asterisks shown in the (non-bold) title. Signed-off-by:
-
Patrick Whewell authored
The firmware path for the sm8250 resources is incorrect. This fixes the path to address the firmware correctly. Signed-off-by:
Patrick Whewell <patrick.whewell@sightlineapplications.com> Signed-off-by:
Stanimir Varbanov <stanimir.k.varbanov@gmail.com> Signed-off-by:
-
Stephan Gerhold authored
Reserved memory can be either looked up using the generic function of_address_to_resource() or using the special of_reserved_mem_lookup(). The latter has the advantage that it ensures that the referenced memory region was really reserved and is not e.g. status = "disabled". of_reserved_mem also supports allocating reserved memory dynamically at boot time. This works only when using of_reserved_mem_lookup() since there won't be a fixed address in the device tree. Switch the code to use of_reserved_mem_lookup(). There is no functional difference for static reserved memory allocations. Signed-off-by:
Stephan Gerhold <stephan@gerhold.net> Signed-off-by:
-
Konrad Dybcio authored
Not all SC7180 devices ship with ChromeOS firmware. WoA devices use Android-like TZ, which uses PAS for image authentication. That requires the predefined virtual address ranges to be passed via scm calls. Define them to enable Venus on non-CrOS SC7180 devices. Signed-off-by:
Konrad Dybcio <konrad.dybcio@linaro.org> Signed-off-by:
-
Konrad Dybcio authored
This write was last present on msm-3.10, which means before HFI3XX platforms were introduced. Guard it with an appropriate if condition. Does not seem to have any adverse effects on at least SM8250. Signed-off-by:
-
Konrad Dybcio authored
Now that we have a way which is independent of the HFI version to set the correct fields in hfi_buffer_requirements, use it! Signed-off-by:
-
Konrad Dybcio authored
Currently we have macros to access these, but they don't provide a way to override the remapped fields. Replace the macros with actual get/set pairs to fix that. Reviewed-by:
Bryan O'Donoghue <bryan.odonoghue@linaro.org> Signed-off-by:
-
Konrad Dybcio authored
Replace the general IS_V6 checks with more specific VPU version checks. Reviewed-by:
-
Konrad Dybcio authored
This is not a matter of the host SoC, but the VPU chip in Venus. Fix it. Reviewed-by:
Vikash Garodia <quic_vgarodia@quicinc.com> Signed-off-by:
-
Konrad Dybcio authored
Replace the general IS_V6 checks with more specific VPU version checks. Signed-off-by:
-
Konrad Dybcio authored
Replace the general IS_V6 checks with more specific VPU version checks. Signed-off-by:
-
Konrad Dybcio authored
Replace the general IS_V6 checks with more specific VPU version checks. Signed-off-by:
-
Konrad Dybcio authored
Replace the general IS_V6 checks with more specific VPU version checks. Reviewed-by:
Dikshita Agarwal <quic_dikshita@quicinc.com> Signed-off-by:
-
Konrad Dybcio authored
Only IRIS2(_1) should enter the until-now-IS_V6() path and IRIS2_1 can be used instead of openly checking the number of VPP pipes. Use VPU version comparison in both of these cases instead. Signed-off-by:
-
Konrad Dybcio authored
The current assumption of IS_V6 is overgeneralized. Adjust the logic to take the VPU hardware version into account. Signed-off-by:
-
Konrad Dybcio authored
The current assumption of IS_V6 is overgeneralized. Adjust the logic to take the VPU hardware version into account. Signed-off-by:
-
Konrad Dybcio authored
The qcom_scm_mem_protect_video_var accepts two sets of <addr size> pairs as arguments. They describe the virtual address ranges of the CP (Content Protection) and CP_NONPIXEL regions. It is however not immediately obvious how to obtain these values. Leave a comment explaining how one can translate the vendor device tree properties for use with the mainline driver. Reviewed-by:
-
Konrad Dybcio authored
Add vpu_version where I was able to retrieve the information to allow for more precise hardware-specific code path matching. Reviewed-by:
-
Konrad Dybcio authored
The Video Processing Unit hardware version is the differentiator, based on which the video driver should decide which code paths to take. Up until now, we've relied on HFI versions instead, but that was just a happy accident between recent SoCs. Add a field in the res struct and add correlated definitions that will be used to account for the aforementioned differences. Reviewed-by:
-
Konrad Dybcio authored
The startup procedure shouldn't be started with interrupts masked, as that may entail silent failures. Kick off initialization only after the interrupts are unmasked. Cc: stable@vger.kernel.org # v4.12+ Fixes: d96d3f30 ("[media] media: venus: hfi: add Venus HFI files") Signed-off-by:
-
Konrad Dybcio authored
As per information from Qualcomm [1], this property is not really supported beyond msm8916 (HFI V1) and some newer HFI versions really dislike receiving it, going as far as crashing the device. Only consider toggling it (via the module option) on HFIV1. While at it, get rid of the global static variable (which defaulted to zero) which was never explicitly assigned to for V1. Note: [1] is a reply to the actual message in question, as lore did not properly receive some of the emails.. [1] https://lore.kernel.org/lkml/955cd520-3881-0c22-d818-13fe9a47e124@linaro.org/ Fixes: 7ed9e0b3 ("media: venus: hfi, vdec: v6 Add IS_V6() to existing IS_V4() if locations") Signed-off-by:
-
Yunfei Dong authored
The vpu maybe null pointer or unreasonable value when scp crash, need to validate that the vpu pointer and the vpu instance within this context is valid in case of leading to kernel reboot. Fixes: 27a274db ("[media] vcodec: mediatek: Add Mediatek VP8 Video Encoder Driver") Signed-off-by:
Yunfei Dong <yunfei.dong@mediatek.com> Reported-by:
Steve Cho <stevecho@google.com> Signed-off-by:
-
Yunfei Dong authored
The vpu maybe null pointer or unreasonable value when scp crash, need to validate that the vpu pointer and the vpu instance within this context is valid in case of leading to kernel reboot. Fixes: 590577a4 ("[media] vcodec: mediatek: Add Mediatek V4L2 Video Decoder Driver") Signed-off-by:
Nicolas Dufresne <nicolas.dufresne@collabora.com> Signed-off-by:
-
Mingjia Zhang authored
Adding to support capture formats V4L2_PIX_FMT_MT2110T and V4L2_PIX_FMT_MT2110R for 10bit playback. Need to get the size of each plane again when user space setting syntax to get 10bit information. V4L2_PIX_FMT_MT2110T for AV1/VP9/HEVC. V4L2_PIX_FMT_MT2110R for H264. Signed-off-by:
Mingjia Zhang <mingjia.zhang@mediatek.com> Co-developed-by:
-
Mingjia Zhang authored
Define one uncompressed capture format V4L2_PIX_FMT_MT2110R in order to support 10bit for H264 in mt8195. Signed-off-by:
-
Mingjia Zhang authored
Define one uncompressed capture format V4L2_PIX_FMT_MT2110T in order to support 10bit for AV1/VP9/HEVC in mt8195. Signed-off-by:
-
Yunfei Dong authored
Move all decoder files to folder decoder. Move all encoder files to folder encoder. Move common files which shared for encoder and decoder to folder common. Change include header files and Makefile to fix build error. Signed-off-by:
AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> Signed-off-by:
-
Yunfei Dong authored
remove unused include header for .c files Signed-off-by:
-
Yunfei Dong authored
Fix unreasonable coding style. Fix unreasonable parameter definition. Signed-off-by:
-
Yunfei Dong authored
Adding different dev struct for encoder and decoder, remove 'struct mtk_vcodec_dev'. Signed-off-by:
-
Yunfei Dong authored
Adding different context struct for encoder and decoder and removing struct 'mtk_vcodec_ctx'. Signed-off-by:
-
Yunfei Dong authored
Adding different macro mtk_v4l2_vdec_dbg and mtk_v4l2_venc_dbg for encoder and decoder. Then calling the common macro mtk_v4l2_debug to print debug message. Replace pr_err with dev_err for 'mtk_v4l2_err' debug message. Replace pr_debug with dev_dbg for 'mtk_v4l2_debug' debug message. Signed-off-by:
-
Yunfei Dong authored
'mtk_vcodec_debug' and 'mtk_vcodec_err' depends on 'mtk_vcodec_ctx' to get the index of each instance. Define two different macro mtk_vdec_debug and mtk_venc_debug for decoder and encoder, and re-write macro mtk_vcodec_debug as the common interface which is called by mtk_vdec_debug and mtk_venc_debug. The vcodec debug log can be separeated by encoder and decoder. Signed-off-by:
-
Yunfei Dong authored
Removing unresonable and useless debug log enter and leave in order to simply the log message. Signed-off-by:
-
Yunfei Dong authored
The shared struct 'mtk_vcodec_ctx/dev' will be changed to 'mtk_vcodec_enc_ctx/dev' and 'mtk_vcodec_dec_ctx/dev' in order to separate encoder and decoder. Removing common struct 'mtk_vcodec_ctx/dev' for shared interface which encoder and decoder used at the same time. Then encoder and decoder can call the same interface independently. Signed-off-by:
-
Yunfei Dong authored
Align scp and vpu firmware interface, remove the depedency for 'struct mtk_vcodec_dev' and 'struct mtk_vcodec_ctx'. It will be much easier to separate video encoder and decoder. Signed-off-by:
-
Yunfei Dong authored
remove unused parameter in struct mtk_vcodec_dev. Signed-off-by:
-
