-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
applications: nrf_desktop: define dts file for each build type #19033
applications: nrf_desktop: define dts file for each build type #19033
Conversation
You can find the documentation preview for this PR at this link. It will be updated about 10 minutes after the documentation build succeeds. Note: This comment is automatically posted by the Documentation Publish GitHub Action. |
CI InformationTo view the history of this post, clich the 'edited' button above Inputs:Sources:sdk-nrf: PR head: 6a966bce64fe0351559783a5a263d73dcc2d98ef more detailssdk-nrf:
Github labels
List of changed files detected by CI (17)
Outputs:ToolchainVersion: b77d8c1312 Test Spec & Results: ✅ Success; ❌ Failure; 🟠 Queued; 🟡 Progress; ◻️ Skipped;
|
ec488e7
to
9223c3b
Compare
@@ -209,6 +209,13 @@ nRF Desktop | |||
As a result, all :ref:`zephyr:nrf54h20dk_nrf54h20` configurations were migrated from the NVS settings backend to the ZMS settings backend. | |||
* The :ref:`zephyr:nrf54h20dk_nrf54h20` release configuration to enable the :ref:`nrf_desktop_watchdog`. | |||
* The configuration files of the :ref:`nrf_desktop_click_detector` (:file:`click_detector_def.h`) to allow using them also when Bluetooth LE peer control using a dedicated button (:ref:`CONFIG_DESKTOP_BLE_PEER_CONTROL <config_desktop_app_options>`) is disabled. | |||
* DTS description for board targets with a different DTS overlay file per build type to isolate the common configuration that is now defined in the :file:`app_common.dtsi` file. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
* DTS description for board targets with a different DTS overlay file per build type to isolate the common configuration that is now defined in the :file:`app_common.dtsi` file. | |
* The DTS description for board targets with a different DTS overlay file for each build type to isolate the common configuration that is now defined in the :file:`app_common.dtsi` file. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
corrected
Defined a dedicated DTS overlay file for each build type in the nRF Desktop application. Ref: NCSDK-13953 Signed-off-by: Kamil Piszczek <[email protected]>
9223c3b
to
6a966bc
Compare
}; | ||
}; | ||
|
||
&usbd { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
btw. This one could be defined per build type (you could align number of USB endpoints to needs of a given configuration). It would also be more consistent with the current approach - USB configuration is defined per build type.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, this could be improved in subsequent PRs. I just made sure that the generated zephyr.dts file is exactly the same after this change
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Improved in the following PR:
}; | ||
}; | ||
|
||
hid_dev_0: hid_dev_0 { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we want to define USB HID instances in common file or per build type?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well, I started from nRF54H20 and changed the approach for other targets. I forgot to align this as well, so I would say we can move it the build-type file.
This is up to discussion. We can easily imagine that the common part for each board target is different.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Improved in the following PR:
Defined a dedicated DTS overlay file for each build type in the nRF Desktop application.
Ref: NCSDK-13953