Skip to content

Promotion to 1.0.23 (qcom/ubuntu/resolute) - #104

Merged
renjiang-qti merged 19 commits into
qcom/ubuntu/resolutefrom
debian/pr/qcom-ubuntu-resolute/1.0.23-1
Jul 30, 2026
Merged

Promotion to 1.0.23 (qcom/ubuntu/resolute)#104
renjiang-qti merged 19 commits into
qcom/ubuntu/resolutefrom
debian/pr/qcom-ubuntu-resolute/1.0.23-1

Conversation

@qcom-service-bot

Copy link
Copy Markdown
Contributor

Automated promotion of upstream version 1.0.23 (tag: v1.0.23) to branch qcom/ubuntu/resolute.

GCC 16.1 with -Wstringop-overread (turned into an error by the
driver's own -Werror) rejects the byte-wise copies of a whole
struct v4l2_format:

  msm_venc.c:1327:9: error: 'memcpy' reading 208 bytes from a region
  of size 0 [-Werror=stringop-overread]
  note: source object is likely at address zero

After msm_venc_s_fmt_input() is inlined into msm_venc_s_fmt(), the
compiler's value-range analysis mis-judges the source object
(&inst->fmts[INPUT_PORT]) as a zero-sized region at address zero and
rejects the memcpy(). The source is a regular member of struct
msm_vidc_inst and is never NULL, so this is a false positive, but it
breaks the build for newer toolchains.

Copy the structures with a plain aggregate assignment instead of
memcpy(). The assignment is a by-value copy of the whole structure -
it copies the entire object, including the embedded union, exactly as
the old memcpy(..., sizeof(struct v4l2_format)) did. It lets the
compiler derive the size from the type and is not subject to the
string/memory builtin diagnostics, so it both fixes the build and is
more idiomatic.

No functional change intended.

Assisted-by: Claude:claude-opus-4.8
Signed-off-by: Ricardo Salveti <ricardo.salveti@oss.qualcomm.com>
Identify "video-mem" as a DDR bus type in the power helper function
get_type_frm_name().

Without this, any interconnect bus named "video-mem" is classified
as PERF, which defaults to voting for the maximum static bandwidth.
Correctly classifying "video-mem" as DDR allows the driver to vote
dynamically for DDR bandwidth (bw_ddr) as intended.

Signed-off-by: Priyanka Gujjula <pgujjula@qti.qualcomm.com>
…3 OPP rate path""

This reverts commit fe7e009.

Signed-off-by: Gourav Kumar <gouravk@qti.qualcomm.com>
…rdware power sequences""

This reverts commit 401af87.

Signed-off-by: Gourav Kumar <gouravk@qti.qualcomm.com>
…nch""

This reverts commit 7f921b6.

Signed-off-by: Gourav Kumar <gouravk@qti.qualcomm.com>
This reverts commit 0126f47.

Signed-off-by: Gourav Kumar <gouravk@qti.qualcomm.com>
The dt-bindings header <dt-bindings/clock/qcom,x1p42100-videocc.h>
is present in qcom-specific kernel trees (qcom-6.18, qcom-next) but
is not yet available in linux-yocto based trees (yocto-6.18,
yocto-next).  A file-existence check cannot be replaced by a version
number because both kernel families share the same version.

Add a build-time probe in video/Kbuild that tests for the header
and, when found, passes -DMSM_VIDC_HAS_X1P42100_VIDEOCC=1 to compiler.

Guard the include of that header and the three clock-table entries
whose initialiser values (VIDEO_CC_MVS0C_CLK, VIDEO_CC_MVS0_CLK,
VIDEO_CC_MVS0_BSE_CLK) are defined exclusively by it with the same
macro.

Also guard the qcom,x1p42100-iris entry in msm_vidc_dt_match[] so
that the kernel does not associate the driver with the purwa device
at all on kernels where the header is absent.

Signed-off-by: Gourav Kumar <gouravk@qti.qualcomm.com>
…overread

video: driver: copy struct v4l2_format by assignment
Update context bank initialization to work with both child node based and
iommu-map dt configurations, allowing the driver to discover and configure
IOMMU mappings from the appropriate dt node. Also ensure context bank
devices are initialized only when a valid IOMMU mapping is established.

Signed-off-by: Vishnu Reddy <busanna.reddy@oss.qualcomm.com>
iris: update context bank creation to support dt subnodes
Update the upstream tag trigger workflow to use actions/github-script@v9,
avoiding the Node 20 deprecation warning from the older action version.

Also refresh the workflow comments to reflect the current packaging branch
names, using qli/debian/latest and qli/debian/trixie while keeping
qcom/ubuntu/resolute unchanged.

Signed-off-by: Renjiang Han <renjiang@qti.qualcomm.com>
Exported vb2 dma-bufs may outlive the msm_vidc_buffer that created them.
During teardown, msm_vb2_put() can return the msm_vidc_buffer to the
buffer pool while the exported dma_buf still holds a reference through
msm_vidc_dma_buf_info. A later dma_buf release then dereferences
dinfo->buf to free the sg_table, which can fault after the buffer has
already been recycled or destroyed.

Keep the exported sg_table ownership information in
msm_vidc_dma_buf_info, and make dma_buf attach/release use that state
instead of dereferencing dinfo->buf. When msm_vb2_put() observes that
dma_buf release is deferred, detach the soon-to-be-pooled buffer from
the exported dma_buf state before returning it to the pool.

Signed-off-by: Renjiang Han <renjiang@qti.qualcomm.com>
video-driver: avoid exported dmabuf release use-after-free
Pass PKG_REPO_GITHUB_NAME through the step environment instead of
expanding the repository variable directly inside the github-script
body.

Signed-off-by: Renjiang Han <renjiang@qti.qualcomm.com>
Add IR_PERIOD capability support for Hamoa encoder sessions and
register the corresponding capability dependencies.
 
Reuse the common IR_PERIOD adjust and set handlers by moving
the implementation from platform-specific code into the common
platform layer. Update Kodiak, Lemans and Monaco to use the
shared implementation and remove duplicated code.

Change-Id: Iffd111abb7f3fd90e0b86edb3a1b440c73de7664
Signed-off-by: Renjiang Han <renjiang@qti.qualcomm.com>
…esolute/1.0.23-1'

This commit pulls in upstream changes from 'v1.0.23' into the
Debian packaging branch.

Since upstream project might have content of their own in their .github/
folder (because they have CI stuff on their side), it's important to NOT
pick up .github/ folder from upstream, and only leave the .github/
folder from debian packaging branch.

The same applies to debian/ folder if upstream has one (which is rare
but possible).

This commit was generated automatically by
qcom-build-utils/scripts/merge_debian_packaging_upstream.

Signed-off-by: GitHub Service Bot <githubservice@qti.qualcomm.com>
Signed-off-by: GitHub Service Bot <githubservice@qti.qualcomm.com>
@renjiang-qti
renjiang-qti merged commit 2483461 into qcom/ubuntu/resolute Jul 30, 2026
22 of 24 checks passed
@renjiang-qti
renjiang-qti deleted the debian/pr/qcom-ubuntu-resolute/1.0.23-1 branch July 30, 2026 03:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants