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=-3.1 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS, USER_AGENT_NEOMUTT 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 F33E1C282D4 for ; Wed, 30 Jan 2019 05:25:17 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id B9C1420989 for ; Wed, 30 Jan 2019 05:25:17 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=linaro.org header.i=@linaro.org header.b="TPcCr10f" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726094AbfA3FZP (ORCPT ); Wed, 30 Jan 2019 00:25:15 -0500 Received: from mail-pf1-f196.google.com ([209.85.210.196]:39808 "EHLO mail-pf1-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725791AbfA3FZP (ORCPT ); Wed, 30 Jan 2019 00:25:15 -0500 Received: by mail-pf1-f196.google.com with SMTP id r136so10875765pfc.6 for ; Tue, 29 Jan 2019 21:25:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=t5yA8cOsWjs/14X76a0lSFOxV69dBFRlKTngX6mg3sk=; b=TPcCr10fTvkMNONcCV4vv+PVOBkwI2iYbbPY5sbNT4ZIbuui8hKkUMnHTMHmjRAyKm 0YoBEulALYRX4ucPEDchvNMAgFwNQ3yvuplnuUurPIP4G/QVkvd3IdUaLomotfllXRoB FY+Vb/KP9bEyZncucuKPIz/W+CZqUbBKOodW0= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=t5yA8cOsWjs/14X76a0lSFOxV69dBFRlKTngX6mg3sk=; b=GNWw3QQYqGHNDVR/j+RMY400YsUUmVCo98G4eZx8srHUVU+hDNN6AqaF82QbAtd1kA 3KrrQ/YLKxU/kBPdgxpwgseHbzcmRr2EgGibl9UwVE7RZn7QoyeRYvrGbLGdiHaAbTue opuJ9tmZ1anPzGfKR/cSXdHgQqVpilTT1VWosCkcpnb09nj2E7hWDII3vMD+KhjaBVWy sHDFSUmc/NtOTWjr6xZE3Bb9Zg6V2u8vdWhYfFq27v51QsO7GGXPCqvH5tHCBdejlCb6 va6MkLB9Kbwk6XHOe4KNTBzpFD+CdKCaukwhwoIorLl1Ur1G6sqqumr819rpomDXNfal aFEQ== X-Gm-Message-State: AJcUukcLsx7ggLdcL6GD/NFD6LI02c/zdh60W8cMqh0csk/DEuRGt+yv eq2U5YetKJZRkI3Vljq3B9WR0A== X-Google-Smtp-Source: ALg8bN4ROBST7MqOE33iqfMSkmBxryyo4iUMHWhJTMBzZN3ubxl7zVTNYvpRGxBUAx2KeCMzS0H2zw== X-Received: by 2002:a63:5207:: with SMTP id g7mr26623198pgb.253.1548825914803; Tue, 29 Jan 2019 21:25:14 -0800 (PST) Received: from localhost ([122.172.102.63]) by smtp.gmail.com with ESMTPSA id u29sm608476pgn.23.2019.01.29.21.25.13 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 29 Jan 2019 21:25:13 -0800 (PST) Date: Wed, 30 Jan 2019 10:55:11 +0530 From: Viresh Kumar To: Juri Lelli Cc: "Rafael J. Wysocki" , Rafael Wysocki , Greg Kroah-Hartman , Viresh Kumar , Linux PM , Vincent Guittot , Matthias Kaehlcke , Linux Kernel Mailing List Subject: Re: [PATCH 0/3] drivers: Frequency constraint infrastructure Message-ID: <20190130052511.5k6mhwu45vzpz6il@vireshk-i7> References: <20190117131631.GA14385@localhost.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190117131631.GA14385@localhost.localdomain> User-Agent: NeoMutt/20180323-120-3dd1ac Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 17-01-19, 14:16, Juri Lelli wrote: > I was also wondering how this new framework is dealing with > constraints/request imposed/generated by the scheduler and related > interfaces (thinking about schedutil and Patrick's util_clamp). I am not very sure about what constraints are imposed by schedutil or util-clamp stuff that may not work well with this stuff. As you are already aware of it, this series isn't doing anything new as we already have thermal/user constraints available in kernel. I am just trying to implement a better way to present those to the cpufreq core. -- viresh