Received: by 2002:a25:c593:0:0:0:0:0 with SMTP id v141csp6390286ybe; Wed, 18 Sep 2019 02:41:07 -0700 (PDT) X-Google-Smtp-Source: APXvYqzLyS4Ph5jg3/c0TZQTUGucAQUl2RCywVgMtwmIZz35LHW5dpbh8/ElNqrUVBCOjgp7UvQ5 X-Received: by 2002:a17:906:4c4c:: with SMTP id d12mr8575537ejw.174.1568799667658; Wed, 18 Sep 2019 02:41:07 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1568799667; cv=none; d=google.com; s=arc-20160816; b=APgHSb+Jm+ucUjP18Yf0eM8zHCPcHb0k8D+EL7eKZUh+f39YHu2n2HTam+BcOJUFCO akluZJQHbCUhJ/hoEf3s5It/9qMv6YXOoVFQOCJKfQNQzkjEhJiykS4losx9nkK1mmO7 FQOjvMXeC3peMkDfXH6J8X0ilszKWURDyf9WH1RkjsaqFzq/TPJ6LgjQj3DGVMzcFH0C c/gWTHnTRN40Opp6Kwg1E0TJuHJADe6S2UAmJzscuKaKLKU5gLmZGjjz1ZpUSt1fG5yl m5WVDCe07oClheGPzmgaqAmBtm46A7XwHHK5OSUd1YmWsrn75pWCXtPcdFYba7c7QJ7S kmqQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=G4hxKX4C+UwHppyagtwLzLYaYfdx3vbwuhfidaVb/nQ=; b=XtRNkkivlXc/Jav79KxaLOCBTvlqlptpG8V86K84FD3OpM3360JBOvVvQNQac2UcjN Uc0W9acJnVtvK0JrqhsZUCIqlaPxMfnFg7MffG51keogULXp6RJv6xV4ViEH3pPd9dTK ecD4t2VInCtGIItzYpWiGQOSkO3xVEnNsq5Nhbx5BHL6B3jsoH68oDhJCfo1R6LHlcMW yhLI6kVyzt4htRJSWumNL9+SHdsVfO865LtrLcACHk+IeMw508aqsGsYWy0xUVw/DA6z E+4Z5peBgcdifr7f0/n7EyFCLlvakZ4y0co7Dv1MfSwH/DhWYkp4xHwxpOMpUa6pmAuw L8VQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=P4FNd9Rh; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id h51si2891743eda.85.2019.09.18.02.40.44; Wed, 18 Sep 2019 02:41:07 -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=@linaro.org header.s=google header.b=P4FNd9Rh; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729915AbfIRJJn (ORCPT + 99 others); Wed, 18 Sep 2019 05:09:43 -0400 Received: from mail-pf1-f196.google.com ([209.85.210.196]:44459 "EHLO mail-pf1-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726491AbfIRJJm (ORCPT ); Wed, 18 Sep 2019 05:09:42 -0400 Received: by mail-pf1-f196.google.com with SMTP id q21so3943390pfn.11 for ; Wed, 18 Sep 2019 02:09:42 -0700 (PDT) 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=G4hxKX4C+UwHppyagtwLzLYaYfdx3vbwuhfidaVb/nQ=; b=P4FNd9RhBzPlUfc1CQgYZsdIp18bxRVlkkoZx0inyMmXAe3hlUh8czZiU3x2EXhloM xvD7raK2qEG2tfvU8zA8qkG9bqGM+K9BtXJeoSLDVDCpiWqJcwOx0JVNpFJqD12g0ALM 3EVMoKO99I+KmpFFCWKFqTQtlLC9xXOML1tFkkzbnLZDxZev7cUSKP6ICbBh4Dlo54XM O1gfiHx0z+t/QTOgydvUKlpylJGKx1yxBHMv8eUX4a93dnJaj/iwojIWEAcxBh/x7zsR cGujmLM//sZv8mFmZmasmc1fV8975M2mO3BtZHVkgGhL2Qcvd1i9qrgWoLMWkbmv0T5a /eLg== 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=G4hxKX4C+UwHppyagtwLzLYaYfdx3vbwuhfidaVb/nQ=; b=BOQv1WgcQXPum5klY2z4K+j31Rzpo6gjaylVX+3/MmvOedoC2T8Qo3kBoizbXP7KE9 ccgIzZ8L83Sl2xVeRHFeuZXsq0pgRvwu6Kse2xLim1g2b9XHZRISHXyIyQxn06mWOI/4 mn3DYEQX0jKbR1eoCDMFm6y8DvyCUdtZOl1RoHfiEZU9mneRAszu+edkAkKnY8oC1EOE FZzVKSvFZq8J2PKLLoRZ7N3h8dlKihHYqZAssh4fHNA0DLQi7x4WKeMwFaW2MWbMpJ77 VD0F9huLSPMJiGroscxcMdL8izJwKWDt3rHkhEcSliL/+KPxYZ8CpXtt5BAbFJgK/vIR 92xw== X-Gm-Message-State: APjAAAUsrFHkAFWjb1GQ8BHx03eqWwSAgDjrNe61WiV/MuQeI2t1S4oP aBv9GJDfGJTUQy3SO4JBvYdf9g== X-Received: by 2002:a63:465c:: with SMTP id v28mr3046498pgk.310.1568797781919; Wed, 18 Sep 2019 02:09:41 -0700 (PDT) Received: from localhost ([122.172.73.172]) by smtp.gmail.com with ESMTPSA id v44sm13954434pgn.17.2019.09.18.02.09.40 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Wed, 18 Sep 2019 02:09:40 -0700 (PDT) Date: Wed, 18 Sep 2019 14:39:38 +0530 From: Viresh Kumar To: Sudeep Holla Cc: Amit Kucheria , linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org, bjorn.andersson@linaro.org, edubezval@gmail.com, agross@kernel.org, tdas@codeaurora.org, swboyd@chromium.org, ilina@codeaurora.org, "Rafael J. Wysocki" , Daniel Lezcano , Zhang Rui , linux-pm@vger.kernel.org Subject: Re: [PATCH 5/5] cpufreq: qcom-hw: Move driver initialisation earlier Message-ID: <20190918090938.b2fj5uk3h6t56t2p@vireshk-mac-ubuntu> References: <20190917093412.GA24757@bogus> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190917093412.GA24757@bogus> User-Agent: NeoMutt/20170609 (1.8.3) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 17-09-19, 10:34, Sudeep Holla wrote: > On Thu, Sep 12, 2019 at 04:02:34AM +0530, Amit Kucheria wrote: > > -device_initcall(qcom_cpufreq_hw_init); > > +postcore_initcall(qcom_cpufreq_hw_init); > > I am fine with core framework initcall pushed to earlier initcall levels > if required, but for individual/platform specific drivers I am not so > happy to see that. > > This goes against the grand plan of single common kernel strategy by > Android moving all drivers as modules. Its been long that I got the opportunity to work on drivers directly, but as far as I remember (which should be incorrect based on your reply) we can still build a driver as module even if it has some postcore_initcall() declarations. They will execute at module insertion. Is that incorrect ? If not, then how is it going to affect android effort ? -- viresh