|
|
Subscribe / Log in / New account

Atomic mode setting design overview, part 2

Atomic mode setting design overview, part 2

Posted Sep 30, 2015 16:40 UTC (Wed) by alkadim (guest, #104623)
Parent article: Atomic mode setting design overview, part 2

Very nice read, Daniel, as the first article!

Again I propose some small fixes. Typo:

- requires a at least a few hundred
+ requires at least a few hundred

I take it that "the acquire context" is the context used by the
wait/wound algorithm for automatic lock acquisition. Then please
consider doing:

- after the initialization of the acquire context
+ after the initialization of the "acquire" context

...in the first usage of the phrase. And then:

- that, ... context — that must not be reinitialized
+ that, ... context — which must not be reinitialized

Nitpicking, consider:

- is the driver helper-library design
+ is the design of the driver helper library

- This allows drivers to keep some features only supported for legacy
- interfaces by keeping the code for old platforms around.
+ This allows drivers to continue supporting some features, though only
+ for legacy interfaces, by keeping the code for old platforms around.

Finally, note that in the first article the A in ADF was expanded as
"Atomic" not "Android".

Thanks!


to post comments


Copyright © 2025, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds