linux-kernel - Re: [PATCH 1/3] clocksource: rockchip: Make the driver more readability and compatible

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1595765.iIuZsGWCYG@diego>
Date:	Thu, 17 Sep 2015 11:43:44 +0200
From:	Heiko Stübner <heiko@...ech.de>
To:	Caesar Wang <caesar.upstream@...il.com>
Cc:	Daniel Lezcano <daniel.lezcano@...aro.org>,
	Catalin Marinas <catalin.marinas@....com>,
	Will Deacon <will.deacon@....com>,
	Caesar Wang <wxt@...k-chips.com>,
	linux-rockchip@...ts.infradead.org,
	Thomas Gleixner <tglx@...utronix.de>,
	linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 1/3] clocksource: rockchip: Make the driver more readability and compatible

Hi,

Am Donnerstag, 17. September 2015, 17:28:10 schrieb Caesar Wang:
> >> The problem was different semantics of dsb on btw arm32 and arm64,
> >> Here we can convert the dsb with insteading of dsb(sy).
> > 
> > What happens to ARM32 then ?
> 
> The dsb() is ok for ARM32, the ARM32/64 are OK if we can convert the
> dsb() to dsb(sy).
> I believe all drivers with 'dsb()' have same issue on ARM64 platform.

correct ... I read this up in the ARM docs 2 days ago too for something.

The "sy" param is the default, which you are allow to omit, so on arm32 dsb() 
and dsb(sy) are the same.


Heiko
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/