-
Notifications
You must be signed in to change notification settings - Fork 2k
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
cpu/lpc11u34: fixed ADC resolution selection #6959
Conversation
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.
Looks fine. I don't have a board with this CPU, but it looks right when I checked the manual for the CPU.
This CPU needs a bit of clean up with regards to magic numbers in the implementation, but that can be done in a separate PR.
Murdock2 is fine, @haukepetersen did you test this on actual hardware? |
nope, I don't have this HW, and if I remember correctly nobody in Berlin/HH/Paris does... |
- fixed selection of resolution - fixed result masking - fixed channel selection (and optimized it) - fixed clock prescaler calculation
e6ff0de
to
ae3f019
Compare
actually, by looking at the driver once more, I found it broken in many more ways (and it seems to have been broken from the beginning as I see it...). Hopefully all should be good now. As nobody seems to have a board with this CPU, is anyone willing to give an untested ACK (maybe after sharply comparing the changes done to the reference manual, page 385 ff?! |
@haukepetersen perhaps it is time to drop the support for this CPU, since nobody seem to have the board and there is little or no interest in the PRs related to it? |
I send a private mail to Paul to check if he is still able to maintain the platform, so let's wait for his reply before dropping anything... |
Got an answer a while ago: he will not be able to maintain the board in the near future and we is ok with removing the board for now. I propose the following: we merge this PR untested and remove the board in a next step, but by documenting it so it can be pulled back into master if a new maintainer is available. @gebart you ok with this? If yes -> press merge :-) |
fixes #5489 (or at least I hope so, don't have a board to test...)