Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp196983yba; Tue, 23 Apr 2019 22:49:42 -0700 (PDT) X-Google-Smtp-Source: APXvYqzVxyTHNahM/cMm1dFLB5zPk92L9gW0hZIui9uDahX27v9W6gcJ6FT6GfM4DvXyBfGoy45B X-Received: by 2002:a62:26c1:: with SMTP id m184mr31616506pfm.102.1556084981930; Tue, 23 Apr 2019 22:49:41 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1556084981; cv=none; d=google.com; s=arc-20160816; b=dWoQfq+Sd4W/MfQw3j/IE5lcE76/BCVk6I4jU/D6lX/GmZSzaTT96RNARkNHE9oWPl cKc9AhvpZixvMRDPAL4e1ARg6H24ADEfx7PEQGuKANRu75ejJOVWqeKWdGdhhX5MxIVp 9R2epcni+taNzC6zoJOtKh8XdFAziiPvqJg2jVozgVDDYP+IEefbED2t/lRpEXCIEs5X rBypfzg9JMapVTp5Aqb/QPKRScCan2gwGHNSTqQ4cyHQGnrIYZPKrxiln3fqoN6YEFWn ZNIEDOhAWA5b4t1gdQDRr6pd/xfgMlj8Icc43DckExjFKPwa3yrVsrbpca/Dnvj5W1Dp us1A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=t0Wc5BL5b8FQMAhj5aGLDV5qkvNFpBbJ01FIXU1V+5U=; b=l5jxzq4oM7msU5hkYG4NQddOeE57hEAeFxI7i3LE5iMmbWWIdqgoLjdqjGlQ26qbbQ V8qSlbERHT6vA5KWDIiumKPFPJmCBeaavXr+vO5V28wTMp1esYueQ9W4udL0wl6zYkHN ZqJDSVshvzvBknNjBim1fhA4MJgrnjmAq302tZsoso9q9xl/b1ITdGval7J1Q8lODpwo xrvqdrfwJcFK6LeHPg6+q26mQrBGROiZcgnDUqvO4+aWB6dTZjHI19CSrZBpirJxUwYL DgLxbVTg0SWMyl/8LD7SgFD0AAo+n9vaJa/Ay6jhuYJscxlT1xkzTjzECzwTr3TjcjT2 rl7g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@verdurent-com.20150623.gappssmtp.com header.s=20150623 header.b=yWRcxS73; 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 8si18815256pfx.43.2019.04.23.22.49.26; Tue, 23 Apr 2019 22:49:41 -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; dkim=pass header.i=@verdurent-com.20150623.gappssmtp.com header.s=20150623 header.b=yWRcxS73; 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 S1729529AbfDXFpS (ORCPT + 99 others); Wed, 24 Apr 2019 01:45:18 -0400 Received: from mail-vk1-f194.google.com ([209.85.221.194]:39637 "EHLO mail-vk1-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726232AbfDXFpR (ORCPT ); Wed, 24 Apr 2019 01:45:17 -0400 Received: by mail-vk1-f194.google.com with SMTP id s80so3758603vke.6 for ; Tue, 23 Apr 2019 22:45:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=verdurent-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=t0Wc5BL5b8FQMAhj5aGLDV5qkvNFpBbJ01FIXU1V+5U=; b=yWRcxS73zxuRuB4oqXAy891+GIvyi9/WMvnmeLlzpFcVSYOEQoTVtT0VjZW8LdlDC6 6wL+rd293kllQ6lWI9SHZROoEkCaCCxKmjxP5MFq+qZvQBEii5N5lXIromh0krFzjERf qMQTaqJVRRDrxqGA5+JZYMwvnlNvZbDR2y5cGaqxQGN41e7Iu+4vMXqddtSlSbpC5JyD rYsRtQET8JeKgbrBlMYMA4ypGrOmPSwtRJOFHgP2TeWakWnjjWtipk0Siec7UUp4JATr 6EWDuLbnzhrkSxVsilSD6OEoHaglAtTk6iP/WBOGHxQUQtr1LXtTwJp1tHx/1biHvBnR 897w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=t0Wc5BL5b8FQMAhj5aGLDV5qkvNFpBbJ01FIXU1V+5U=; b=C6aZI+GeFNZ6eeGOr/z4KpPMCHwUElYrxqJDJMi1phdAU7BRYmbQLf3dexrWo0CAf/ ue4+DTiWWx1PsZTtdbKe6MCPkuGuzJGQZz+gVcfTh5o31a1rPVvBpHGXkvlsvy834k9/ GLR2yv4gEtF6YHybU8IIDeCNuPSIngKj+C5HzTwEf4LeIayW3CG9DigCSQYvwgu3RGrv eMF6fKETHJyUUqn66jUh8C0R6M3K+iq30g7fvG6mT84XQ9KOwt0isvIiLLjOeOpyHZWq jtXkB208vfsujB+APVBh44BI4GWj9RMJf75sDL7dzgf0PUNCojUUs0402+Tnq9PtGBGr 2usQ== X-Gm-Message-State: APjAAAX0Mdjz3dOsN8PFUdSlXN0ZWPNUpYszWBXKTqh+CseZ1lBfwNhD vNGnfPhfChV4vPDkyOVrfXCY1L8P6KsGSf9HR6DF9w== X-Received: by 2002:a1f:812:: with SMTP id 18mr377332vki.68.1556084716748; Tue, 23 Apr 2019 22:45:16 -0700 (PDT) MIME-Version: 1.0 References: <20190402161256.11044-1-daniel.lezcano@linaro.org> <20190423155208.GC16014@localhost.localdomain> In-Reply-To: <20190423155208.GC16014@localhost.localdomain> From: Amit Kucheria Date: Wed, 24 Apr 2019 11:15:05 +0530 Message-ID: Subject: Re: [PATCH 1/7] thermal/drivers/core: Remove the module Kconfig's option To: Eduardo Valentin Cc: Daniel Lezcano , Zhang Rui , Linux PM list , LKML , Guenter Roeck , Krzysztof Kozlowski , Russell King , Ralf Baechle , Paul Burton , James Hogan , Guan Xuetao , Andrew Morton , Alexey Brodkin , Robert Jarzmik , Arnd Bergmann , Enric Balletbo i Serra , Daniel Mack , "moderated list:ARM PORT" , "open list:MIPS" Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Apr 23, 2019 at 9:22 PM Eduardo Valentin wrote: > > Hello, > > On Tue, Apr 02, 2019 at 06:12:44PM +0200, Daniel Lezcano wrote: > > The module support for the thermal subsystem makes little sense: > > - some subsystems relying on it are not modules, thus forcing the > > framework to be compiled in > > - it is compiled in for almost every configs, the remaining ones > > are a few platforms where I don't see why we can not switch the thermal > > to 'y'. The drivers can stay in tristate. > > - platforms need the thermal to be ready as soon as possible at boot time > > in order to mitigate > > > > Usually the subsystems framework are compiled-in and the plugs are as module. > > > > Remove the module option. The removal of the module related dead code will > > come after this patch gets in or is acked. > > > I remember some buzilla entry around this some time back. > > Rui, do you remember why you made this to be module? > > I dont have strong opinion here, but I would like to see > a better description why we are going this direction rather > than "most people dont use it as module". Was there any particular > specific technical motivation? Speaking for Qualcomm platforms, we want the thermal subsystem available as soon as possible for boot time thermal mitigation since faster boot times equals hotter cpus. Also the dependency on cpufreq subsystem due to the cpufreq cooling device would be simplified with this. In fact, I now have a follow on patch to move thermal init earlier than fs_initcall since we'd now not wait on modules to be available. /Amit