All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: Ketan Patil <ketanp@nvidia.com>
Cc: krzk@kernel.org, jonathanh@nvidia.com,
	linux-kernel@vger.kernel.org,  linux-tegra@vger.kernel.org
Subject: Re: [PATCH v5 1/4] memory: tegra: Group mc-err related registers
Date: Mon, 12 Jan 2026 14:29:30 +0100	[thread overview]
Message-ID: <aWTuW1ffEWFz5ChH@orome> (raw)
In-Reply-To: <20251219114354.2727906-2-ketanp@nvidia.com>

[-- Attachment #1: Type: text/plain, Size: 1352 bytes --]

On Fri, Dec 19, 2025 at 11:43:51AM +0000, Ketan Patil wrote:
[...]
> diff --git a/include/soc/tegra/mc.h b/include/soc/tegra/mc.h
[...]
> @@ -168,6 +168,23 @@ struct tegra_mc_ops {
>  	int (*probe_device)(struct tegra_mc *mc, struct device *dev);
>  };
>  
> +struct tegra_mc_regs {
> +	unsigned int mc_cfg_channel_enable;
> +	unsigned int mc_err_status;
> +	unsigned int mc_err_add;
> +	unsigned int mc_err_add_hi;
> +	unsigned int mc_err_vpr_status;
> +	unsigned int mc_err_vpr_add;
> +	unsigned int mc_err_sec_status;
> +	unsigned int mc_err_sec_add;
> +	unsigned int mc_err_mts_status;
> +	unsigned int mc_err_mts_add;
> +	unsigned int mc_err_gen_co_status;
> +	unsigned int mc_err_gen_co_add;
> +	unsigned int mc_err_route_status;
> +	unsigned int mc_err_route_add;

There's really no need for the mc_ prefix here since the structure is
already called tegra_mc_regs.

> +};
> +
>  struct tegra_mc_soc {
>  	const struct tegra_mc_client *clients;
>  	unsigned int num_clients;
> @@ -196,6 +213,7 @@ struct tegra_mc_soc {
>  
>  	const struct tegra_mc_icc_ops *icc_ops;
>  	const struct tegra_mc_ops *ops;
> +	const struct tegra_mc_regs *mc_regs;
>  };

Similarly, there's only one "regs" structure, and it's embedded inside a
structure that is all about the MC, so the mc_ prefix can be omitted.

Thierry

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2026-01-12 13:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-19 11:43 [PATCH v5 0/4] memory: tegra: Add MC error logging support for Tegra264 SoC Ketan Patil
2025-12-19 11:43 ` [PATCH v5 1/4] memory: tegra: Group mc-err related registers Ketan Patil
2026-01-12 13:29   ` Thierry Reding [this message]
2025-12-19 11:43 ` [PATCH v5 2/4] memory: tegra: Group register and fields Ketan Patil
2026-01-07 11:53   ` Jon Hunter
2025-12-19 11:43 ` [PATCH v5 3/4] memory: tegra: Add support for multiple irqs Ketan Patil
2026-01-12 10:52   ` Thierry Reding
2025-12-19 11:43 ` [PATCH v5 4/4] memory: tegra: Add MC error logging support for Tegra264 Ketan Patil
2026-01-07 12:47   ` Jon Hunter
2026-01-07 12:57     ` Jon Hunter
2026-01-12 12:49   ` Thierry Reding

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=aWTuW1ffEWFz5ChH@orome \
    --to=thierry.reding@gmail.com \
    --cc=jonathanh@nvidia.com \
    --cc=ketanp@nvidia.com \
    --cc=krzk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.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.