[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BN8PR12MB3266393BD37EAABBF45D8AEFD3AD0@BN8PR12MB3266.namprd12.prod.outlook.com>
Date: Wed, 29 Apr 2020 06:19:55 +0000
From: Jose Abreu <Jose.Abreu@...opsys.com>
To: Eugeniy Paltsev <Eugeniy.Paltsev@...opsys.com>,
"linux-snps-arc@...ts.infradead.org"
<linux-snps-arc@...ts.infradead.org>,
Vineet Gupta <Vineet.Gupta1@...opsys.com>
CC: Alexey Brodkin <Alexey.Brodkin@...opsys.com>,
Eugeniy Paltsev <Eugeniy.Paltsev@...opsys.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Angelo Ribeiro <Angelo.Ribeiro@...opsys.com>
Subject: RE: [PATCH] ARC: guard dsp early init against non ARCv2
From: Eugeniy Paltsev <Eugeniy.Paltsev@...opsys.com>
Date: Apr/28/2020, 19:50:24 (UTC+00:00)
> As of today we guard early DSP init code with
> ARC_AUX_DSP_BUILD (0x7A) BCR check to verify that we have
> CPU with DSP configured. However that's not enough as in
> ARCv1 CPU the same BCR (0x7A) is used for checking MUL/MAC
> instructions presence.
>
> So, let's guard DSP early init against non ARCv2.
>
> Signed-off-by: Eugeniy Paltsev <Eugeniy.Paltsev@...opsys.com>
Reported-by: Angelo Ribeiro
<angelor@...opsys.com>
---
Thanks,
Jose Miguel Abreu
Powered by blists - more mailing lists