From: Jon Hunter <jonathanh@nvidia.com>
To: Kartik Rajput <kkartik@nvidia.com>,
akhilrajeev@nvidia.com, andi.shyti@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
thierry.reding@gmail.com, ldewangan@nvidia.com, digetx@gmail.com,
linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v9 4/4] i2c: tegra: Add Tegra264 support
Date: Fri, 24 Oct 2025 16:43:13 +0100 [thread overview]
Message-ID: <cf862356-1ed4-48ca-9d43-7e008a86eef0@nvidia.com> (raw)
In-Reply-To: <20251001064759.664630-5-kkartik@nvidia.com>
On 01/10/2025 07:47, Kartik Rajput wrote:
> From: Akhil R <akhilrajeev@nvidia.com>
>
> Add support for Tegra264 SoC which supports 17 generic I2C controllers,
> two of which are in the AON (always-on) partition of the SoC. In
> addition to the features supported by Tegra194 it also supports a
> SW mutex register to allow sharing the same I2C instance across
> multiple firmware.
>
> Signed-off-by: Akhil R <akhilrajeev@nvidia.com>
> Signed-off-by: Kartik Rajput <kkartik@nvidia.com>
> ---
> v1 -> v4:
> * Update commit message to mention the SW mutex feature
> available on Tegra264.
> ---
> drivers/i2c/busses/i2c-tegra.c | 29 +++++++++++++++++++++++++++++
> 1 file changed, 29 insertions(+)
>
> diff --git a/drivers/i2c/busses/i2c-tegra.c b/drivers/i2c/busses/i2c-tegra.c
> index 1c8c24ae54ed..f324cf3b1f28 100644
> --- a/drivers/i2c/busses/i2c-tegra.c
> +++ b/drivers/i2c/busses/i2c-tegra.c
> @@ -1814,7 +1814,36 @@ static const struct tegra_i2c_hw_feature tegra256_i2c_hw = {
> .has_interface_timing_reg = true,
> };
>
> +static const struct tegra_i2c_hw_feature tegra264_i2c_hw = {
> + .has_continue_xfer_support = true,
> + .has_per_pkt_xfer_complete_irq = true,
> + .clk_divisor_hs_mode = 1,
> + .clk_divisor_std_mode = 0x1d,
> + .clk_divisor_fast_mode = 0x15,
> + .clk_divisor_fast_plus_mode = 0x8,
> + .has_config_load_reg = true,
> + .has_multi_master_mode = true,
> + .has_slcg_override_reg = true,
> + .has_mst_fifo = true,
> + .quirks = &tegra194_i2c_quirks,
> + .supports_bus_clear = true,
> + .has_apb_dma = false,
> + .tlow_std_mode = 0x8,
> + .thigh_std_mode = 0x7,
> + .tlow_fast_fastplus_mode = 0x2,
> + .thigh_fast_fastplus_mode = 0x2,
> + .tlow_hs_mode = 0x4,
> + .thigh_hs_mode = 0x2,
> + .setup_hold_time_std_mode = 0x08080808,
> + .setup_hold_time_fast_fast_plus_mode = 0x02020202,
> + .setup_hold_time_hs_mode = 0x090909,
> + .has_interface_timing_reg = true,
> + .has_hs_mode_support = true,
> + .has_mutex = true,
> +};
> +
> static const struct of_device_id tegra_i2c_of_match[] = {
> + { .compatible = "nvidia,tegra264-i2c", .data = &tegra264_i2c_hw, },
> { .compatible = "nvidia,tegra256-i2c", .data = &tegra256_i2c_hw, },
> { .compatible = "nvidia,tegra194-i2c", .data = &tegra194_i2c_hw, },
> { .compatible = "nvidia,tegra186-i2c", .data = &tegra186_i2c_hw, },
Reviewed-by: Jon Hunter <jonathanh@nvidia.com>
Jon
--
nvpublic
next prev parent reply other threads:[~2025-10-24 15:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-01 6:47 [PATCH v9 0/4] Add I2C support for Tegra264 Kartik Rajput
2025-10-01 6:47 ` [PATCH v9 1/4] i2c: tegra: Do not configure DMA if not supported Kartik Rajput
2025-10-24 15:20 ` Jon Hunter
2025-10-28 10:00 ` Akhil R
2025-10-28 10:41 ` Jon Hunter
2025-10-28 13:08 ` Akhil R
2025-10-28 16:09 ` Jon Hunter
2025-11-06 15:51 ` Jon Hunter
2025-10-01 6:47 ` [PATCH v9 2/4] i2c: tegra: Add HS mode support Kartik Rajput
2025-10-24 15:28 ` Jon Hunter
2025-11-06 6:17 ` Akhil R
2025-11-06 16:02 ` Jon Hunter
2025-10-01 6:47 ` [PATCH v9 3/4] i2c: tegra: Add support for SW mutex register Kartik Rajput
2025-10-24 15:42 ` Jon Hunter
2025-10-28 12:54 ` Akhil R
2025-10-28 16:14 ` Jon Hunter
2025-11-06 15:52 ` Jon Hunter
2025-10-01 6:47 ` [PATCH v9 4/4] i2c: tegra: Add Tegra264 support Kartik Rajput
2025-10-24 15:43 ` Jon Hunter [this message]
2025-10-21 8:17 ` [PATCH v9 0/4] Add I2C support for Tegra264 Kartik Rajput
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=cf862356-1ed4-48ca-9d43-7e008a86eef0@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=akhilrajeev@nvidia.com \
--cc=andi.shyti@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=digetx@gmail.com \
--cc=kkartik@nvidia.com \
--cc=krzk+dt@kernel.org \
--cc=ldewangan@nvidia.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh@kernel.org \
--cc=thierry.reding@gmail.com \
/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