linux-edac.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Xiaofei Tan <tanxiaofei@huawei.com>
Cc: <linux-edac@vger.kernel.org>, <linuxarm@huawei.com>,
	<shiju.jose@huawei.com>, <jonathan.cameron@huawei.com>
Subject: Re: [PATCH RESEND 1/2] rasdaemon: add support of l3tag and l3data in hip08 OEM format2
Date: Tue, 21 Jul 2020 13:21:08 +0200	[thread overview]
Message-ID: <20200721132108.3d837c62@coco.lan> (raw)
In-Reply-To: <1590566553-51565-2-git-send-email-tanxiaofei@huawei.com>

Em Wed, 27 May 2020 16:02:32 +0800
Xiaofei Tan <tanxiaofei@huawei.com> escreveu:

> The two modules, l3tag and l3data were originally reported through "ARM
> processor error section". But it is not suitable. Because l3tag or l3data
> doesn't belong to any single CPU core. So we change it to use OEM format2.
> 
> Signed-off-by: Xiaofei Tan <tanxiaofei@huawei.com>

Patches applied, thanks!

> ---
>  non-standard-hisi_hip08.c | 44 ++++++++++++++++++++++++++++++++++++++++++++
>  1 file changed, 44 insertions(+)
> 
> diff --git a/non-standard-hisi_hip08.c b/non-standard-hisi_hip08.c
> index 4cfa107..8bf10c1 100644
> --- a/non-standard-hisi_hip08.c
> +++ b/non-standard-hisi_hip08.c
> @@ -52,6 +52,8 @@
>  #define HISI_OEM_MODULE_ID_PA	2
>  #define HISI_OEM_MODULE_ID_HLLC	3
>  #define HISI_OEM_MODULE_ID_DDRC	4
> +#define HISI_OEM_MODULE_ID_L3T	5
> +#define HISI_OEM_MODULE_ID_L3D	6
>  
>  #define HISI_OEM_TYPE2_VALID_ERR_FR	BIT(6)
>  #define HISI_OEM_TYPE2_VALID_ERR_CTRL	BIT(7)
> @@ -374,6 +376,36 @@ static const char *ddrc_submodule_name[] = {
>  	"TA_DDRC3",
>  };
>  
> +static const char *l3tag_submodule_name[] = {
> +	"TB_PARTITION0",
> +	"TB_PARTITION1",
> +	"TB_PARTITION2",
> +	"TB_PARTITION3",
> +	"TB_PARTITION4",
> +	"TB_PARTITION5",
> +	"TB_PARTITION6",
> +	"TB_PARTITION7",
> +	"TA_PARTITION0",
> +	"TA_PARTITION1",
> +	"TA_PARTITION2",
> +	"TA_PARTITION3",
> +	"TA_PARTITION4",
> +	"TA_PARTITION5",
> +	"TA_PARTITION6",
> +	"TA_PARTITION7",
> +};
> +
> +static const char *l3data_submodule_name[] = {
> +	"TB_BANK0",
> +	"TB_BANK1",
> +	"TB_BANK2",
> +	"TB_BANK3",
> +	"TA_BANK0",
> +	"TA_BANK1",
> +	"TA_BANK2",
> +	"TA_BANK3",
> +};
> +
>  static const struct hisi_module_info hisi_oem_type2_module[] = {
>  	{
>  		.id = HISI_OEM_MODULE_ID_SMMU,
> @@ -404,6 +436,18 @@ static const struct hisi_module_info hisi_oem_type2_module[] = {
>  		.sub_num = ARRAY_SIZE(ddrc_submodule_name),
>  	},
>  	{
> +		.id = HISI_OEM_MODULE_ID_L3T,
> +		.name = "L3TAG",
> +		.sub = l3tag_submodule_name,
> +		.sub_num = ARRAY_SIZE(l3tag_submodule_name),
> +	},
> +	{
> +		.id = HISI_OEM_MODULE_ID_L3D,
> +		.name = "L3DATA",
> +		.sub = l3data_submodule_name,
> +		.sub_num = ARRAY_SIZE(l3data_submodule_name),
> +	},
> +	{
>  	}
>  };
>  



Thanks,
Mauro

  reply	other threads:[~2020-07-21 11:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-27  8:02 [PATCH RESEND 0/2] support l3tag&l3data decoding and one fix Xiaofei Tan
2020-05-27  8:02 ` [PATCH RESEND 1/2] rasdaemon: add support of l3tag and l3data in hip08 OEM format2 Xiaofei Tan
2020-07-21 11:21   ` Mauro Carvalho Chehab [this message]
2020-05-27  8:02 ` [PATCH RESEND 2/2] rasdaemon: fix the issue that non standard decoder can't work in pthread way Xiaofei Tan

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=20200721132108.3d837c62@coco.lan \
    --to=mchehab+huawei@kernel.org \
    --cc=jonathan.cameron@huawei.com \
    --cc=linux-edac@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=shiju.jose@huawei.com \
    --cc=tanxiaofei@huawei.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).