Received: by 2002:a4a:311b:0:0:0:0:0 with SMTP id k27-v6csp4250325ooa; Tue, 14 Aug 2018 03:28:55 -0700 (PDT) X-Google-Smtp-Source: AA+uWPzMJDgtjjbqtgCHtDJIVFy5F/h+jZ2HN24zHiTo54IBINapl1SszhJQiJqho90A0q2HZlyL X-Received: by 2002:a62:7983:: with SMTP id u125-v6mr22593657pfc.177.1534242535904; Tue, 14 Aug 2018 03:28:55 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1534242535; cv=none; d=google.com; s=arc-20160816; b=DjOOAelQ4WZ4kd7aMyAdEFnMgkr4xl+Jt3HSr9+hDYgqDloawRuYAGIW3HKNvpnkDO BqhEBArk4IUe7xST0tR3rF0bmuIltWk57ovEMav2qEg95JlMftIidQECCIaBgH3kXJYU z3WdeJhrqIw7vxWU3pWeA6OOdMUwQSyz4wEw7Y6010fyqDDZuQu9HeYfOL7VpJy2GYl+ C0QQ7axyKvSKiW6iP5tkoDLYO0h88WaEHKlLk/af52VFSb36Gq2YdYQZjJWgzOL9ocDj 9DeEvSWT/MX32/Xzg0NOQlHl3ZUW8ulq44sqfiKRBH8mp76LjTrF5UgKy3rdw5EE7XpU Ig3g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :arc-authentication-results; bh=/xyiFZeVKf+DlXi4BKN255Ky4JmfQLvFXix2HfgTUCY=; b=NGJOa6EarzQxEtswQeNW/Bh5SWs6g6wQgPcjyf6FIvOhm4nlHBgHr60oE4YdZyu6Os RchUD8/+rULuk5RLZkOcVUA4YKJDvpWwUi21jTqq0MAacMMWilDLt8PD+CqpWXdN3Emp salfie3wSJH1FLLd13nqM5/9L9Tw+WIGUVU/h2VBeH7YpuL2TP+ZKVykJJbITH80cFPN qp9xvPRUt9cLVQuOeIsgtgmt2K8DtzSLEiBRxV80rNgZ4U8Q7Du3CGuz+spV3Z+NawMI a9ufd/DkH3eX/OzDgr60kSOCkvNmkLwHsa/ksLyWP364cS2lbcVjzzAyvekczJgdoepL hBQw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id v3-v6si17143451plz.419.2018.08.14.03.28.41; Tue, 14 Aug 2018 03:28:55 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1732135AbeHNNA0 (ORCPT + 99 others); Tue, 14 Aug 2018 09:00:26 -0400 Received: from cloudserver094114.home.pl ([79.96.170.134]:51767 "EHLO cloudserver094114.home.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1732070AbeHNNAZ (ORCPT ); Tue, 14 Aug 2018 09:00:25 -0400 Received: from 79.184.254.66.ipv4.supernova.orange.pl (79.184.254.66) (HELO aspire.rjw.lan) by serwer1319399.home.pl (79.96.170.134) with SMTP (IdeaSmtpServer 0.83) id 8008b5d4cf829f7b; Tue, 14 Aug 2018 12:13:53 +0200 From: "Rafael J. Wysocki" To: Pu Wen Cc: "Rafael J. Wysocki" , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , the arch/x86 maintainers , thomas.lendacky@amd.com, Borislav Petkov , Paolo Bonzini , Viresh Kumar , Linux Kernel Mailing List , linux-arch , Linux PM Subject: Re: [PATCH v3 15/17] driver/cpufreq: enable Hygon support to cpufreq driver Date: Tue, 14 Aug 2018 12:11:44 +0200 Message-ID: <2048121.dGp66DhuPz@aspire.rjw.lan> In-Reply-To: <04744a9f-5865-bbc8-7735-e92c6cf6472d@hygon.cn> References: <04744a9f-5865-bbc8-7735-e92c6cf6472d@hygon.cn> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Monday, August 13, 2018 6:22:16 PM CEST Pu Wen wrote: > On 2018/8/12 17:55, Rafael J. Wysocki wrote: > > On Sat, Aug 11, 2018 at 3:36 PM Pu Wen wrote: > >> > >> Enable ACPI cpufreq driver support for Hygon by adding family ID check > >> along with AMD. > >> > >> As Hygon platforms have SMBus device(PCI device ID 0x790b), enable Hygon > >> support to function amd_freq_sensitivity_init(). > >> > >> Signed-off-by: Pu Wen > > > > Is there any technical difference between HYGON and AMD? > > For ACPI cpufreq patch, you are right. But for the whole point of view, > there has some technical difference between Hygon Dhyana and AMD Family > 17h. > For cpufreq if not added X86_VENDOR_HYGON codes, this driver will not > work functionally on Hygon platforms. > > > > > You seem to be mechanically adding X86_VENDOR_HYGON wherever > > X86_VENDOR_AMD is used. > > X86_VENDOR_HYGON is not mechanically added wherever X86_VENDOR_AMD is > used, we have reviewed and tested the features wherever X86_VENDOR_HYGON > is needed. > > As Hygon Dhyana can share code path with AMD family 17h, to minimize the > code duplication, we choose to reuse the AMD's codes here. OK The cpufreq changes are fine by me. Thanks!