fix: flowchart in section 6.2.2 to show multiple multiscalers#615
Merged
Conversation
PrathamTI
requested review from
StaticRocket,
VeeruPrudhvi,
cshilwant,
gehariprasath,
jeevantelukula,
praneethbajjuri and
uditkumarti
as code owners
cshilwant
requested changes
Jan 7, 2026
cshilwant
left a comment
cshilwant
left a comment
Member
There was a problem hiding this comment.
The CI is flagging the commit message format. Can you update it to match the project's commit convention?
It doesn't match regex: ^(build|chore|ci|docs|feat|fix|refactor|style){1}(\([\w\-\.]+\))?(!)?: ([\w ])+([\s\S]*)|(Merge).*|(fixup!.*)
The commit message should follow Conventional Commits. See https://www.conventionalcommits.org/
Suggest: Use <type>(<scope>): <description> with allowed types
The flowchart in section 6.2.2 incorrectly showed a single tiovxmultiscaler in the GStreamer pipeline, which did not match the actual pipeline code. Since tiovxmultiscaler cannot scale beyond 1/4 resolution, multiple multiscaler blocks are required in the pipeline. Updated the flowchart to indicate "tiovxmultiscaler x2" to accurately reflect that two MSC blocks are used in the implementation. This fixes the discrepancy between the documentation flowchart and the actual code implementation. Fix: SITSW-6487 Reference: https://software-dl.ti.com/processor-sdk-linux/esd/AM62AX/10_01_00/exports/edgeai-docs/common/edgeai_dataflows.html#id2 Signed-off-by: Pratham Deshmukh <p-deshmukh@ti.com>
Contributor
Author
Resolved. |
cshilwant
approved these changes
Jan 7, 2026
v-singh1
approved these changes
Jan 7, 2026
Akshay-Abdar
approved these changes
Jan 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The flowchart in section 6.2.2 incorrectly showed a single tiovxmultiscaler in the GStreamer pipeline, which did not match the actual pipeline code.
Since tiovxmultiscaler cannot scale beyond 1/4 resolution, multiple multiscaler blocks are required in the pipeline. Updated the flowchart to indicate "tiovxmultiscaler x2" to accurately reflect that two MSC blocks are used in the implementation.
This fixes the discrepancy between the documentation flowchart and the actual code implementation.
Fix: SITSW-6487
Reference: https://software-dl.ti.com/processor-sdk-linux/esd/AM62AX/10_01_00/exports/edgeai-docs/common/edgeai_dataflows.html#id2