[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d7db3e4c3c4a40843d60fe92666d7f9e90df8801.camel@mediatek.com>
Date: Tue, 28 Sep 2021 09:21:41 +0800
From: Yong Wu <yong.wu@...iatek.com>
To: Arnd Bergmann <arnd@...nel.org>, Joerg Roedel <joro@...tes.org>,
"Will Deacon" <will@...nel.org>,
Matthias Brugger <matthias.bgg@...il.com>
CC: Arnd Bergmann <arnd@...db.de>,
Nathan Chancellor <nathan@...nel.org>,
Nick Desaulniers <ndesaulniers@...gle.com>,
Tomasz Figa <tfiga@...omium.org>,
Robin Murphy <robin.murphy@....com>,
<iommu@...ts.linux-foundation.org>,
<linux-mediatek@...ts.infradead.org>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-kernel@...r.kernel.org>, <llvm@...ts.linux.dev>
Subject: Re: [PATCH] iommu/mediatek: fix out-of-range warning with clang
On Mon, 2021-09-27 at 14:18 +0200, Arnd Bergmann wrote:
> From: Arnd Bergmann <arnd@...db.de>
>
> clang-14 notices that a comparison is never true when
> CONFIG_PHYS_ADDR_T_64BIT is disabled:
>
> drivers/iommu/mtk_iommu.c:553:34: error: result of comparison of
> constant 5368709120 with expression of type 'phys_addr_t' (aka
> 'unsigned int') is always false [-Werror,-Wtautological-constant-out-
> of-range-compare]
> if (dom->data->enable_4GB && pa >=
> MTK_IOMMU_4GB_MODE_REMAP_BASE)
> ~~
> ^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> Add an explicit check for the type of the variable to skip the check
> and the warning in that case.
>
> Fixes: b4dad40e4f35 ("iommu/mediatek: Adjust the PA for the 4GB
> Mode")
> Signed-off-by: Arnd Bergmann <arnd@...db.de>
Reviewed-by: Yong Wu <yong.wu@...iatek.com>
Thanks.
Powered by blists - more mailing lists