From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Akhil R <akhilrajeev@nvidia.com>
Cc: andi.shyti@kernel.org, digetx@gmail.com, jonathanh@nvidia.com,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-tegra@vger.kernel.org, thierry.reding@gmail.com,
wsa@kernel.org, kkartik@nvidia.com, ldewangan@nvidia.com,
smangipudi@nvidia.com
Subject: Re: [PATCH v13 5/6] i2c: tegra: Add support for SW mutex register
Date: Tue, 13 Jan 2026 16:42:33 +0100 [thread overview]
Message-ID: <aWZn6boSNd0Z4F1b@ninjato> (raw)
In-Reply-To: <20251118140620.549-6-akhilrajeev@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 1003 bytes --]
On Tue, Nov 18, 2025 at 07:36:19PM +0530, Akhil R wrote:
> From: Kartik Rajput <kkartik@nvidia.com>
>
> Add support for SW mutex register introduced in Tegra264 to provide
> an option to share the interface between multiple firmwares and/or
> VMs. This involves following steps:
>
> - A firmware/OS writes its unique ID to the mutex REQUEST field.
> - Ownership is established when reading the GRANT field returns the
> same ID.
> - If GRANT shows a different non-zero ID, the firmware/OS retries
> until timeout.
> - After completing access, it releases the mutex by writing 0.
>
> However, the hardware does not ensure any protection based on the
> values. The driver/firmware should honor the peer who already holds
> the mutex.
>
> Signed-off-by: Kartik Rajput <kkartik@nvidia.com>
> Signed-off-by: Akhil R <akhilrajeev@nvidia.com>
> Reviewed-by: Jon Hunter <jonathanh@nvidia.com>
> Acked-by: Thierry Reding <treding@nvidia.com>
Applied to for-next, thanks!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-01-13 15:42 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-18 14:06 [PATCH v13 0/6] Updates for Tegra264 and Tegra256 Akhil R
2025-11-18 14:06 ` [PATCH v13 1/6] i2c: tegra: Do not configure DMA if not supported Akhil R
2025-11-27 9:29 ` Thierry Reding
2026-01-13 15:42 ` Wolfram Sang
2025-11-18 14:06 ` [PATCH v13 2/6] i2c: tegra: Use separate variables for fast and fastplus Akhil R
2025-11-27 9:30 ` Thierry Reding
2026-01-13 15:42 ` Wolfram Sang
2025-11-18 14:06 ` [PATCH v13 3/6] i2c: tegra: Update Tegra256 timing parameters Akhil R
2025-11-27 9:31 ` Thierry Reding
2026-01-13 15:42 ` Wolfram Sang
2025-11-18 14:06 ` [PATCH v13 4/6] i2c: tegra: Add HS mode support Akhil R
2025-11-18 14:19 ` Jon Hunter
2025-11-27 9:34 ` Thierry Reding
2026-01-13 15:42 ` Wolfram Sang
2025-11-18 14:06 ` [PATCH v13 5/6] i2c: tegra: Add support for SW mutex register Akhil R
2025-11-27 9:36 ` Thierry Reding
2026-01-13 15:42 ` Wolfram Sang [this message]
2025-11-18 14:06 ` [PATCH v13 6/6] i2c: tegra: Add Tegra264 support Akhil R
2025-11-27 9:36 ` Thierry Reding
2026-01-13 15:42 ` Wolfram Sang
2025-11-27 9:37 ` [PATCH v13 0/6] Updates for Tegra264 and Tegra256 Thierry Reding
2025-12-19 9:09 ` Akhil R
2026-01-06 6:28 ` Akhil R
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=aWZn6boSNd0Z4F1b@ninjato \
--to=wsa+renesas@sang-engineering.com \
--cc=akhilrajeev@nvidia.com \
--cc=andi.shyti@kernel.org \
--cc=digetx@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=kkartik@nvidia.com \
--cc=ldewangan@nvidia.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=smangipudi@nvidia.com \
--cc=thierry.reding@gmail.com \
--cc=wsa@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 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.