-
Notifications
You must be signed in to change notification settings - Fork 1.8k
drivers:dac:ad5710r: Add support for AD5710r #2784
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
Conversation
305896d to
f137700
Compare
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 good overall. a commit with documentation should be added.
drivers/dac/ad5710r/ad5710r.c
Outdated
|
|
||
| short_instr = data->spi_cfg->short_instr; | ||
| sign = desc->spi_cfg.addr_asc ? 1 : -1; | ||
| inc = 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.
these should be initialized at declaration. reduces code duplication.
| return ret; | ||
|
|
||
| desc->range = range_sel; | ||
| return 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.
preffered an empty line before the last return of the function. check all occurences.
Added support for AD5710R DAC driver. Signed-off-by: SGudla <Saikiran.Gudla@analog.com>
61ececb to
71527b9
Compare
Change log: Addressed review comments and added doc |
06ffcc1 to
f88cf20
Compare
Add rst documentation file for AD5710r driver. Signed-off-by: SGudla <Saikiran.Gudla@analog.com>
f88cf20 to
ec12c39
Compare
|
@amiclaus, I've addressed review comments and added doc. May I know if this is good to be merged now? |
Added support for AD5710R DAC driver.
Pull Request Description
Please replace this with a detailed description and motivation of the changes.
You can tick the checkboxes below with an 'x' between square brackets or just check them after publishing the PR.
If this PR contains a breaking change, list dependent PRs and try to push all related PRs at the same time.
PR Type
PR Checklist