Received: by 10.213.65.68 with SMTP id h4csp3923559imn; Tue, 10 Apr 2018 06:44:38 -0700 (PDT) X-Google-Smtp-Source: AIpwx4/Q8P6h/WyxKTjFRpBn14AQR9hSRljngoWhtkITKdziyJ7Hk7bzUIHI3tBqnhZN3qeQUemo X-Received: by 2002:a17:902:988d:: with SMTP id s13-v6mr543021plp.30.1523367878477; Tue, 10 Apr 2018 06:44:38 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1523367878; cv=none; d=google.com; s=arc-20160816; b=gXeVfp1NNOX1zjQGeXtr12jSPgdrF7DtbwzQ6+GM8kmc6UGhLtoau+mHs4w/zBgW75 0d6IGJez9i69w3SxDDDySATLqjCn5SDmfmzoogyOc5Hywd3hU0F5VNBbCQbhe5nXUoVg ObnWKfOcjM+lRrbAA7GLIWkKWulPGgjCgwIsjMuSF9pryD9WfUC+t4zyC2IzcbxHoojE 1gjqcw7o9Rchtx/39PNYYnN86Xttj/6gB4lrs7y+5gfvZLcusCazfufZDIu44inqMrE8 ePimrmqEO+YQKtTKqashPfFszikkLVrIzsTf1Z4hQS6ndnJrmG8y0ie0nDt48gUb5mXE B5OQ== 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:date:cc:to:from:subject:message-id :arc-authentication-results; bh=qUSDPhYpWO6j82CQSwMGDp6KfM4CF1lpsQevStWEZFI=; b=X+Cy2MZQ+6KxsuIm8AiHwsDWE3lWuWaDFLALSAtWBrxKYA4D5bRNiYj7lE2Pb01dnl 7SUvjQsXX53zglvlYv2VrqQw4PZlWPUqnsGxwR269wy+TuJXUeA+YHHBatHf6mQSXhdx tqK4MK0k+x1pJsbziSJ9RoA6bm2UEOCBuVFugFOk6BvXEb37beHSNZ5CwUET4N9t8Xtg nW9NpN1pRO7PLjf6xSOQo3Y7vE9fVTt5N5sUxihL10/s2GHsr3U/y4cj0sRJ3VynN1uL Qs4hSA+PBs/s3B9cf4p7NBtetcBPxlPvQTAT8KGP19jIOp5PTbWY6goADRmKh34gAKbU dr1w== 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 p6si2109699pfk.357.2018.04.10.06.44.01; Tue, 10 Apr 2018 06:44:38 -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 S1753122AbeDJNlC (ORCPT + 99 others); Tue, 10 Apr 2018 09:41:02 -0400 Received: from metis.ext.pengutronix.de ([85.220.165.71]:36189 "EHLO metis.ext.pengutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753057AbeDJNlA (ORCPT ); Tue, 10 Apr 2018 09:41:00 -0400 Received: from weser.hi.pengutronix.de ([2001:67c:670:100:fa0f:41ff:fe58:4010]) by metis.ext.pengutronix.de with esmtp (Exim 4.89) (envelope-from ) id 1f5tW2-0006l5-Uz; Tue, 10 Apr 2018 15:40:54 +0200 Message-ID: <1523367652.4981.9.camel@pengutronix.de> Subject: Re: [PATCH V7 00/13] drivers: Boot Constraint core From: Lucas Stach To: Georgi Djakov , Greg Kroah-Hartman , Viresh Kumar Cc: Vincent Guittot , Stephen Boyd , Rajendra Nayak , linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, robdclark@gmail.com, s.hauer@pengutronix.de, shawnguo@kernel.org, fabio.estevam@nxp.com, nm@ti.com, xuwei5@hisilicon.com, robh+dt@kernel.org, olof@lixom.net Date: Tue, 10 Apr 2018 15:40:52 +0200 In-Reply-To: References: <20180322012606.vuaemu3pvpeojtwr@vireshk-mac-ubuntu> <20180323150420.GA21152@kroah.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.22.6-1+deb9u1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-SA-Exim-Connect-IP: 2001:67c:670:100:fa0f:41ff:fe58:4010 X-SA-Exim-Mail-From: l.stach@pengutronix.de X-SA-Exim-Scanned: No (on metis.ext.pengutronix.de); SAEximRunCond expanded to false X-PTX-Original-Recipient: linux-kernel@vger.kernel.org Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Georgi, Am Freitag, den 30.03.2018, 18:24 +0300 schrieb Georgi Djakov: [...] > The interconnect core takes requests from consumer drivers for their > bandwidth needs and configures the hardware to keep the lowest possible > power profile. I think that the boot constraint patches would be useful > to make a board run at maximum performance during boot, until all > consumer drivers are probed and all bandwidth requests are taken into > account. Can you please describe how this bootconstraints core integration is simpler than a "run things at max performance until late kernel init", which could be triggered by a simple initcall similar to what is done for clocks and regulators? To me the bootcontraints stuff looks like a fairly complex solution and your use-case doesn't even sound like you strictly want to keep a bootloader configuration, but rather run things at max performance until you are reasonably sure that you got all the necessary bandwidth requests. Regards, Lucas