From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.6 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS, URIBL_BLOCKED,USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 2D927C65C20 for ; Mon, 8 Oct 2018 17:11:20 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id D47982089D for ; Mon, 8 Oct 2018 17:11:19 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=kernel.org header.i=@kernel.org header.b="lOvF/PN7" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org D47982089D Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=linuxfoundation.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726492AbeJIAX7 (ORCPT ); Mon, 8 Oct 2018 20:23:59 -0400 Received: from mail.kernel.org ([198.145.29.99]:49174 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726396AbeJIAX7 (ORCPT ); Mon, 8 Oct 2018 20:23:59 -0400 Received: from localhost (ip-213-127-77-176.ip.prioritytelecom.net [213.127.77.176]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id F30212089D; Mon, 8 Oct 2018 17:11:16 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1539018677; bh=CJO4otBB+4AG157yKMcbbLRwaWjsc8GIaTy0Te5F9/E=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=lOvF/PN7rYMs982LOGieFSgCBplXix9MMgCouJXdh62hDhV4rMccSGoiHP040dqNZ Q8KDabdfAD8/0M5Gq773ynPHoIJlOErhQJZb4Rz6AWurM7dsxSVcvyBzKms1fZDtAV NQB20eg4qYz4QUXCX/RK3o6MapieU5WdG90cFfe4= Date: Mon, 8 Oct 2018 19:11:15 +0200 From: Greg Kroah-Hartman To: "Deucher, Alexander" Cc: "linux-kernel@vger.kernel.org" , "stable@vger.kernel.org" , "Wentland, Harry" , "Zhu, Rex" , Sasha Levin Subject: Re: [PATCH 4.18 222/235] drm/amd/pp: Send khz clock values to DC for smu7/8 Message-ID: <20181008171115.GB29418@kroah.com> References: <20180924113103.999624566@linuxfoundation.org> <20180924113125.488862921@linuxfoundation.org> <20181008144421.GB15968@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Oct 08, 2018 at 04:02:19PM +0000, Deucher, Alexander wrote: > > -----Original Message----- > > From: Greg Kroah-Hartman > > Sent: Monday, October 8, 2018 10:44 AM > > To: Deucher, Alexander > > Cc: linux-kernel@vger.kernel.org; stable@vger.kernel.org; Wentland, Harry > > ; Zhu, Rex ; Sasha Levin > > > > Subject: Re: [PATCH 4.18 222/235] drm/amd/pp: Send khz clock values to DC > > for smu7/8 > > > > On Mon, Oct 08, 2018 at 02:33:56PM +0000, Deucher, Alexander wrote: > > > > -----Original Message----- > > > > From: Greg Kroah-Hartman > > > > Sent: Monday, September 24, 2018 7:53 AM > > > > To: linux-kernel@vger.kernel.org > > > > Cc: Greg Kroah-Hartman ; > > > > stable@vger.kernel.org; Wentland, Harry ; > > > > Deucher, Alexander ; Zhu, Rex > > > > ; Sasha Levin > > > > Subject: [PATCH 4.18 222/235] drm/amd/pp: Send khz clock values to > > > > DC for > > > > smu7/8 > > > > > > > > 4.18-stable review patch. If anyone has any objections, please let me > > know. > > > > > > > > > > This regresses power usage on 4.18. Please revert. > > > https://bugzilla.kernel.org/show_bug.cgi?id=201275 > > > > Is it reverted in "upstream" as well? If not, please get the fix in there and > > then I will be glad to backport it here. > > > > There's no breakage in upstream. This patch addressed breakages in > 4.19 specifically due to some other refactoring we did in the driver. > I'll try and dig out the exact series of patches this addressed. So there is no problem in 4.19-rc7? That contridicts the statement of looking in drm-next for the fixes. confused, greg k-h