All of lore.kernel.org
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
	Marc Zyngier <maz@kernel.org>,
	Suzuki K Poulose <suzuki.poulose@arm.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Douglas Anderson <dianders@chromium.org>,
	Stephen Boyd <swboyd@chromium.org>,
	Andre Przywara <andre.przywara@arm.com>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-arm-msm@vger.kernel.org,
	Jeffrey Hugo <jhugo@codeaurora.org>
Subject: Re: [PATCH 3/3] arm64: Add KRYO4XX silver CPU cores to erratum list 1530923 and 1024718
Date: Fri, 3 Jul 2020 16:38:24 +0100	[thread overview]
Message-ID: <20200703153824.GA19327@willie-the-truck> (raw)
In-Reply-To: <7335e7fa1303a56a5e60339ed0c5d619@codeaurora.org>

On Fri, Jul 03, 2020 at 08:04:04PM +0530, Sai Prakash Ranjan wrote:
> On 2020-07-03 19:25, Will Deacon wrote:
> > On Tue, Jun 30, 2020 at 11:30:55PM +0530, Sai Prakash Ranjan wrote:
> > > KRYO4XX silver/LITTLE CPU cores with revision r1p0 are affected by
> > > erratum 1530923 and 1024718, so add them to the respective list.
> > > The variant and revision bits are implementation defined and are
> > > different from the their Cortex CPU counterparts on which they are
> > > based on, i.e., r1p0 is equivalent to rdpe.
> > 
> > So just to confirm, revisions prior to rdpe are unaffected, or do those
> > parts simply not exist?
> > 
> 
> There is one revision prior to this r0p1(r7pc) which has a different part
> number and are used in v1 of SoCs which are limited to only internal test
> platforms in the early stages of bringup and not used in actual devices out
> there, so I did not add it to the list but they are affected. Plus we would
> need to add another MIDR_QCOM_KRYO_4XX_SILVER_V1 if we are supporting them
> which I thought was not worth it when devices with those CPUs are not
> available.

Thanks, just wanted to make sure. Sounds like we can safely assume those
parts don't exist.

Will

WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will@kernel.org>
To: Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
	Suzuki K Poulose <suzuki.poulose@arm.com>,
	Jeffrey Hugo <jhugo@codeaurora.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	linux-arm-msm@vger.kernel.org,
	Douglas Anderson <dianders@chromium.org>,
	Stephen Boyd <swboyd@chromium.org>,
	Andre Przywara <andre.przywara@arm.com>,
	linux-arm-kernel@lists.infradead.org,
	Marc Zyngier <maz@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] arm64: Add KRYO4XX silver CPU cores to erratum list 1530923 and 1024718
Date: Fri, 3 Jul 2020 16:38:24 +0100	[thread overview]
Message-ID: <20200703153824.GA19327@willie-the-truck> (raw)
In-Reply-To: <7335e7fa1303a56a5e60339ed0c5d619@codeaurora.org>

On Fri, Jul 03, 2020 at 08:04:04PM +0530, Sai Prakash Ranjan wrote:
> On 2020-07-03 19:25, Will Deacon wrote:
> > On Tue, Jun 30, 2020 at 11:30:55PM +0530, Sai Prakash Ranjan wrote:
> > > KRYO4XX silver/LITTLE CPU cores with revision r1p0 are affected by
> > > erratum 1530923 and 1024718, so add them to the respective list.
> > > The variant and revision bits are implementation defined and are
> > > different from the their Cortex CPU counterparts on which they are
> > > based on, i.e., r1p0 is equivalent to rdpe.
> > 
> > So just to confirm, revisions prior to rdpe are unaffected, or do those
> > parts simply not exist?
> > 
> 
> There is one revision prior to this r0p1(r7pc) which has a different part
> number and are used in v1 of SoCs which are limited to only internal test
> platforms in the early stages of bringup and not used in actual devices out
> there, so I did not add it to the list but they are affected. Plus we would
> need to add another MIDR_QCOM_KRYO_4XX_SILVER_V1 if we are supporting them
> which I thought was not worth it when devices with those CPUs are not
> available.

Thanks, just wanted to make sure. Sounds like we can safely assume those
parts don't exist.

Will

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2020-07-03 15:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-03 14:34 [PATCH 3/3] arm64: Add KRYO4XX silver CPU cores to erratum list 1530923 and 1024718 Sai Prakash Ranjan
2020-07-03 15:38 ` Will Deacon [this message]
2020-07-03 15:38   ` Will Deacon
  -- strict thread matches above, loose matches on Subject: below --
2020-06-30 18:00 [PATCH 0/3] Add Kryo4xx gold and silver cores to applicable errata list Sai Prakash Ranjan
2020-06-30 18:00 ` [PATCH 3/3] arm64: Add KRYO4XX silver CPU cores to erratum list 1530923 and 1024718 Sai Prakash Ranjan
2020-06-30 18:00   ` Sai Prakash Ranjan
2020-07-03 13:55   ` Will Deacon
2020-07-03 13:55     ` Will Deacon

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=20200703153824.GA19327@willie-the-truck \
    --to=will@kernel.org \
    --cc=andre.przywara@arm.com \
    --cc=catalin.marinas@arm.com \
    --cc=dianders@chromium.org \
    --cc=jhugo@codeaurora.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=maz@kernel.org \
    --cc=saiprakash.ranjan@codeaurora.org \
    --cc=suzuki.poulose@arm.com \
    --cc=swboyd@chromium.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.