Skip to content

Enable support for IQ-8275-AC STARTER EVK board#1873

Open
nkumarsi wants to merge 2 commits into
qualcomm-linux:masterfrom
nkumarsi:monaco-evk-ac
Open

Enable support for IQ-8275-AC STARTER EVK board#1873
nkumarsi wants to merge 2 commits into
qualcomm-linux:masterfrom
nkumarsi:monaco-evk-ac

Conversation

@nkumarsi
Copy link
Copy Markdown
Contributor

@nkumarsi nkumarsi commented Apr 3, 2026

Add IQ-8275-AC STARTER EVK support to the machine IQ-8275 and add the corresponding FIT compatible mapping.

The IQ-8275-AC STARTER is a hardware variant of the IQ-8275 (monaco) platform
with a reduced PMIC configuration (2x PM8654AU), compared to the
IQ-8275 EVK which uses a 4-PMIC setup. The rest of the hardware
peripherals are largely identical and shared across both variants.

Since the IQ-8275-AC STARTER EVK belongs to the same platform family and reuses
the same core hardware description, it is added under the existing IQ-8275 machine.

Changes:

  • Add monaco-ac EVK DTB to LINUX_QCOM_KERNEL_DEVICETREE to the IQ-8275 machine

  • Add FIT DTB compatible string for monaco-ac-evk.dtb to ensure the
    correct DTB is selected during boot

Comment thread conf/machine/iq-8275-evk.conf Outdated
@@ -13,6 +13,7 @@ KERNEL_DEVICETREE ?= " \

# These DTs are not upstreamed and currently exist only in linux-qcom kernels
LINUX_QCOM_KERNEL_DEVICETREE ?= " \
qcom/monaco-evk-ac-sku.dtb \
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please wait for the name to be at least agreen upon upstream. Not to mention that your commit message doesn't explain, why do we want it, why is it different from the normal monaco-evk.dtb and why it's being enabled as a part of IQ-8275-EVK machine.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hello Dmitry,
Had raised this PR as draft PR just for validation and sharing with other teams for internal testing.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Commit message is still not saying why you are adding this as part of monaco-evk (iq-8275-evk).

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Acknowledge, updated commit message.

@nkumarsi nkumarsi changed the title Enable support for monaco-evk ac SKU Enable support for monaco-ac EVK board Apr 14, 2026
@nkumarsi nkumarsi marked this pull request as ready for review April 14, 2026 21:35
@ricardosalveti
Copy link
Copy Markdown
Contributor

What is AC here?

@nkumarsi
Copy link
Copy Markdown
Contributor Author

What is AC here?

Hi @ricardosalveti ,

Here, ac refers to QCS8300-AC SKU, a variant of monaco SoC (QCS8300) with 20 TOPS NPU capability and a simplified two-PMIC power delivery network (2x PM8650AU), as opposed to the QCS8300-AA SKU used in the existing monaco-evk.

@ricardosalveti
Copy link
Copy Markdown
Contributor

What is AC here?

Hi @ricardosalveti ,

Here, ac refers to QCS8300-AC SKU, a variant of monaco SoC (QCS8300) with 20 TOPS NPU capability and a simplified two-PMIC power delivery network (2x PM8650AU), as opposed to the QCS8300-AA SKU used in the existing monaco-evk.

Please add this to the commit message.

@nkumarsi
Copy link
Copy Markdown
Contributor Author

What is AC here?

Hi @ricardosalveti ,
Here, ac refers to QCS8300-AC SKU, a variant of monaco SoC (QCS8300) with 20 TOPS NPU capability and a simplified two-PMIC power delivery network (2x PM8650AU), as opposed to the QCS8300-AA SKU used in the existing monaco-evk.

Please add this to the commit message.

Thank you for the review . updated the commit message.

@ricardosalveti
Copy link
Copy Markdown
Contributor

Please rebase.

@nkumarsi
Copy link
Copy Markdown
Contributor Author

Please rebase

Done rebased it.

@nkumarsi
Copy link
Copy Markdown
Contributor Author

The BT WA changes were not carried in the current promoted tag - and it's was missed to add it in the refactored change for monaco-evk and monaco-ac-evk - hence moving this PR to draft PR for now until proper clean changes are bought in ...

The corresponding kernel promotion of the same also will be reverted ...

@github-actions
Copy link
Copy Markdown

This pull request has been marked as stale due to 30 days of inactivity. To prevent automatic closure in 5 days, remove the stale label or add a comment. You can reopen a closed pull request at any time.

@github-actions github-actions Bot added the Stale label May 18, 2026
@nkumarsi nkumarsi marked this pull request as ready for review May 19, 2026 11:08
@nkumarsi
Copy link
Copy Markdown
Contributor Author

Hi @ricardosalveti , could you please help review this PR?
as monaco-ac-evk dt support merged on kernel tag : qcom-6.18.y-20260515.

@github-actions
Copy link
Copy Markdown

Test run workflow

Test jobs for commit 2ce9795

qcom-distro
Pass: 264 | Fail: 1 | Total: 285
nodistro
Pass: 9 | Fail: 0 | Total: 9
qcom-distro_linux-qcom-6.18
Pass: 217 | Fail: 3 | Total: 238

@nkumarsi
Copy link
Copy Markdown
Contributor Author

It definitely should be IQ-8275, not iq-8275. What is the correct capitalization for monaco-ac?

acknowledge , updated iq-8275 to IQ-8275 . i think monaco-ac is in small capitalization because it refers to a device tree component.

@nkumarsi
Copy link
Copy Markdown
Contributor Author

You can't add 'under the machine'. 'to the machine' sounds a bit better.

Acknowledged.

@lumag
Copy link
Copy Markdown
Contributor

lumag commented May 21, 2026

It definitely should be IQ-8275, not iq-8275. What is the correct capitalization for monaco-ac?

acknowledge , updated iq-8275 to IQ-8275 . i think monaco-ac is in small capitalization because it refers to a device tree component.

What is the marketing name for the board? E.g. iq-8275-evk is a Yocto's machine name, but IQ-8275 EVK is a marketing name (IIRC).

@nkumarsi
Copy link
Copy Markdown
Contributor Author

It definitely should be IQ-8275, not iq-8275. What is the correct capitalization for monaco-ac?

acknowledge , updated iq-8275 to IQ-8275 . i think monaco-ac is in small capitalization because it refers to a device tree component.

What is the marketing name for the board? E.g. iq-8275-evk is a Yocto's machine name, but IQ-8275 EVK is a marketing name (IIRC).

Marketing name for the monaco-ac board is the same as IQ-8275 EVK.

@lumag
Copy link
Copy Markdown
Contributor

lumag commented May 21, 2026

Marketing name for the monaco-ac board is the same as IQ-8275 EVK.

How does one distinguish, which one is it buying or working with? Having the same marketing name for two different boards is a disaster.

@nkumarsi
Copy link
Copy Markdown
Contributor Author

Marketing name for the monaco-ac board is the same as IQ-8275 EVK.

How does one distinguish, which one is it buying or working with? Having the same marketing name for two different boards is a disaster.

monaco-ac (2*PMIC) is only for licenced customers. Not for developers.

@lumag
Copy link
Copy Markdown
Contributor

lumag commented May 21, 2026

monaco-ac (2*PMIC) is only for licenced customers. Not for developers.

What does this change? The customer writes to us about the problem with the IQ-8275 EVK. Which board does it concern?

@github-actions
Copy link
Copy Markdown

Test run workflow

Test jobs for commit 67b9d45

qcom-distro
Pass: 272 | Fail: 1 | Total: 291
nodistro
Pass: 9 | Fail: 0 | Total: 9
qcom-distro_linux-qcom-6.18
Pass: 204 | Fail: 1 | Total: 228

@umang-chheda
Copy link
Copy Markdown
Contributor

What does this change? The customer writes to us about the problem with the IQ-8275 EVK. Which board does it concern?

@lumag -
while we are checking with marketing team on this ...

I believe customers can know the board variant via CDT and/or DT model string as well - Just checking if a different marketing name would be needed? As this is intended only for licensed customers....

What are your thoughts on the same ?

@lumag
Copy link
Copy Markdown
Contributor

lumag commented May 25, 2026

What does this change? The customer writes to us about the problem with the IQ-8275 EVK. Which board does it concern?

@lumag - while we are checking with marketing team on this ...

I believe customers can know the board variant via CDT and/or DT model string as well - Just checking if a different marketing name would be needed? As this is intended only for licensed customers....

What are your thoughts on the same ?

I already shared them: each board should have a unique name,

@akdwived-dev
Copy link
Copy Markdown

What does this change? The customer writes to us about the problem with the IQ-8275 EVK. Which board does it concern?

@lumag - while we are checking with marketing team on this ...
I believe customers can know the board variant via CDT and/or DT model string as well - Just checking if a different marketing name would be needed? As this is intended only for licensed customers....
What are your thoughts on the same ?

I already shared them: each board should have a unique name,

@lumag Here Carrier board is EVK and EVK design and pin compatibility remain same for both the SKU and between 2XPMIC and 4XPMIC variant/SKU it is SoC Daughter card which is changing, and we have Marketing name only as per carrier board not as Per SoC's SKUs.

@lumag
Copy link
Copy Markdown
Contributor

lumag commented May 26, 2026

Carrier board doesn't define the device. Again, which board is affected if the customer reports and error happening with the 'IQ-8275 EVK'?

@akdwived-dev
Copy link
Copy Markdown

Carrier board doesn't define the device. Again, which board is affected if the customer reports and error happening with the 'IQ-8275 EVK'?

Marketing Team is not averse of using IQ-8275-AC EVK for 2XPMIC SKU.

@lumag
Copy link
Copy Markdown
Contributor

lumag commented May 26, 2026

Carrier board doesn't define the device. Again, which board is affected if the customer reports and error happening with the 'IQ-8275 EVK'?

Marketing Team is not averse of using IQ-8275-AC EVK for 2XPMIC SKU.

Then I think it should be settled this way. Please update the commit message.

@nkumarsi
Copy link
Copy Markdown
Contributor Author

Carrier board doesn't define the device. Again, which board is affected if the customer reports and error happening with the 'IQ-8275 EVK'?

Marketing Team is not averse of using IQ-8275-AC EVK for 2XPMIC SKU.

Then I think it should be settled this way. Please update the commit message.

Hi @lumag , Marketing team suggested using IQ-8275-ac-starter-evk for RB4 2PMIC board. can we update commit text with same ?

@lumag
Copy link
Copy Markdown
Contributor

lumag commented May 28, 2026

Carrier board doesn't define the device. Again, which board is affected if the customer reports and error happening with the 'IQ-8275 EVK'?

Marketing Team is not averse of using IQ-8275-AC EVK for 2XPMIC SKU.

Then I think it should be settled this way. Please update the commit message.

Hi @lumag , Marketing team suggested using IQ-8275-ac-starter-evk for RB4 2PMIC board. can we update commit text with same ?

What is 'starter'? Also, why 'evk' is now lowercase and squashed to the name?

@umang-chheda
Copy link
Copy Markdown
Contributor

umang-chheda commented May 28, 2026

Carrier board doesn't define the device. Again, which board is affected if the customer reports and error happening with the 'IQ-8275 EVK'?

Marketing Team is not averse of using IQ-8275-AC EVK for 2XPMIC SKU.

Then I think it should be settled this way. Please update the commit message.

Hi @lumag , Marketing team suggested using IQ-8275-ac-starter-evk for RB4 2PMIC board. can we update commit text with same ?

What is 'starter'? Also, why 'evk' is now lowercase and squashed to the name?

Hi @lumag , we have two more new RB4 EVK variants in the pipeline (of both 4 PMIC and 2 PMIC variants). To clearly differentiate between them, the marketing team has suggested naming this 2 PMIC RB4 AC variant as mentioned above. With capitalization applied, can we name it IQ-8275-AC-STARTER-EVK?

@lumag
Copy link
Copy Markdown
Contributor

lumag commented May 29, 2026

@umang-chheda what is so "starter" in it? What would be the name for the two other EVKs?

@umang-chheda
Copy link
Copy Markdown
Contributor

umang-chheda commented May 31, 2026

@umang-chheda what is so "starter" in it?

@lumag - This version of RB4 - AC variant is an entry level developer hardware kit designed to minimize the cost and to help developer to get started with - hence the name "starter" in it.

"starter" here is added - to differentiate b/w the advanced feature's EVK which might come in near future.

What would be the name for the two other EVKs?

Currently the name of other two planned EVKs cannot be disclosed.

@lumag
Copy link
Copy Markdown
Contributor

lumag commented May 31, 2026

Okay , thanks a lot for all the explanations! Could you please rebase on the current master and use the established name in the commit messages.

@nkumarsi nkumarsi changed the title Enable support for monaco-ac EVK board Enable support for IQ-8275-AC STARTER EVK board Jun 1, 2026
@nkumarsi
Copy link
Copy Markdown
Contributor Author

nkumarsi commented Jun 1, 2026

Okay , thanks a lot for all the explanations! Could you please rebase on the current master and use the established name in the commit messages.

Sure, thank you for the feedback. I’ve rebased and updated the commit message.

FIT_DTB_COMPATIBLE[qcom_qcs8275-iot] = \
"monaco-evk monaco-evk-camera-imx577"

FIT_DTB_COMPATIBLE[qcom_qcs8275-iot-subtype0] = "monaco-ac-evk monaco-evk-camera-imx577"
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since you added the dtb to LINUX_QCOM_KERNEL_DEVICETREE, change https://github.com/qualcomm-linux/meta-qcom/blob/master/conf/machine/include/fit-dtb-compatible-linux-qcom.inc instead.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Acknowledged

@ricardosalveti
Copy link
Copy Markdown
Contributor

IQ-8275-AC-STARTER-EVK: Add monaco-ac EVK DTB to LINUX_QCOM_KERNEL_DEVICETREE

Change to iq-8275-evk: add support for IQ-8275-AC-STARTER-EVK or similar, as you are changing iq-8275-evk.

nkumarsi added 2 commits June 1, 2026 17:50
Include monaco-ac-evk.dtb in LINUX_QCOM_KERNEL_DEVICETREE to
support the IQ-8275-AC STARTER EVK.

The IQ-8275-AC STARTER EVK is a hardware variant of the IQ-8275 (monaco)
platform with a reduced PMIC configuration (2x PM8654AU), compared to
the IQ-8275 EVK which uses a 4-PMIC setup (Monaco-AA SKU). Apart from
this difference, the rest of the hardware peripherals are largely identical
and shared across both variants.

Since the IQ-8275-AC STARTER EVK belongs to the same platform family
and reuses the same core hardware description, it is added to the machine
IQ-8275. Add the corresponding FIT compatible mapping to distinguish the
variant and ensure the correct DTB is selected during boot.

Signed-off-by: Nirmesh Kumar Singh <nirmesh.singh@oss.qualcomm.com>
Add compatible string mapping for monaco-ac-evk.dtb to ensure the
correct DTB is selected during boot for the IQ-8275-AC STARTER EVK.

Signed-off-by: Nirmesh Kumar Singh <nirmesh.singh@oss.qualcomm.com>
@nkumarsi
Copy link
Copy Markdown
Contributor Author

nkumarsi commented Jun 1, 2026

IQ-8275-AC-STARTER-EVK: Add monaco-ac EVK DTB to LINUX_QCOM_KERNEL_DEVICETREE

Change to iq-8275-evk: add support for IQ-8275-AC-STARTER-EVK or similar, as you are changing iq-8275-evk.

Acknowledged.

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.

5 participants