Linux Tegra architecture development
 help / color / mirror / Atom feed
From: Srirangan Madhavan <smadhavan@nvidia.com>
To: "Bence Csókás" <bence.csokas@arm.com>,
	"Mark Rutland" <mark.rutland@arm.com>,
	"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
	"Sudeep Holla" <sudeep.holla@kernel.org>,
	"Conor Dooley" <conor@kernel.org>,
	"Jonathan Cameron" <jic23@kernel.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>, Dan Williams <djbw@kernel.org>,
	Thierry Reding <treding@nvidia.com>,
	Jonathan Hunter <jonathanh@nvidia.com>,
	Souvik Chakravarty <Souvik.Chakravarty@arm.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH v2 2/2] cache: add SMCCC-backed cache invalidate provider
Date: Thu, 10 Sep 2026 01:26:25 -0700	[thread overview]
Message-ID: <29347083-d892-4539-99d7-020eeeb61151@nvidia.com> (raw)
In-Reply-To: <591e7ac9-310e-40f4-ab22-161d6ea8f487@arm.com>

On 7/2/26 6:04 AM, Bence Csókás wrote:
> 
> I'm reading the 1.7 H BET0 [1] version of the spec (released
> 2026-04-20), and I see some discrepancies. Not sure if I'm the one
> reading it wrong, or if you had a different version than me.
> 
> [1] https://developer.arm.com/documentation/den0028/h/?lang=en
> 
> Either way, thanks for posting this patch, I'm also looking forward to
> seeing it get merged!

Hi Bence, 
  

  
  
  

Thanks for the review, and apologies for the delayed response.

I have addressed the declaration ordering, preserved the final BUSY or 
RATE_LIMITED error after retry exhaustion, removed the redundant feature 
query for the mandatory ATTRIBUTES call, retained the full 64-bit X3 
rate-limit value, and removed the routine registration message.

The macro values are already aligned to the same column using tabs, so I
left those unchanged. I also kept the status-to-errno conversion local 
for now because the mapping reflects this provider's handling policy and 
there is currently no other caller that would justify a common SMCCC 
API. Please let me know if this works, else I'll move it.

I've sent out these changes in v3.



-- 
Regards,
Srirangan

  reply	other threads:[~2026-09-10  8:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-08 22:07 [PATCH v2 0/2] Add SMCCC cache clean/invalidate provider Srirangan Madhavan
2026-06-08 22:07 ` [PATCH v2 1/2] arm64: smccc: add cache clean/invalidate IDs and return codes Srirangan Madhavan
2026-06-08 22:07 ` [PATCH v2 2/2] cache: add SMCCC-backed cache invalidate provider Srirangan Madhavan
2026-07-02 13:04   ` Bence Csókás
2026-09-10  8:26     ` Srirangan Madhavan [this message]
2026-06-23 23:37 ` [PATCH v2 0/2] Add SMCCC cache clean/invalidate provider Srirangan Madhavan

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=29347083-d892-4539-99d7-020eeeb61151@nvidia.com \
    --to=smadhavan@nvidia.com \
    --cc=Souvik.Chakravarty@arm.com \
    --cc=bence.csokas@arm.com \
    --cc=catalin.marinas@arm.com \
    --cc=conor@kernel.org \
    --cc=djbw@kernel.org \
    --cc=jic23@kernel.org \
    --cc=jonathanh@nvidia.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=sudeep.holla@kernel.org \
    --cc=treding@nvidia.com \
    --cc=will@kernel.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