Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp556635ybl; Thu, 23 Jan 2020 03:49:27 -0800 (PST) X-Google-Smtp-Source: APXvYqyajRTzNaJgGZehG/cKe4/2nceISuZuqSyxaYBXBEXi6Ea7Hjl9OYJ/kAn4mcFo8TgMeUQu X-Received: by 2002:a05:6830:1e37:: with SMTP id t23mr11264565otr.16.1579780167146; Thu, 23 Jan 2020 03:49:27 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1579780167; cv=none; d=google.com; s=arc-20160816; b=y7hHv8wwki4AXO+bn8R0lr18HESN1qLy6CJOSoR7MEaij6M1ELd/UOersKIFcKtLRf JNn/cCFKbh4K8LixVWQjfWGAturDBt3bE8fhLUBX//oj5MleBRf4P+0dq9H02v/eAxo+ ReZu9LNc9AZxfESrqwVebP9dnQleiAkP5loBN/TqDuvV0v4mDUJJrYixBDoW6eKsUNOA HVuuzvbn/MgPffLvxrWYx2HUriKG/IYe44M+NjZ/B5BU8Scw9ilQBhl+pHwytozYpc0u NV4H+2K+sCOtesypc/6NZ5vZwS3f8Hch4EATHdtNNq/3dxsGjbaQ8S6E6+6+Agncouch SRZg== 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; bh=e++wVnE0ZahsN4n3x7/ve1oStmzjA3GzI9UCyDD4RrQ=; b=P2qsVldWQ2SGuo6ysc6TFfJMU75qGr3ACHJ96knI+b+AvwHJ/B/6c0Q8Yu/zmBsrcO 5XE/u76R+yZI6k9UM2co/tm8cIKMRdeOuLPwkftD+zoW7RjZAmbr4z1tHKTN2Le9ZCsP ruoV0np0a/v03ITRJfH28Pg0kba3zViriA2CGrfTRGk5nvmE+OLS9ABHPKfWB5yLPlpM 5f3ZCu6eo/uFFtrMqoYSeMN8UTvVpSKaULaaRCs0ASN2SKp8pIWJhXrGo4Z8Ca9sU5b8 2ExsySeC0CAGRDiUujmCqz/0h4aV7pHPtetC0G/w5T6lzlwa/dKDxon/GBaiIJvFsgcy O1dw== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id r1si1003435otk.251.2020.01.23.03.49.14; Thu, 23 Jan 2020 03:49:27 -0800 (PST) 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726885AbgAWLsI (ORCPT + 99 others); Thu, 23 Jan 2020 06:48:08 -0500 Received: from foss.arm.com ([217.140.110.172]:38388 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726260AbgAWLsI (ORCPT ); Thu, 23 Jan 2020 06:48:08 -0500 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 0A0FC328; Thu, 23 Jan 2020 03:48:08 -0800 (PST) Received: from localhost (unknown [10.37.6.21]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 7DBF13F6C4; Thu, 23 Jan 2020 03:48:07 -0800 (PST) Date: Thu, 23 Jan 2020 11:48:05 +0000 From: Mark Brown To: Charles Keepax Cc: lee.jones@linaro.org, lgirdwood@gmail.com, linux-kernel@vger.kernel.org, patches@opensource.cirrus.com Subject: Re: [PATCH RESEND 1/2] regulator: arizona-ldo1: Improve handling of regulator unbinding Message-ID: <20200123114805.GA5440@sirena.org.uk> References: <20200122110842.10702-1-ckeepax@opensource.cirrus.com> <20200122131149.GE3833@sirena.org.uk> <20200123092639.GC4098@ediswmail.ad.cirrus.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="ikeVEW9yuYc//A+q" Content-Disposition: inline In-Reply-To: <20200123092639.GC4098@ediswmail.ad.cirrus.com> X-Cookie: ((lambda (foo) (bar foo)) (baz)) User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --ikeVEW9yuYc//A+q Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, Jan 23, 2020 at 09:26:39AM +0000, Charles Keepax wrote: > 3) We could look at doing something in regmap IRQ to change when > it does PM runtime calls, it is regmap doing runtime gets when > drivers remove IRQs that causes the issue. But my accessment was > that what regmap is doing makes perfect sense, so I don't think > this is a good approach. Why do you even care about the errors? It's not like this device is going to get removed in a production system and the primary IRQ will be disabled when the core is removed, this is just something that happens during development isn't it? --ikeVEW9yuYc//A+q Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAl4ph/IACgkQJNaLcl1U h9Arnwf9Fajpy9ImwxaVzbe5ya64UjdSTAQpKU/CPvVZiEmGWUpiiG030wtRUV4E +bxPoRUMTwnre4Q9HVA9hEaHCtLkq7kEqQczdaonVBIg39nZ+rx0HlF7VvHbYiJU JFhoM/LCeWioxrvUjh7+fTKIfSGRYiO7k/Rb51kC3wekFwytP1Xz+eOR2ToNymDb P2v70shC5dCVY/QR527BK2hTxUk41Z8fAgCS/fq0rWHdR+HU8uRCeWMJKVAVokKU q34spGxN2pzlDlBXOdd06VyQlMP3I1UGYpyOytMctKivuNa0Krl0YXNuNnemiu4v qKFiTEbWbLrQqrTvFGMYMfKzWBk4mQ== =9spY -----END PGP SIGNATURE----- --ikeVEW9yuYc//A+q--