mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: joro@8bytes.org,
	Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Cc: catalin.marinas@arm.com, kernel-team@android.com,
	Will Deacon <will@kernel.org>,
	linux-kernel@vger.kernel.org, steev@kali.org,
	iommu@lists.linux.dev, johan+linaro@kernel.org,
	andersson@kernel.org, linux-arm-kernel@lists.infradead.org,
	robin.murphy@arm.com
Subject: Re: [PATCH v5] iommu/arm-smmu-qcom: Limit the SMR groups to 128
Date: Mon, 27 Mar 2023 13:52:01 +0100	[thread overview]
Message-ID: <167991987524.1305084.466646756285487652.b4-ty@kernel.org> (raw)
In-Reply-To: <20230327080029.11584-1-manivannan.sadhasivam@linaro.org>

On Mon, 27 Mar 2023 13:30:29 +0530, Manivannan Sadhasivam wrote:
> Some platforms support more than 128 stream matching groups than what is
> defined by the ARM SMMU architecture specification. But due to some unknown
> reasons, those additional groups don't exhibit the same behavior as the
> architecture supported ones.
> 
> For instance, the additional groups will not detect the quirky behavior of
> some firmware versions intercepting writes to S2CR register, thus skipping
> the quirk implemented in the driver and causing boot crash.
> 
> [...]

Applied to will (for-joerg/arm-smmu/updates), thanks!

[1/1] iommu/arm-smmu-qcom: Limit the SMR groups to 128
      https://git.kernel.org/will/c/122611347326 

Cheers,
-- 
Will

https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev

  reply	other threads:[~2023-03-27 12:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-27  8:00 Manivannan Sadhasivam
2023-03-27 12:52 ` Will Deacon [this message]
2023-03-30  5:41   ` Manivannan Sadhasivam
2023-03-30 15:06     ` 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=167991987524.1305084.466646756285487652.b4-ty@kernel.org \
    --to=will@kernel.org \
    --cc=andersson@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=iommu@lists.linux.dev \
    --cc=johan+linaro@kernel.org \
    --cc=joro@8bytes.org \
    --cc=kernel-team@android.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=robin.murphy@arm.com \
    --cc=steev@kali.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®