Subject should be:

EDAC, amd64: Add Hygon Dhyana support

On Wed, Aug 29, 2018 at 08:45:45PM +0800, Pu Wen wrote:
> To make AMD64 EDAC and MCE drivers working on Hygon platforms, add
> support for Hygon by using the code path of AMD family 0x17.
> 
> As Hygon will negotiate with AMD to make sure that only Hygon will
> use family 0x18, under this consideration try to minimize code
> modifications and share most codes with AMD.
> 
> Also Hygon PCI Device ID DF_F0/DF_F6(0x1460/0x1466) of Host bridges
> is needed for edac driver.
> 
> Signed-off-by: Pu Wen <pu...@hygon.cn>
> ---
>  drivers/edac/amd64_edac.c | 20 +++++++++++++++++++-
>  drivers/edac/amd64_edac.h |  4 ++++
>  drivers/edac/mce_amd.c    |  4 +++-
>  3 files changed, 26 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/edac/amd64_edac.c b/drivers/edac/amd64_edac.c
> index 18aeabb..d8b4b0e 100644
> --- a/drivers/edac/amd64_edac.c
> +++ b/drivers/edac/amd64_edac.c
> @@ -211,7 +211,7 @@ static int __set_scrub_rate(struct amd64_pvt *pvt, u32 
> new_bw, u32 min_rate)
>  
>       scrubval = scrubrates[i].scrubval;
>  
> -     if (pvt->fam == 0x17) {
> +     if (pvt->fam == 0x17 || pvt->fam == 0x18) {
>               __f17h_set_scrubval(pvt, scrubval);
>       } else if (pvt->fam == 0x15 && pvt->model == 0x60) {
>               f15h_select_dct(pvt, 0);
> @@ -264,6 +264,7 @@ static int get_scrub_rate(struct mem_ctl_info *mci)
>               break;
>  
>       case 0x17:
> +     case 0x18:
>               amd64_read_pci_cfg(pvt->F6, F17H_SCR_BASE_ADDR, &scrubval);
>               if (scrubval & BIT(0)) {
>                       amd64_read_pci_cfg(pvt->F6, F17H_SCR_LIMIT_ADDR, 
> &scrubval);
> @@ -1044,6 +1045,7 @@ static void determine_memory_type(struct amd64_pvt *pvt)
>               goto ddr3;
>  
>       case 0x17:
> +     case 0x18:
>               if ((pvt->umc[0].dimm_cfg | pvt->umc[1].dimm_cfg) & BIT(5))
>                       pvt->dram_type = MEM_LRDDR4;
>               else if ((pvt->umc[0].dimm_cfg | pvt->umc[1].dimm_cfg) & BIT(4))
> @@ -2200,6 +2202,16 @@ static struct amd64_family_type family_types[] = {
>                       .dbam_to_cs             = f17_base_addr_to_cs_size,
>               }
>       },
> +     [HYGON_F18_CPUS] = {
> +             /* Hygon F18h uses the same AMD F17h support */
> +             .ctl_name = "Hygon_F18h",
> +             .f0_id = PCI_DEVICE_ID_HYGON_18H_DF_F0,
> +             .f6_id = PCI_DEVICE_ID_HYGON_18H_DF_F6,
> +             .ops = {
> +                     .early_channel_count    = f17_early_channel_count,
> +                     .dbam_to_cs             = f17_base_addr_to_cs_size,
> +             }
> +     },
>  };
>  
>  /*
> @@ -3192,6 +3204,11 @@ static struct amd64_family_type 
> *per_family_init(struct amd64_pvt *pvt)
>               pvt->ops        = &family_types[F17_CPUS].ops;
>               break;
>  
> +     case 0x18:
> +             fam_type        = &family_types[HYGON_F18_CPUS];
> +             pvt->ops        = &family_types[HYGON_F18_CPUS].ops;
> +             break;
> +

You can use the F17_CPUS array element here and overwrite the ->ctl_name
string only. No need to define [HYGON_F18_CPUS] above... yet.

>       default:
>               amd64_err("Unsupported family!\n");
>               return NULL;
> @@ -3428,6 +3445,7 @@ static const struct x86_cpu_id amd64_cpuids[] = {
>       { X86_VENDOR_AMD, 0x15, X86_MODEL_ANY,  X86_FEATURE_ANY, 0 },
>       { X86_VENDOR_AMD, 0x16, X86_MODEL_ANY,  X86_FEATURE_ANY, 0 },
>       { X86_VENDOR_AMD, 0x17, X86_MODEL_ANY,  X86_FEATURE_ANY, 0 },
> +     { X86_VENDOR_HYGON, 0x18, X86_MODEL_ANY, X86_FEATURE_ANY, 0 },
>       { }
>  };
>  MODULE_DEVICE_TABLE(x86cpu, amd64_cpuids);
> diff --git a/drivers/edac/amd64_edac.h b/drivers/edac/amd64_edac.h
> index 1d4b74e..6e5f609 100644
> --- a/drivers/edac/amd64_edac.h
> +++ b/drivers/edac/amd64_edac.h
> @@ -116,6 +116,9 @@
>  #define PCI_DEVICE_ID_AMD_17H_DF_F0  0x1460
>  #define PCI_DEVICE_ID_AMD_17H_DF_F6  0x1466
>  
> +#define PCI_DEVICE_ID_HYGON_18H_DF_F0        0x1460
> +#define PCI_DEVICE_ID_HYGON_18H_DF_F6        0x1466

As in the previous patch - use the AMD defines.

-- 
Regards/Gruss,
    Boris.

Good mailing practices for 400: avoid top-posting and trim the reply.

Reply via email to