-
Notifications
You must be signed in to change notification settings - Fork 7.6k
drivers: hwinfo: litex: add warning and infos #89240
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
Open
maass-hamburg
wants to merge
1
commit into
zephyrproject-rtos:main
Choose a base branch
from
maass-hamburg:litex_hwinfo_warning
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+9
−1
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -191,7 +191,9 @@ config HWINFO_LITEX | |
depends on DT_HAS_LITEX_DNA0_ENABLED | ||
select HWINFO_HAS_DRIVER | ||
help | ||
Enable LiteX hwinfo driver | ||
Enable LiteX hwinfo driver. It does not return a unique device id. It is shared | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. same remark -- I understand you want to warn people but that KConfig can in theory be for more than just getting device ID. FWIW I think documenting this hardware limitation in the binding might make more sense. |
||
across all devices with the same bitstream. See litex/soc/cores/identifier.py in the | ||
LiteX repository for more information. | ||
|
||
config HWINFO_PSOC6 | ||
bool "Cypress PSOC 6 unique device ID" | ||
|
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.
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.
it's kind of weird to have it as a warning at this level -- there's several other things that this Kconfig being enabled potentially gives access to. In the future the driver might e.g. implement
hwinfo_get_reset_cause
and at this point warning people who couldn't care less about device ID seems odd.How about making it a
__WARN(...)
right in thez_impl_hwinfo_get_device_id
of the driver?