Add QCS615 LYRA EVK platform

[kranthi-peruri]

Add the device tree for the QCS615-based Lyra EVK platform. The
platform is composed of a System-on-Module following the SMARC
standard, and a Carrier Board.

The initial device tree includes support for:
- CPU and memory
- UART
- GPIOs
- Regulators
- PMIC
- Early console
- AT24MAC602 EEPROM
- MCP2515 SPI to CAN
- ADV7535 DSI-to-HDMI bridge
- DisplayPort interface
- Wi-Fi/BT

[qlijarvis]

PR #829 — validate-patch

PR: #829

Verdict	Issues	Detailed Report
❌	8	Full report

Final Summary

1. Lore link present: No — FROMLIST: prefix used but no Link: https://lore.kernel.org/r/<message-id> tag found in commit message
2. Lore link matches PR commits: N/A — cannot compare without a lore link
3. Upstream patch status: Unknown — cannot verify upstream review status without lore link
4. PR present in qcom-next/topics: Fail - 1/1 commit(s) are missing from both qcom-next and topics

Verdict: ❌ — click to expand

🔍 Patch Validation

PR: #829 - FROMLIST: arm64: dts: qcom: qsc615-lyra-evk: Add support for QCS615 lyra evk board
Upstream commit: N/A (no lore link found)
Verdict: ❌ FAIL

Commit Message

Check	Status	Note
Subject matches upstream	❌	Cannot verify - no lore link to compare against
Body preserves rationale	❌	Cannot verify - no lore link to compare against
Fixes tag present/correct	N/A	Not a fix commit
Authorship preserved	❌	Cannot verify - no lore link to compare against
Backport note (if applicable)	N/A	Not a backport

Diff

File	Status	Notes
arch/arm64/boot/dts/qcom/Makefile	❌	Cannot verify against upstream - no lore link
arch/arm64/boot/dts/qcom/talos-lyra-evk.dts	❌	Cannot verify against upstream - no lore link

Issues

Critical: Missing lore.kernel.org link

• The commit uses the FROMLIST: prefix, which indicates the patch was posted to a mailing list
• Per kernel commit message conventions, FROMLIST: commits must include a Link: https://lore.kernel.org/r/<message-id> tag
• No lore link was found in the commit message

Subject line inconsistency

• Subject mentions "qsc615-lyra-evk" but the actual DTS file created is talos-lyra-evk.dts
• This naming mismatch suggests either the subject or filename needs correction

Integration presence failure

• Commit is missing from both qcom-next and kernel topic branches
• For a FROMLIST: commit, this is expected if the patch is still under review upstream
• However, without a lore link, the upstream review status cannot be verified

Verdict

Do not merge. This commit cannot be validated because it lacks the required lore.kernel.org link. The FROMLIST: prefix indicates this patch was posted to a mailing list, but without a Link tag, reviewers cannot:

1. Verify the patch content matches what was posted upstream
2. Check the upstream review status and community feedback
3. Confirm authorship and sign-off chain integrity
4. Track the patch through the upstream acceptance process

Final Summary

1. Lore link present: No — FROMLIST: prefix used but no Link: https://lore.kernel.org/r/<message-id> tag found in commit message
2. Lore link matches PR commits: N/A — cannot compare without a lore link
3. Upstream patch status: Unknown — cannot verify upstream review status without lore link
4. PR present in qcom-next/topics: No — commit missing from both qcom-next and topics (per integration_presence_report.md: "FAIL - 1/1 commit(s) are missing from both qcom-next and topics")

Recommendation

Add a Link: https://lore.kernel.org/r/<message-id> line to the commit message pointing to the upstream mailing list posting, then re-run validation. If the patch has not yet been posted upstream, consider using the PENDING: prefix instead of FROMLIST: until it is actually posted to the mailing list.

Additionally, resolve the subject/filename inconsistency: either update the subject to reference "talos-lyra-evk" or rename the DTS file to "qsc615-lyra-evk.dts" to match the subject line.

Deterministic Integration Presence

Integration Presence Report

This report is generated by Jarvis before validate-patch runs.
It is the authoritative source for whether PR changes are already present
in qcom-next or in the kernel topic branches.

Kernel repo: /local/mnt/workspace/sgaud/Qgenie/image_pipeline/kernel
qcom-next ref: a5cf3debd8c3c660711ad586ad4bb84e9ca42635
topics remote: topics -> https://github.com/qualcomm-linux/kernel-topics
topics fetch: fetched

Commit	Subject	qcom-next	topics	Final
1/1	[PATCH] FROMLIST: arm64: dts: qcom: qsc615-lyra-evk: Add support for	missing - no subject, patch-id, or full tree-content match found	missing - no subject, patch-id, or full tree-content match found	missing

Final Status

overall_status: FAIL
present_commits: 0/1
partial_commits: 0/1
missing_commits: 1/1
topics_checked_for_commits: 1/1
final_summary: PR present in qcom-next/topics: Fail - 1/1 commit(s) are missing from both qcom-next and topics

[qlijarvis]

PR #829 — checker-log-analyzer

PR: #829
Checker run: https://github.com/qualcomm-linux/kernel-config/actions/runs/29420885373

Checker	Result	Summary
Checker	Result	Summary
checkpatch	✅	Passed
dt-binding-check	⏭️	Skipped (no binding changes)
dtb-check	❌	USB node schema validation failures
sparse-check	⏭️	Skipped (no C/H changes)
check-uapi-headers	⏭️	Skipped (no UAPI changes)
check-patch-compliance	❌	Missing Link: tag
tag-check	✅	FROMLIST: prefix present

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #829 - FROMLIST: arm64: dts: qcom: qsc615-lyra-evk: Add support for QCS615 lyra evk board
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/29420885373

Checker	Result	Summary
checkpatch	✅	Passed
dt-binding-check	⏭️	Skipped (no binding changes)
dtb-check	❌	USB node schema validation failures
sparse-check	⏭️	Skipped (no C/H changes)
check-uapi-headers	⏭️	Skipped (no UAPI changes)
check-patch-compliance	❌	Missing Link: tag
tag-check	✅	FROMLIST: prefix present

---

❌ dtb-check

Root cause: The new talos-lyra-evk.dts includes talos-evk-som.dtsi, which contains USB nodes (usb@a600000, usb@a800000) that violate the qcom,snps-dwc3.yaml binding schema.

Failure details:

talos-lyra-evk.dtb: usb@a600000 (qcom,qcs615-dwc3): #address-cells: 1 was expected
talos-lyra-evk.dtb: usb@a600000 (qcom,qcs615-dwc3): #size-cells: 0 was expected
talos-lyra-evk.dtb: usb@a600000 (qcom,qcs615-dwc3): Unevaluated properties are not allowed 
  ('#address-cells', '#size-cells', 'dr_mode', 'phy-names', 'phys', 'ranges', 
   'snps,dis-u1-entry-quirk', 'snps,dis-u2-entry-quirk', 'snps,dis_enblslpm_quirk', 
   'snps,dis_u2_susphy_quirk', 'snps,dis_u3_susphy_quirk', 'snps,has-lpm-erratum', 
   'snps,hird-threshold', 'snps,usb3_lpm_capable' were unexpected)

talos-lyra-evk.dtb: usb@a800000 (qcom,qcs615-dwc3): #address-cells: 1 was expected
talos-lyra-evk.dtb: usb@a800000 (qcom,qcs615-dwc3): #size-cells: 0 was expected
talos-lyra-evk.dtb: usb@a800000 (qcom,qcs615-dwc3): Unevaluated properties are not allowed 
  ('#address-cells', '#size-cells', 'dr_mode', 'maximum-speed', 'phy-names', 'phys', 
   'ranges', 'snps,dis_enblslpm_quirk', 'snps,dis_u2_susphy_quirk', 'snps,dis_u3_susphy_quirk', 
   'snps,has-lpm-erratum', 'snps,hird-threshold' were unexpected)

Analysis:

This is a pre-existing tree issue in talos-evk-som.dtsi, not introduced by this PR. The PR only adds a new board DTS file that includes the existing SoM DTSI. The USB nodes in the included file have two problems:

1. Wrong cell values: The binding expects #address-cells = <1> and #size-cells = <0>, but the nodes likely have #address-cells = <2> and #size-cells = <2> (inherited from parent or explicitly set).

2. Unevaluated properties: The qcom,snps-dwc3.yaml binding uses unevaluatedProperties: false but doesn't declare many standard DWC3 properties (dr_mode, phy-names, phys, ranges, snps,* quirks). These properties should either be:

   • Added to the binding's properties: section, or
   • Allowed via unevaluatedProperties: true, or
   • Referenced via $ref to a parent schema that declares them

Fix:

This requires fixing the binding schema (Documentation/devicetree/bindings/usb/qcom,snps-dwc3.yaml), not the DTS file:

# In qcom,snps-dwc3.yaml, add to properties section:
properties:
  '#address-cells':
    const: 1
  '#size-cells':
    const: 0
  dr_mode: true
  phy-names: true
  phys: true
  ranges: true
  maximum-speed: true
  
  # Add all snps,* properties or reference snps,dwc3.yaml
  snps,dis-u1-entry-quirk: true
  snps,dis-u2-entry-quirk: true
  snps,dis_enblslpm_quirk: true
  snps,dis_u2_susphy_quirk: true
  snps,dis_u3_susphy_quirk: true
  snps,has-lpm-erratum: true
  snps,hird-threshold: true
  snps,usb3_lpm_capable: true

OR reference the generic DWC3 binding:

allOf:
  - $ref: snps,dwc3.yaml#

Reproduce locally:

make -j$(nproc) O=out defconfig
make -j$(nproc) O=out CHECK_DTBS=y arch/arm64/boot/dts/qcom/talos-lyra-evk.dtb

Note: Since this is a pre-existing issue in the included DTSI file (not introduced by this PR), the PR author should either:

1. Submit a separate patch to fix the binding schema first, or
2. Coordinate with maintainers to fix the binding as part of the board enablement series

---

❌ check-patch-compliance

Root cause: The commit message has a FROMLIST: prefix but is missing the required Link: tag pointing to the upstream lore.kernel.org posting.

Failure details:

Checking commit: FROMLIST: arm64: dts: qcom: qsc615-lyra-evk: Add support for QCS615 lyra evk board
No 'Link' found in commit message

Fix:

Add a Link: tag to the commit message body pointing to the lore.kernel.org URL where this patch was posted upstream:

git commit --amend

Then add before the Signed-off-by: line:

Link: https://lore.kernel.org/r/<message-id>
Signed-off-by: Kranthi Peruri <kperuri@qti.qualcomm.com>

If the patch hasn't been posted upstream yet, either:

• Post it to the appropriate mailing list first, then add the Link, or
• Change the prefix from FROMLIST: to PENDING: (though note that PENDING: will also fail check-patch-compliance as it's not in the allowed prefix list)

Reproduce locally:

# Verify the Link tag is present
git log -1 --format=%B 7774e974fdcf | grep -E "^Link:"

---

Verdict

2 blockers must be fixed before merge:

1. dtb-check failure — Pre-existing binding schema issue in qcom,snps-dwc3.yaml. The binding must be updated to allow the DWC3 properties used in talos-evk-som.dtsi. This is not a defect in the PR itself, but the DTB validation will continue to fail until the binding is fixed.

2. check-patch-compliance failure — Missing Link: tag. This is a mandatory fix for the PR commit message. Add the lore.kernel.org URL where this patch was posted upstream.

Recommendation: Fix the Link: tag immediately. For the dtb-check issue, coordinate with maintainers — either submit a binding fix patch first, or request that the binding be updated as part of reviewing this board enablement series.

[qswat-orbit-external]

Merge Check Failed: No CR Numbers Found

Error: No Change Request numbers were found.

Please add Change Request numbers to your pull request description in the format CRs-Fixed: 12345 or link GitHub issues that are associated with Change Requests.

[qswat-orbit-external]

Merge Check Failed: No CR Numbers Found

Error: No Change Request numbers were found.

Please add Change Request numbers to your pull request description in the format CRs-Fixed: 12345 or link GitHub issues that are associated with Change Requests.

[qswat-orbit-external]

Merge Check Failed: No CR Numbers Found

Error: No Change Request numbers were found.

Please add Change Request numbers to your pull request description in the format CRs-Fixed: 12345 or link GitHub issues that are associated with Change Requests.

[qlijarvis]

PR #829 — validate-patch

PR: #829

Verdict	Issues	Detailed Report
❌	0	Full report

Final Summary

1. Lore link present: No — no lore.kernel.org link found in commit message; no vendor prefix to indicate this is vendor-only
2. Lore link matches PR commits: N/A — no lore link to compare against
3. Upstream patch status: Unknown — no lore link provided; cannot determine if posted/accepted/rejected upstream
4. PR present in qcom-next/topics: Fail - 1/1 commit(s) are missing from both qcom-next and topics

Verdict: ❌ — click to expand

🔍 Patch Validation

PR: #829 — arm64: dts: qcom: qsc615-lyra-evk: Add support for QCS615 lyra evk board
Upstream commit: N/A
Verdict: ❌ FAIL

Commit Message

Check	Status	Note
Subject matches upstream	❌	No upstream source; missing vendor prefix (QCLINUX:/FROMLIST:/UPSTREAM:)
Body preserves rationale	⚠️	Describes what is added but not why or the submission status
Fixes tag present/correct	N/A	Not a fix
Authorship preserved	✅	Author is Qualcomm engineer with @qti.qualcomm.com email
Backport note (if applicable)	N/A	Not a backport

Diff

File	Status	Notes
arch/arm64/boot/dts/qcom/Makefile	⚠️	Adds talos-lyra-evk.dtb (note: subject says qsc615-lyra-evk but file is talos-lyra-evk)
arch/arm64/boot/dts/qcom/talos-lyra-evk.dts	⚠️	New 195-line device tree; no upstream attribution or lore link

Issues

1. Missing vendor prefix — Commit subject lacks a prefix to indicate origin/status. Expected one of:

   • QCLINUX: if this is vendor-only (not intended for upstream)
   • FROMLIST: if posted to mailing list (requires Link: tag)
   • UPSTREAM: if already merged upstream (requires Link: tag)

2. No lore.kernel.org link — No Link: tag in commit message. Per kernel submission guidelines and this tree's conventions, commits should reference their upstream posting or indicate vendor-only status.

3. Naming inconsistency — Subject line says "qsc615-lyra-evk" but the actual file is talos-lyra-evk.dts. The commit message body mentions "QCS615" while the model string in the DTS says "Qualcomm QCS615 IQ 615 EVK" and compatible is "qcom,talos-evk".

4. Missing from integration branches — Per integration_presence_report.md, this commit is not present in qcom-next or any topic branch. New device trees should typically land in a topic branch first before PR submission.

Verdict

Do not merge without addressing the following:

1. Add appropriate vendor prefix to subject line (most likely QCLINUX: if this is vendor-specific hardware)
2. If this was posted upstream, add Link: https://lore.kernel.org/r/<message-id> tag
3. Clarify the qsc615 vs talos naming discrepancy
4. Ensure the commit lands in the appropriate topic branch before integration

Final Summary

1. Lore link present: No — no lore.kernel.org link found in commit message; no vendor prefix to indicate this is vendor-only
2. Lore link matches PR commits: N/A — no lore link to compare against
3. Upstream patch status: Unknown — no lore link provided; cannot determine if posted/accepted/rejected upstream
4. PR present in qcom-next/topics: Fail — 1/1 commit(s) are missing from both qcom-next and topics (per integration_presence_report.md)

Deterministic Integration Presence

Integration Presence Report

This report is generated by Jarvis before validate-patch runs.
It is the authoritative source for whether PR changes are already present
in qcom-next or in the kernel topic branches.

Kernel repo: /local/mnt/workspace/sgaud/Qgenie/image_pipeline/kernel
qcom-next ref: a5cf3debd8c3c660711ad586ad4bb84e9ca42635
topics remote: topics -> https://github.com/qualcomm-linux/kernel-topics
topics fetch: fetched

Commit	Subject	qcom-next	topics	Final
1/1	[PATCH] arm64: dts: qcom: qsc615-lyra-evk: Add support for QCS615	missing - no subject, patch-id, or full tree-content match found	missing - no subject, patch-id, or full tree-content match found	missing

Final Status

overall_status: FAIL
present_commits: 0/1
partial_commits: 0/1
missing_commits: 1/1
topics_checked_for_commits: 1/1
final_summary: PR present in qcom-next/topics: Fail - 1/1 commit(s) are missing from both qcom-next and topics

[qlijarvis]

PR #829 — checker-log-analyzer

PR: #829
Checker run: https://github.com/qualcomm-linux/kernel-config/actions/runs/29732360018

Checker	Result	Summary
Checker	Result	Summary
checkpatch	✅	No style issues
dt-binding-check	⏭️	No binding changes
dtb-check	❌	Unevaluated properties in USB nodes
sparse-check	⏭️	No C/H file changes
check-uapi-headers	⏭️	No UAPI changes
check-patch-compliance	❌	Missing required subject prefix
tag-check	❌	Missing required subject prefix (mandatory for qcom-6.18.y)

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #829 - arm64: dts: qcom: qsc615-lyra-evk: Add support for QCS615 lyra evk board
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/29732360018
Target Branch: qcom-6.18.y

Checker	Result	Summary
checkpatch	✅	No style issues
dt-binding-check	⏭️	No binding changes
dtb-check	❌	Unevaluated properties in USB nodes
sparse-check	⏭️	No C/H file changes
check-uapi-headers	⏭️	No UAPI changes
check-patch-compliance	❌	Missing required subject prefix
tag-check	❌	Missing required subject prefix (mandatory for qcom-6.18.y)

---

❌ dtb-check

Root cause: The qcom,qcs615-dwc3 USB binding schema does not allow several properties that are present in the new talos-lyra-evk.dts file.

Failure details:

talos-lyra-evk.dtb: usb@a600000 (qcom,qcs615-dwc3): #address-cells: 1 was expected
talos-lyra-evk.dtb: usb@a600000 (qcom,qcs615-dwc3): #size-cells: 0 was expected
talos-lyra-evk.dtb: usb@a600000 (qcom,qcs615-dwc3): Unevaluated properties are not allowed 
  ('#address-cells', '#size-cells', 'dr_mode', 'phy-names', 'phys', 'ranges', 
   'snps,dis-u1-entry-quirk', 'snps,dis-u2-entry-quirk', 'snps,dis_enblslpm_quirk', 
   'snps,dis_u2_susphy_quirk', 'snps,dis_u3_susphy_quirk', 'snps,has-lpm-erratum', 
   'snps,hird-threshold', 'snps,usb3_lpm_capable' were unexpected)

talos-lyra-evk.dtb: usb@a800000 (qcom,qcs615-dwc3): #address-cells: 1 was expected
talos-lyra-evk.dtb: usb@a800000 (qcom,qcs615-dwc3): #size-cells: 0 was expected
talos-lyra-evk.dtb: usb@a800000 (qcom,qcs615-dwc3): Unevaluated properties are not allowed 
  ('#address-cells', '#size-cells', 'dr_mode', 'maximum-speed', 'phy-names', 'phys', 
   'ranges', 'snps,dis_enblslpm_quirk', 'snps,dis_u2_susphy_quirk', 'snps,dis_u3_susphy_quirk', 
   'snps,has-lpm-erratum', 'snps,hird-threshold' were unexpected)

Fix: The qcom,snps-dwc3.yaml binding schema needs to be updated to allow these properties. This is likely a pre-existing binding issue rather than a problem with the DTS file itself. The properties being flagged (#address-cells, #size-cells, ranges, dr_mode, phy-names, phys, and various snps,* quirk properties) are standard DWC3 USB controller properties.

Options:

1. Update the binding schema (recommended): Modify Documentation/devicetree/bindings/usb/qcom,snps-dwc3.yaml to set unevaluatedProperties: false to unevaluatedProperties: true or explicitly allow these properties via patternProperties or by including the proper parent schema references.

2. Remove unsupported properties from DTS: If these properties are not actually needed for the hardware, remove them from talos-lyra-evk.dts. However, this is unlikely since these are standard USB controller properties.

Reproduce locally:

make -j$(nproc) O=out defconfig
make -j$(nproc) O=out CHECK_DTBS=y arch/arm64/boot/dts/qcom/talos-lyra-evk.dtb

---

❌ check-patch-compliance

Root cause: The commit subject line does not start with a required prefix tag.

Failure details:

Checking commit: arm64: dts: qcom: qsc615-lyra-evk: Add support for QCS615 lyra evk board
Commit summary does not start with a required prefix

Fix: Add an appropriate prefix to the commit subject. Since this is a new board addition (not posted upstream), use one of these prefixes:

Prefix	When to use
FROMLIST:	If this patch has been posted to the upstream mailing list (lore.kernel.org)
UPSTREAM:	If this patch is already merged in Linus's mainline tree
QCLINUX:	If this is a vendor-only change with no upstream equivalent
PENDING:	If this is work-in-progress, not yet posted upstream

Recommended action:

git rebase -i HEAD~1   # mark commit as 'edit'
git commit --amend -m "QCLINUX: arm64: dts: qcom: qsc615-lyra-evk: Add support for QCS615 lyra evk board"
# (keep the rest of the commit message body unchanged)
git rebase --continue

Note: If you choose QCLINUX: or PENDING:, the check-patch-compliance checker will continue to fail because it only accepts upstream-linkable prefixes (FROMLIST:, FROMGIT:, UPSTREAM:, BACKPORT:). This is a known limitation of the checker for vendor-only commits.

Reproduce locally:

cd kernel-checkers
./check-patch-compliance.sh --kernel-src /path/to/kernel --base <base_sha> --head <head_sha>

---

❌ tag-check

Root cause: The PR targets branch qcom-6.18.y, which requires every commit to have a subject-line prefix tag. The commit is missing this required prefix.

Failure details:

Commit e6304c6b752c ("arm64: dts: qcom: qsc615-lyra-evk: Add support for QCS615 lyra evk board"): 
subject line does not start with a required prefix.

All branches except qcom-next and qcom-next-staging require one of:
FROMLIST: / FROMGIT: / UPSTREAM: / BACKPORT: / QCLINUX: / PENDING: / WORKAROUND:

Fix: Same as check-patch-compliance above — add an appropriate prefix to the commit subject.

Required prefixes:

• FROMLIST: — Patch posted to mailing list (lore.kernel.org)
• FROMGIT: — Patch taken from a maintainer git tree
• UPSTREAM: — Patch merged into Linus's mainline tree
• BACKPORT: — Upstream patch backported with modifications
• QCLINUX: — Vendor-only change with no upstream equivalent
• PENDING: — Work-in-progress, not yet posted upstream
• WORKAROUND: — Temporary fix not suitable for upstream

Reproduce locally:

git log --format="%H %s" <base>..<head> | grep -vE '^[a-f0-9]+ (FROMLIST|FROMGIT|UPSTREAM|BACKPORT|QCLINUX|PENDING|WORKAROUND):'

---

Verdict

2 blockers must be fixed before merge:

1. Subject prefix (affects both check-patch-compliance and tag-check): Add a required prefix tag (QCLINUX:, FROMLIST:, etc.) to the commit subject line.

2. dtb-check binding issue: The qcom,snps-dwc3.yaml binding schema needs to be updated to allow standard DWC3 USB properties, or the DTS file needs to be adjusted to match the current binding constraints. This appears to be a pre-existing binding limitation rather than an error in the new DTS file.

Recommended next steps:

1. Fix the commit subject prefix immediately (trivial fix via git commit --amend).
2. Investigate whether the dtb-check failure is a genuine binding gap or if the DTS properties need adjustment. Check other qcom,qcs615-dwc3 users in the tree for reference.