Received: by 2002:a5b:505:0:0:0:0:0 with SMTP id o5csp4898463ybp; Mon, 7 Oct 2019 16:01:25 -0700 (PDT) X-Google-Smtp-Source: APXvYqxA1KW7r75qQsVxJYyDYYWrLQl2m79eArTUrvGZE/sCCncoQXsyxboqI6BcK3vJWm1ImgBd X-Received: by 2002:a50:8961:: with SMTP id f30mr30525580edf.144.1570489285670; Mon, 07 Oct 2019 16:01:25 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1570489285; cv=none; d=google.com; s=arc-20160816; b=eGgCH9FqJh8MHsZqH/2TOqZCMrcA1BudKtxja8dl1XMoIcr1PBE/DdFgPEIkrBXTWx cYgWuXO+gvEpVFMWzS0KO4OyePHDt9vu7kS09mZmYPOaZx3juJmI6LPQS3dpQmN2yJxF VJu5x2Wfw2o1XBN3piWhlt6dr4grnh19BAOl4DIpY3KoK9KL6HL2BMGIbHzBXAVHhhx1 BO8/Oq3KFRg++OmdcZpYDB45YlHEEC79kTDao/JQhIp/wdRM4Tr5mMDpxf2xxe8VLSUE 8E7+9y1ySq/8GiyxeFrovsXI1cMMv8XXG4tVOTKuXtvIPKivbRB+FkFlS27DdOFSDRN7 FCjg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:message-id:date:references :in-reply-to:subject:cc:to:from:dkim-signature; bh=HcljqBtqZ0n7Ky2kGCyvmwQmBy2Uww4x9f71GEl4Z8U=; b=yuTfqK+M6Vmoc/M7feW2hPPHjo3mW3qYaCG54fkjAqXdLbb1Yb5Eq+h22RWXzFDd0X rROgxPDj6HJXHdR93KAA0y8sbHc0kvG0qZ3Ay3RinleeHxOasLnt2BYP9hH+EC+0kTu1 JcL3BgusRLKSybGnNXFVmLj61FVKFTXxfpIwx0pWWa1PhMa9G++V19T4gNCd29DIRDfr FL6hSKi0ygFA/E6r3PzdxiPT5NcuwePQl1Y7nRsbpL1x1cMAmbAKo2kdFzq2jvlVdOKk wzau6icH5im8dFpgXIIdrzT+rbY2RMpDGOTNrRQCCP4JVjXftaPvQOMR6Bwaxh/76kqt gZLQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@baylibre-com.20150623.gappssmtp.com header.s=20150623 header.b=A94WXkxS; 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 x45si9123368edd.388.2019.10.07.16.01.01; Mon, 07 Oct 2019 16:01:25 -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=@baylibre-com.20150623.gappssmtp.com header.s=20150623 header.b=A94WXkxS; 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 S1729575AbfJGW6C (ORCPT + 99 others); Mon, 7 Oct 2019 18:58:02 -0400 Received: from mail-pl1-f195.google.com ([209.85.214.195]:39971 "EHLO mail-pl1-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728980AbfJGW6C (ORCPT ); Mon, 7 Oct 2019 18:58:02 -0400 Received: by mail-pl1-f195.google.com with SMTP id d22so7572527pll.7 for ; Mon, 07 Oct 2019 15:58:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=baylibre-com.20150623.gappssmtp.com; s=20150623; h=from:to:cc:subject:in-reply-to:references:date:message-id :mime-version; bh=HcljqBtqZ0n7Ky2kGCyvmwQmBy2Uww4x9f71GEl4Z8U=; b=A94WXkxSy/iySlIL7pQDbk5PyEHAV56d2+iR4LFGlii5+pbrJhkGI9GamLLoNTp12V g3e9CFHLq2AC728cDVClIDG2UxNJ5N3fH1AfNYALNjvbTpOSGmomeBb3eXQ08eJYoZk6 LU41rYaKI7Zmb1wKEoQWeSRAZ3gyy7X2TzCqPh41wNYsvmoupQFVQLsv8o0uOBqnW001 TNxb1jdGtt62cUx/R+dWLujDN5vi+hdJ/P/yrqpBibd5wr3zkNV+jGHXKk8g1j0fjxcL ShHB6G/+3rJf1OdL2Syq7gxBYqmuuArpeguVvRhkfckQBq3io5FGAOPIrLkybmRobMO9 hkIg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:in-reply-to:references:date :message-id:mime-version; bh=HcljqBtqZ0n7Ky2kGCyvmwQmBy2Uww4x9f71GEl4Z8U=; b=Mg/RbhUVcZGhk3B4kiPG6h6dz17W5H5ueFa5gOuRh+kIavUPChXHQQF2z9BGrQjl6p sGYAWPyAe9wBi8wqRh+gG8wk7L6G5GSB08lOZzxonYm0iLiMsQRKWD1sXCYtbc9kYyy7 qoWN/kOXT3LFzVcQP6iW19vf2RLrU3/AKguLu4xopTHkHDFLaJobQRKQly95RjMRayzw tfoDZSyPeh0hYGIbz7CrunxPij1L5+Hs6WzJe96ZutTMrXsNAMiLG7WOdQhVdwmi8wt3 RepZDKFBIXbrF00mwA++Fo9rN7gN/9ytRtV2SzNXhKyZHotN5OUdKTpyqfH8RDa7lBso hUeA== X-Gm-Message-State: APjAAAW6os73kphcZ9vPl7WjZkGlwV/N05JBRAEWjDkZr+CaNsyn2Bf3 BYD1DOBcvF5n2r7iDZiVUUk3uQ== X-Received: by 2002:a17:902:9a06:: with SMTP id v6mr25829128plp.221.1570489081140; Mon, 07 Oct 2019 15:58:01 -0700 (PDT) Received: from localhost ([2601:602:9200:a1a5:ad34:3a95:9a31:e6bb]) by smtp.gmail.com with ESMTPSA id f62sm16453675pfg.74.2019.10.07.15.57.59 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Mon, 07 Oct 2019 15:58:00 -0700 (PDT) From: Kevin Hilman To: Martin Blumenstingl , Anand Moon Cc: Rob Herring , Mark Rutland , Jerome Brunet , Neil Armstrong , Catalin Marinas , Will Deacon , devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [RFCv1 5/5] arm64/ARM: configs: Change CONFIG_PWM_MESON from m to y In-Reply-To: References: <20191007131649.1768-1-linux.amoon@gmail.com> <20191007131649.1768-6-linux.amoon@gmail.com> Date: Mon, 07 Oct 2019 15:57:59 -0700 Message-ID: <7hsgo4cgeg.fsf@baylibre.com> MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Martin Blumenstingl writes: > On Mon, Oct 7, 2019 at 3:17 PM Anand Moon wrote: > [...] >> diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig >> index c9a867ac32d4..72f6a7dca0d6 100644 >> --- a/arch/arm64/configs/defconfig >> +++ b/arch/arm64/configs/defconfig >> @@ -774,7 +774,7 @@ CONFIG_MPL3115=m >> CONFIG_PWM=y >> CONFIG_PWM_BCM2835=m >> CONFIG_PWM_CROS_EC=m >> -CONFIG_PWM_MESON=m >> +CONFIG_PWM_MESON=y > > some time ago I submitted a similar patch for the 32-bit SoCs > it turned that that pwm-meson can be built as module because the > kernel will run without CPU DVFS as long as the clock and regulator > drivers are returning -EPROBE_DEFER (-517) On 64-bit SoCs, the kernel boots with PWM as a module also, but DVFS only works sometimes, and making it built-in fixes the problem. Actually, it doesn't fix, it just hides the problem, which is likely a race or timeout happening during deferred probing. > did you check whether there's some other problem like some unused > clock which is being disabled at that moment? > I've been hunting weird problems in the past where it turned out that > changing kernel config bits changed the boot timing - that masked the > original problem Right, I would definitely prefer to not make this built-in without a lot more information to *why* this is needed. In figuring that out, we'll probably find the race/timeout that's the root cause. Kevin