From: Dmitry Osipenko <digetx@gmail.com>
To: Ashish Mhetre <amhetre@nvidia.com>,
thierry.reding@gmail.com, jonathanh@nvidia.com,
linux-tegra@vger.kernel.org, krzysztof.kozlowski@canonical.com,
linux-kernel@vger.kernel.org
Cc: Snikam@nvidia.com, vdumpa@nvidia.com
Subject: Re: [Patch V1 3/4] memory: tegra: add mc-err support for T186
Date: Wed, 19 Jan 2022 16:41:35 +0300 [thread overview]
Message-ID: <f98df604-1b2b-3803-b415-445656a6fa4b@gmail.com> (raw)
In-Reply-To: <a926e5aa-4872-5585-d367-da815518915c@nvidia.com>
19.01.2022 11:53, Ashish Mhetre пишет:
>
>
> On 1/12/2022 4:31 PM, Dmitry Osipenko wrote:
>> External email: Use caution opening links or attachments
>>
>>
>> 11.01.2022 21:45, Ashish Mhetre пишет:
>>> Add all mc-errors supported by T186.
>>> Implement mc interrupt handling routine for T186.
>>>
>>> Signed-off-by: Ashish Mhetre <amhetre@nvidia.com>
>>> ---
>>> drivers/memory/tegra/mc.h | 17 +++++++
>>> drivers/memory/tegra/tegra186.c | 100
>>> ++++++++++++++++++++++++++++++++++++++++
>>> 2 files changed, 117 insertions(+)
>>>
>>> diff --git a/drivers/memory/tegra/mc.h b/drivers/memory/tegra/mc.h
>>> index 2d4f495..7817492 100644
>>> --- a/drivers/memory/tegra/mc.h
>>> +++ b/drivers/memory/tegra/mc.h
>>> @@ -44,6 +44,15 @@
>>> #define MC_TIMING_CONTROL_DBG 0xf8
>>> #define MC_TIMING_CONTROL 0xfc
>>>
>>
>> this empty line is unnecessary
>>
> I'll fix this in next version.
>
>>> +#define MC_ERR_VPR_STATUS 0x654
>>> +#define MC_ERR_VPR_ADR 0x658
>>> +#define MC_ERR_SEC_STATUS 0x67c
>>> +#define MC_ERR_SEC_ADR 0x680
>>> +#define MC_ERR_MTS_STATUS 0x9b0
>>> +#define MC_ERR_MTS_ADR 0x9b4
>>> +#define MC_ERR_GENERALIZED_CARVEOUT_STATUS 0xc00
>>> +#define MC_ERR_GENERALIZED_CARVEOUT_ADR 0xc04
>>> +
>>> #define MC_INT_DECERR_ROUTE_SANITY BIT(20)
>>> #define MC_INT_WCAM_ERR BIT(19)
>>> #define MC_INT_SCRUB_ECC_WR_ACK BIT(18)
>>> @@ -159,6 +168,14 @@ extern const struct tegra_mc_ops tegra186_mc_ops;
>>> extern const char * const tegra_mc_status_names[32];
>>> extern const char * const tegra_mc_error_names[8];
>>>
>>> +struct tegra_mc_error {
>>> + u32 int_bit;
>>> + const char *msg;
>>> + u32 status_reg;
>>> + u32 addr_reg;
>>> + u32 addr_reg_hi;
>>> +};
>>> +
>>> /*
>>> * These IDs are for internal use of Tegra ICC drivers. The ID
>>> numbers are
>>> * chosen such that they don't conflict with the device-tree ICC
>>> node IDs.
>>> diff --git a/drivers/memory/tegra/tegra186.c
>>> b/drivers/memory/tegra/tegra186.c
>>> index 6766cc4..4f3ae71 100644
>>> --- a/drivers/memory/tegra/tegra186.c
>>> +++ b/drivers/memory/tegra/tegra186.c
>>> @@ -146,8 +146,107 @@ static void tegra186_mc_clear_interrupt(struct
>>> tegra_mc *mc)
>>> mc_writel(mc, MC_INTSTATUS_CLEAR, MC_INTSTATUS);
>>> }
>>>
>>> +static const struct tegra_mc_error int_mc_errors[] = {
>>> + {
>>> + .int_bit = MC_INT_DECERR_EMEM,
>>> + .msg = "EMEM address decode error",
>>> + .status_reg = MC_ERR_STATUS,
>>> + .addr_reg = MC_ERR_ADR,
>>> + },
>>> + {
>>> + .int_bit = MC_INT_SECURITY_VIOLATION,
>>> + .msg = "non secure access to secure region",
>>> + .status_reg = MC_ERR_STATUS,
>>> + .addr_reg = MC_ERR_ADR,
>>> + },
>>> + {
>>> + .int_bit = MC_INT_DECERR_VPR,
>>> + .msg = "MC request violates VPR requirements",
>>> + .status_reg = MC_ERR_VPR_STATUS,
>>> + .addr_reg = MC_ERR_VPR_ADR,
>>> + },
>>
>> I see that these VPR registers present on all SoCs starting with T124.
>> It doesn't look like you need the separate IRQ handlers at all, instead
>> please extend the common T30 handler. For example, you may add a
>> switch-case statements to handle those T124+ specific bits differently.
>>
>> static irqreturn_t tegra30_mc_handle_irq(int irq, void *data)
>> {
>> ...
>> switch (bit) {
>> case MC_INT_DECERR_VPR:
>> status_reg = MC_ERR_VPR_STATUS;
>> addr_reg = MC_ERR_VPR_ADR;
>> break;
>> ...
>> default:
>> status_reg = MC_ERR_STATUS;
>> addr_reg = MC_ERR_ADR;
>> }
>>
>> value = mc_readl(mc, status_reg);
>> ...
>>
>> value = mc_readl(mc, addr_reg);
> Okay. I'll use same handler as Tegra30 with additional Tegra186 onward
> bits.
> Also, shall I change name of tegra30_mc_handle_irq() to
> tegra_mc_handle_irq() as we are using it across all Tegra SOCs ?
T20 won't use it, no need to change the name.
next prev parent reply other threads:[~2022-01-19 13:41 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 18:45 [Patch V1 0/4] memory: tegra: Update mc interrupts Ashish Mhetre
2022-01-11 18:45 ` [Patch V1 1/4] memory: tegra: Add support for " Ashish Mhetre
2022-01-11 20:29 ` Krzysztof Kozlowski
2022-01-19 7:36 ` Ashish Mhetre
2022-01-12 8:13 ` Dmitry Osipenko
2022-01-19 8:47 ` Ashish Mhetre
2022-01-19 13:42 ` Dmitry Osipenko
2022-01-11 18:45 ` [Patch V1 2/4] memory: tegra: Add interrupt mask Ashish Mhetre
2022-01-11 20:32 ` Krzysztof Kozlowski
2022-01-19 7:38 ` Ashish Mhetre
2022-01-11 18:45 ` [Patch V1 3/4] memory: tegra: add mc-err support for T186 Ashish Mhetre
2022-01-11 20:56 ` Krzysztof Kozlowski
2022-01-19 8:33 ` Ashish Mhetre
2022-01-12 11:01 ` Dmitry Osipenko
2022-01-19 8:53 ` Ashish Mhetre
2022-01-19 13:41 ` Dmitry Osipenko [this message]
2022-01-12 11:02 ` Dmitry Osipenko
2022-01-19 8:58 ` Ashish Mhetre
2022-01-12 11:22 ` Dmitry Osipenko
2022-01-12 11:24 ` Dmitry Osipenko
2022-01-19 9:09 ` Ashish Mhetre
2022-01-19 13:42 ` Dmitry Osipenko
2022-01-11 18:45 ` [Patch V1 4/4] memory: tegra: add mc-err support for T194 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=f98df604-1b2b-3803-b415-445656a6fa4b@gmail.com \
--to=digetx@gmail.com \
--cc=Snikam@nvidia.com \
--cc=amhetre@nvidia.com \
--cc=jonathanh@nvidia.com \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.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).