All of lore.kernel.org
 help / color / mirror / Atom feed
From: Angelo Ribeiro <Angelo.Ribeiro@synopsys.com>
To: Jose Abreu <Jose.Abreu@synopsys.com>,
	Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>,
	"linux-snps-arc@lists.infradead.org" 
	<linux-snps-arc@lists.infradead.org>,
	Vineet Gupta <Vineet.Gupta1@synopsys.com>
Cc: Alexey Brodkin <Alexey.Brodkin@synopsys.com>,
	Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] ARC: guard dsp early init against non ARCv2
Date: Wed, 29 Apr 2020 10:03:21 +0000	[thread overview]
Message-ID: <CH2PR12MB3782E5561AB98EDA1E350C02CBAD0@CH2PR12MB3782.namprd12.prod.outlook.com> (raw)
In-Reply-To: <BN8PR12MB3266393BD37EAABBF45D8AEFD3AD0@BN8PR12MB3266.namprd12.prod.outlook.com>

Hi Eugeniy,

Tested okay on a ARCv1.

Thanks
Angelo

Tested-by: Angelo Ribeiro <angelo.ribeiro@synopsys.com>

From: Jose Abreu <joabreu@synopsys.com>
Date: Wed, Apr 29, 2020 at 07:19:55

> From: Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.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@synopsys.com>
> 
> Reported-by: Angelo Ribeiro 
> <angelor@synopsys.com>
> 
> ---
> Thanks,
> Jose Miguel Abreu



WARNING: multiple messages have this Message-ID (diff)
From: Angelo Ribeiro <Angelo.Ribeiro@synopsys.com>
To: Jose Abreu <Jose.Abreu@synopsys.com>,
	Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>,
	"linux-snps-arc@lists.infradead.org"
	<linux-snps-arc@lists.infradead.org>,
	Vineet Gupta <Vineet.Gupta1@synopsys.com>
Cc: Alexey Brodkin <Alexey.Brodkin@synopsys.com>,
	Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] ARC: guard dsp early init against non ARCv2
Date: Wed, 29 Apr 2020 10:03:21 +0000	[thread overview]
Message-ID: <CH2PR12MB3782E5561AB98EDA1E350C02CBAD0@CH2PR12MB3782.namprd12.prod.outlook.com> (raw)
In-Reply-To: <BN8PR12MB3266393BD37EAABBF45D8AEFD3AD0@BN8PR12MB3266.namprd12.prod.outlook.com>

Hi Eugeniy,

Tested okay on a ARCv1.

Thanks
Angelo

Tested-by: Angelo Ribeiro <angelo.ribeiro@synopsys.com>

From: Jose Abreu <joabreu@synopsys.com>
Date: Wed, Apr 29, 2020 at 07:19:55

> From: Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.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@synopsys.com>
> 
> Reported-by: Angelo Ribeiro 
> <angelor@synopsys.com>
> 
> ---
> Thanks,
> Jose Miguel Abreu



_______________________________________________
linux-snps-arc mailing list
linux-snps-arc@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-snps-arc

  reply	other threads:[~2020-04-29 10:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-28 18:50 [PATCH] ARC: guard dsp early init against non ARCv2 Eugeniy Paltsev
2020-04-28 18:50 ` Eugeniy Paltsev
2020-04-28 19:46 ` Vineet Gupta
2020-04-28 19:46   ` Vineet Gupta
2020-04-29 17:12   ` Eugeniy Paltsev
2020-04-29 17:12     ` Eugeniy Paltsev
2020-04-29 18:50     ` Vineet Gupta
2020-04-29 18:50       ` Vineet Gupta
2020-04-29  6:19 ` Jose Abreu
2020-04-29  6:19   ` Jose Abreu
2020-04-29 10:03   ` Angelo Ribeiro [this message]
2020-04-29 10:03     ` Angelo Ribeiro

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CH2PR12MB3782E5561AB98EDA1E350C02CBAD0@CH2PR12MB3782.namprd12.prod.outlook.com \
    --to=angelo.ribeiro@synopsys.com \
    --cc=Alexey.Brodkin@synopsys.com \
    --cc=Eugeniy.Paltsev@synopsys.com \
    --cc=Jose.Abreu@synopsys.com \
    --cc=Vineet.Gupta1@synopsys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-snps-arc@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.