devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ashish Mhetre <amhetre@nvidia.com>
To: Dmitry Osipenko <digetx@gmail.com>,
	krzysztof.kozlowski@linaro.org, thierry.reding@gmail.com,
	jonathanh@nvidia.com, robh+dt@kernel.org,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	linux-tegra@vger.kernel.org, krzysztof.kozlowski+dt@linaro.org
Cc: vdumpa@nvidia.com, Snikam@nvidia.com
Subject: Re: [Patch v6 2/4] memory: tegra: Add MC error logging on tegra186 onward
Date: Mon, 11 Apr 2022 11:47:37 +0530	[thread overview]
Message-ID: <583c656f-02d2-9bd9-b381-916abc2eb97a@nvidia.com> (raw)
In-Reply-To: <158816cb-9509-5962-11ea-e06aee991e14@gmail.com>



On 4/10/2022 8:25 PM, Dmitry Osipenko wrote:
> External email: Use caution opening links or attachments
> 
> 
> 06.04.2022 08:24, Ashish Mhetre пишет:
>>        /* clear interrupts */
>> -     mc_writel(mc, status, MC_INTSTATUS);
>> +     if (mc->soc->num_channels) {
>> +             u32 status_chan_bit;
>> +
>> +             mc_ch_writel(mc, channel, status, MC_INTSTATUS);
>> +             status_chan_bit = BIT(channel) << mc->soc->status_reg_chan_shift;
> 
> s/status_reg_chan_shift/global_intstatus_channel_shift/
> 
Okay, I'll update in v7.

>> +             mc_ch_writel(mc, MC_BROADCAST_CHANNEL, status_chan_bit, MC_GLOBAL_INTSTATUS);
> and maybe add a one-line mc_channel_to_global_intstatus(mc, channel) helper
> 
> mc_ch_writel(mc, MC_BROADCAST_CHANNEL,
>               mc_channel_to_global_intstatus(mc, chan),
>               MC_GLOBAL_INTSTATUS);
> 
Okay, I'll add helper for getting status bit from channel and use it.

>> +     } else
>> +             mc_writel(mc, status, MC_INTSTATUS);
> 
> Missing braces after "else", "./scripts/checkpatch.pl --strict" should warn about this.
> 
I didn't run checkpatch.pl with "--strict". I will run from next time
and address this.

> Otherwise this patch looks okay at a quick glance.

Thanks Dmitry. I'll address these comments.


  reply	other threads:[~2022-04-11  6:17 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-06  5:24 [Patch v6 0/4] memory: tegra: Add MC channels and error logging Ashish Mhetre
2022-04-06  5:24 ` [Patch v6 1/4] memory: tegra: Add memory controller channels support Ashish Mhetre
2022-04-10 14:18   ` Dmitry Osipenko
2022-04-11  6:05     ` Ashish Mhetre
2022-04-11  6:33       ` Dmitry Osipenko
2022-04-11  7:28         ` Ashish Mhetre
2022-04-11  7:35           ` Dmitry Osipenko
2022-04-11  9:18             ` Ashish Mhetre
2022-04-11 11:13               ` Dmitry Osipenko
2022-04-10 15:01   ` Dmitry Osipenko
2022-04-11  6:18     ` Ashish Mhetre
2022-04-10 15:04   ` Dmitry Osipenko
2022-04-11  6:20     ` Ashish Mhetre
2022-04-06  5:24 ` [Patch v6 2/4] memory: tegra: Add MC error logging on tegra186 onward Ashish Mhetre
2022-04-10 14:55   ` Dmitry Osipenko
2022-04-11  6:17     ` Ashish Mhetre [this message]
2022-04-06  5:24 ` [Patch v6 3/4] dt-bindings: memory: Update reg maxitems for tegra186 Ashish Mhetre
2022-04-10 14:21   ` Dmitry Osipenko
2022-04-11  6:09     ` Ashish Mhetre
2022-04-11 15:02     ` Ashish Mhetre
2022-04-11 15:29       ` Dmitry Osipenko
2022-04-11 15:41         ` Ashish Mhetre
2022-04-11 22:28           ` Dmitry Osipenko
2022-04-12  4:11             ` Ashish Mhetre
2022-04-06  5:24 ` [Patch v6 4/4] arm64: tegra: Add memory controller channels Ashish Mhetre

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=583c656f-02d2-9bd9-b381-916abc2eb97a@nvidia.com \
    --to=amhetre@nvidia.com \
    --cc=Snikam@nvidia.com \
    --cc=devicetree@vger.kernel.org \
    --cc=digetx@gmail.com \
    --cc=jonathanh@nvidia.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=thierry.reding@gmail.com \
    --cc=vdumpa@nvidia.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;
as well as URLs for NNTP newsgroup(s).