Re: [PATCH v2 05/19] PM / devfreq: tegra: Replace write memory barrier with the read barrier

On 19. 4. 16. 오후 10:57, Dmitry Osipenko wrote: > 16.04.2019 11:00, Chanwoo Choi пишет: >> Hi, >> >> On 19. 4. 15. 오후 11:54, Dmitry Osipenko wrote: >>> The write memory barrier isn't needed because the BUS buffer is flushed >>> by read after write that happens after the removed wmb(), we will also

Re: [PATCH v2 05/19] PM / devfreq: tegra: Replace write memory barrier with the read barrier

16.04.2019 11:00, Chanwoo Choi пишет: > Hi, > > On 19. 4. 15. 오후 11:54, Dmitry Osipenko wrote: >> The write memory barrier isn't needed because the BUS buffer is flushed >> by read after write that happens after the removed wmb(), we will also >> use readl() instead of the relaxed version to

Re: [PATCH v2 05/19] PM / devfreq: tegra: Replace write memory barrier with the read barrier

Hi, On 19. 4. 15. 오후 11:54, Dmitry Osipenko wrote: > The write memory barrier isn't needed because the BUS buffer is flushed > by read after write that happens after the removed wmb(), we will also > use readl() instead of the relaxed version to ensure that read is indeed > completed. > >

[PATCH v2 05/19] PM / devfreq: tegra: Replace write memory barrier with the read barrier

The write memory barrier isn't needed because the BUS buffer is flushed by read after write that happens after the removed wmb(), we will also use readl() instead of the relaxed version to ensure that read is indeed completed. Signed-off-by: Dmitry Osipenko --- drivers/devfreq/tegra-devfreq.c |