-
Notifications
You must be signed in to change notification settings - Fork 221
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
Create virtual peripherals for CPU control and radio clocks #1428
Conversation
This LGTM, just need to use peripheral ref on the constructors like @bjoernQ said. |
Sorry forgot on Friday, will get that updated shortly! |
pub struct CpuControl { | ||
_cpu_control: crate::system::CpuControl, | ||
pub struct CpuControl<'d> { | ||
_cpu_control: PeripheralRef<'d, CPU_CTRL>, |
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.
I think we don't really need to store it if we don't have any use for it
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.
LGTM - the virtual peripherals are really nice
I'm having second thoughts on merging this before the release, maybe we should wait so that we can tackle the remaining bits of the |
dbc0f98
to
7e78ce6
Compare
This should be fine to merge now, I think. |
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.
LGTM, thanks!
7e78ce6
to
a27eeff
Compare
A first step towards #1401, the changes get a little more involved from here on out so I figured I'd just split things up to keep it easy to review.
In short, I've created virtual
CPU_CTRL
andRADIO_CLK
peripherals, rather than manually defining the structs like we used to do when splitting.Happy to hear any feedback regarding peripheral names, I think these are reasonable though.