Linux Tegra architecture development
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Ketan Patil <ketanp@nvidia.com>,
	thierry.reding@gmail.com, jonathanh@nvidia.com
Cc: linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH 4/4] memory: tegra: Add MC error logging support for Tegra264
Date: Wed, 17 Sep 2025 11:09:05 +0900	[thread overview]
Message-ID: <cef760ee-f74d-4a0a-86e6-020223f79b27@kernel.org> (raw)
In-Reply-To: <20250916051754.39250-5-ketanp@nvidia.com>

On 16/09/2025 07:17, Ketan Patil wrote:
> +static irqreturn_t handle_sbs_irq(int irq, void *data)
> +{
> +	return handle_generic_irq((struct tegra_mc *)data, MSS_SBS_INTSTATUS_0);
> +}
> +
> +static irqreturn_t handle_channel_irq(int irq, void *data)
> +{
> +	return handle_generic_irq((struct tegra_mc *)data, MC_CH_INTSTATUS_0);
> +}


Patchset fails building (see LKP report), so I won't be doing full
review, but few obvious issues to spare you from one resubmit:

> +
> +const irq_handler_t tegra264_mc_irq_handlers[8] = {

static

> +	handle_mcf_irq, handle_hub_irq, handle_hub_irq,
> +	handle_hub_irq, handle_hub_irq, handle_hub_irq,
> +	handle_sbs_irq, handle_channel_irq
> +};
> +
> +const struct tegra_mc_ops tegra264_mc_ops = {
> +	.probe = tegra186_mc_probe,
> +	.remove = tegra186_mc_remove,
> +	.probe_device = tegra186_mc_probe_device,
> +	.resume = tegra186_mc_resume,
> +	.handle_irq = tegra264_mc_irq_handlers,
> +	.num_interrupts = ARRAY_SIZE(tegra264_mc_irq_handlers),
> +};
> +
>  static const struct tegra_mc_icc_ops tegra264_mc_icc_ops = {
>  	.xlate = tegra_mc_icc_xlate,
>  	.aggregate = tegra264_mc_icc_aggregate,
> @@ -290,18 +657,31 @@ static const struct tegra_mc_icc_ops tegra264_mc_icc_ops = {
>  	.set = tegra264_mc_icc_set,
>  };
>  


Best regards,
Krzysztof

      parent reply	other threads:[~2025-09-17  2:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-16  5:17 [PATCH 0/4] memory: tegra: Add MC error logging support for Tegra264 SoC Ketan Patil
2025-09-16  5:17 ` [PATCH 1/4] memory: tegra: Group mc-err related registers Ketan Patil
2025-09-16  5:17 ` [PATCH 2/4] memory: tegra: Group register and fields Ketan Patil
2025-09-16  5:17 ` [PATCH 3/4] memory: tegra: Add support for multiple irqs Ketan Patil
2025-09-22  1:39   ` kernel test robot
2025-09-16  5:17 ` [PATCH 4/4] memory: tegra: Add MC error logging support for Tegra264 Ketan Patil
2025-09-17  1:32   ` kernel test robot
2025-09-17  2:09   ` Krzysztof Kozlowski [this message]

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=cef760ee-f74d-4a0a-86e6-020223f79b27@kernel.org \
    --to=krzk@kernel.org \
    --cc=jonathanh@nvidia.com \
    --cc=ketanp@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.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