Received: by 2002:a25:1985:0:0:0:0:0 with SMTP id 127csp4030509ybz; Mon, 20 Apr 2020 14:13:38 -0700 (PDT) X-Google-Smtp-Source: APiQypJQQxfDhYjy8YZf+Znba3x2vFGYzMCXM/CbNUwtKDgcyQ3sNKOkeTypz8QXb3X421aCyJIb X-Received: by 2002:a17:906:1e4a:: with SMTP id i10mr17417218ejj.169.1587417218816; Mon, 20 Apr 2020 14:13:38 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1587417218; cv=none; d=google.com; s=arc-20160816; b=H4z0HmnMht0gnwTlFs64h1rmQNqudDJkAgIPhEt33R7YxDT/kSsDnnYFWoS29eNq0v L2dN8o7Js5/jpOup/ub8lopwWRTUPIENNaGgX01oUUhKa3HgLMkvFeMhRhEQHIt7FN6t bRIBqx7A9P/bLYx5V5xXY56wSYQMS99FPeBeei3WyfvJHkDL51xSRwPI9rZOq57AI+Lc Kx6piJIhdoQwiIiw97cY+5AIIR4gbiSV1m+JcSCVmGw5awgfdjHzjzBCs+8VjQBDYoRc Z4Kt2UjtuLUapsrn2Ntzryi2wM4Ol7gZaH/PctqDd/0AI+Ln6IMx2+K/NfRZiPP0l8IF tH1g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:to:references:message-id :content-transfer-encoding:cc:date:in-reply-to:from:mime-version :subject:dkim-signature; bh=VM/1mpb9W6dJV54ZyNTgXDXYYRn4ff5iJpVvPcwV7tQ=; b=naBDiE7EiBZkhEpsXBt6boDXChPb9x9q/Jj+Omj5i9aJmJkg3u313aGszAxEu1yLxH Iug2ia5L9nlPMq27pbL5lupaXfRwMZW+GhQPb2Pd+6lQteQ4M0HM5hAVgqU3yxnMb1H7 7dHrvlSBPl7MkCDgSanMuWC0PAeodT2s8aMyNqVyK0PYpz8LuX+vqLjkXbtEMvWmrgpD bTk/GHtMvR7pfPLfnJV0s9U1G3Ukuzso7eemmnrsUj0BnItgxydqe4Vt79AHssRPirHd HLlsqCKPd8n0aUqKgTSx0ksj52cidLS1ICE5BU0gRhd7fK1B/jKfpF7C+hzWizlDzEmA fdkQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@goldelico.com header.s=strato-dkim-0002 header.b=V3DbmNB+; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id g26si252046ejr.99.2020.04.20.14.13.16; Mon, 20 Apr 2020 14:13:38 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=fail header.i=@goldelico.com header.s=strato-dkim-0002 header.b=V3DbmNB+; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727804AbgDTVLf (ORCPT + 99 others); Mon, 20 Apr 2020 17:11:35 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57046 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1726758AbgDTVLf (ORCPT ); Mon, 20 Apr 2020 17:11:35 -0400 Received: from mo6-p01-ob.smtp.rzone.de (mo6-p01-ob.smtp.rzone.de [IPv6:2a01:238:20a:202:5301::11]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 927D0C061A0C; Mon, 20 Apr 2020 14:11:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1587417092; s=strato-dkim-0002; d=goldelico.com; h=To:References:Message-Id:Cc:Date:In-Reply-To:From:Subject: X-RZG-CLASS-ID:X-RZG-AUTH:From:Subject:Sender; bh=VM/1mpb9W6dJV54ZyNTgXDXYYRn4ff5iJpVvPcwV7tQ=; b=V3DbmNB+/2OzYcD/ksfoGgU7TCUJp4yy6gYorp2RklGUGtZ4VE9hYISqfMMZ96PLeU bI/JcsnrPG62syMuTnEnhYOVCMrKI45vfQejkc5gi7twVmG/ILKdrxccdFwLwE1EFMY5 mD5zziwKj+jg75hORSUFS2zPOQopCRZamvggfUgA9TPPUDW1kNed7eJM0uy1zYETdzcr XiqE7p7q5vPGj4cu3agEejnMcAF629x057HJqPI3TsTLga2xVS4clfh8sAr9n1qdb/tM AL8JrjW/aR+bLoAUuLHCvXCcr7Mxh/eEuccPcc7enXkm12ZEVqu/z825zgf0ZVYm7Xk/ Ojeg== X-RZG-AUTH: ":JGIXVUS7cutRB/49FwqZ7WcJeFKiMgPgp8VKxflSZ1P34KBj5Qpw97WFDlWeXA4LPg==" X-RZG-CLASS-ID: mo00 Received: from imac.fritz.box by smtp.strato.de (RZmta 46.5.0 DYNA|AUTH) with ESMTPSA id g06d2dw3KLBJF0M (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (curve X9_62_prime256v1 with 256 ECDH bits, eq. 3072 bits RSA)) (Client did not present a certificate); Mon, 20 Apr 2020 23:11:19 +0200 (CEST) Subject: Re: [PATCHv3] w1: omap-hdq: Simplify driver with PM runtime autosuspend Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Content-Type: text/plain; charset=us-ascii From: "H. Nikolaus Schaller" In-Reply-To: <20200420150802.GR37466@atomide.com> Date: Mon, 20 Apr 2020 23:11:18 +0200 Cc: Andreas Kemnade , Evgeniy Polyakov , Greg Kroah-Hartman , Linux Kernel Mailing List , linux-omap , Adam Ford , "Andrew F . Davis" , Vignesh R Content-Transfer-Encoding: quoted-printable Message-Id: References: <20191217004048.46298-1-tony@atomide.com> <7B8C7DD9-095B-48FC-9642-695D07B79E97@goldelico.com> <20200416184638.GI37466@atomide.com> <3197C3F0-DEB9-4221-AFBD-4F2A08C84C4C@goldelico.com> <20200417164340.3d9043d1@aktux> <6430AF54-849E-456B-8DB0-B4478BBDB78D@goldelico.com> <20200417150721.GL37466@atomide.com> <8E062482-5D5D-4837-9980-D6C708DD24D4@goldelico.com> <20200420150802.GR37466@atomide.com> To: Tony Lindgren X-Mailer: Apple Mail (2.3124) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Tony, > Am 20.04.2020 um 17:08 schrieb Tony Lindgren : >=20 > * H. Nikolaus Schaller [200417 21:04]: >> To me it looks as if reading hqd too quickly after = omap_hdq_runtime_resume() >> may be part of the problem, although it is 0.4 seconds between [ = 18.355163] >> and [ 18.745269]. So I am not sure about my interpretation. >>=20 >> A different attempt for interpretation may be that trying to read the >> slave triggers omap_hdq_runtime_resume() just before doing the >> first hdq_read_byte(). >=20 > Hmm so I wonder if adding msleep(100) at the end of > omap_hdq_runtime_resume() might help? I have tried and initially it did boot and work once. But after the second boot/reboot the effect was back. This is something I have observed previously, that the issue is there in ca. 9 or 10 boot attempts. So I would assume some race condition with udev reading the uevent file of the bq27xxx bus client and hence through hdq. I already had noticed some hqd_read activity right after probing success. I had also tried to change pm_runtime_set_autosuspend_delay(, 1000) with no success. And I tried to call omap_hdq_runtime_resume() at the end of probe. The only maybe important observation was when I disabled all kernel modules except *hdq*.ko and *bq27*.ko. Then I did only get an emergency shell so that it is quite similar to the scenario Andreas has tested. With this setup it did work. I then tried to reenable other kernel modules but the result wasn't convincing that it gives a reliable result. So I have still no clear indication when the problem occurs and when not. BR and thanks, Nikolaus