Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1382305
| From | Mark Brown <broonie@kernel.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH 1/5] max44000: Initial commit |
| Date | 2016-04-19 11:10 +0200 |
| Message-ID | <rpzPs-4lP-7@gated-at.bofh.it> (permalink) |
| References | (5 earlier) <roQpk-1k4-3@gated-at.bofh.it> <rpeL0-3XZ-11@gated-at.bofh.it> <rpgjM-5u2-13@gated-at.bofh.it> <rpgD8-5G5-9@gated-at.bofh.it> <rpnbA-2v9-7@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
On Mon, Apr 18, 2016 at 08:36:19PM +0100, Jonathan Cameron wrote: > On 18/04/16 13:34, Mark Brown wrote: > > Yes. I have to say that you are the first person I've encountered who > > has been confused by this, I'm not sure why you'd expect writes to be > > discarded. > It confused me too :) To my mind a classic cache optimization would be > to not write to the hardware if the value is already known to be as > desired. > Still, I guess it would add another check to identify which > registers you really wanted to hammer whatever vs which can be assumed > not to read the write is not worth the effort for this case that > inherently won't be hit that often. We'd also have to add another API for cases where someone explicitly wants to write the same thing to the hardware, you get things like latched "do it" bits in registers.
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: [PATCH 1/5] max44000: Initial commit Jonathan Cameron <jic23@kernel.org> - 2016-04-17 10:40 +0200
Re: [PATCH 1/5] max44000: Initial commit Mark Brown <broonie@kernel.org> - 2016-04-18 12:40 +0200
Re: [PATCH 1/5] max44000: Initial commit Lars-Peter Clausen <lars@metafoo.de> - 2016-04-18 13:00 +0200
Re: [PATCH 1/5] max44000: Initial commit Crestez Dan Leonard <leonard.crestez@intel.com> - 2016-04-18 14:20 +0200
Re: [PATCH 1/5] max44000: Initial commit Mark Brown <broonie@kernel.org> - 2016-04-18 14:40 +0200
Re: [PATCH 1/5] max44000: Initial commit Jonathan Cameron <jic23@kernel.org> - 2016-04-18 21:40 +0200
Re: [PATCH 1/5] max44000: Initial commit Mark Brown <broonie@kernel.org> - 2016-04-19 11:10 +0200
Re: [PATCH 1/5] max44000: Initial commit Jonathan Cameron <jic23@kernel.org> - 2016-04-18 21:40 +0200
csiph-web