Received: by 10.192.165.148 with SMTP id m20csp5250215imm; Wed, 9 May 2018 01:48:31 -0700 (PDT) X-Google-Smtp-Source: AB8JxZqMd65Pv0yxmfTm/R9hOIzULIblnhV2vI7x8Pow8KelM/jYt1PQCKglR3DbKr861EXe58ZV X-Received: by 2002:a63:618b:: with SMTP id v133-v6mr34405455pgb.285.1525855711217; Wed, 09 May 2018 01:48:31 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1525855711; cv=none; d=google.com; s=arc-20160816; b=BHrc16kmJEF6tw5neS/K8O5TC9EMQv3mPydBifHXh6urxNn0E3HF4Tf/XxgBFjYYWt y80AQGUOkdoHgvPto5hxHb/FitJ+jABLaQZMkaDPSG/PUyWuZLupmW8JBBQ1pIIoWwJh i+yj+ZJeKPeyA7UYu5rSPjkpjBZfXXf4bcXx74vZBZM+JCdAqawS9mKmLtdKqrLlJh0E 0s9h0nqV2BnGW9Z3Ek4DaV5MNUEmjMRtUPgTBxusfDCIVP8oRAmg8hZRQ3Fvdo3JKWA9 DFUMikOBq77kokM0pE09e3taLs6FjT3qg1t4pM53QA4nFxa2Tzqytg09S7Irgnawy0cj MVzQ== 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:arc-authentication-results; bh=46CM/jq6LkUlbr1XG3KrDYGs3eiPNRBUta61j+ojQfw=; b=qIXbnWozk+QabkK/H8UM1Ps4v1ED1mT+HnSC+TGx+0LKuO0PsOMr3Dd2zi1r1/MU+H xvzkhg4/xl9XNTkHzcFzC7B1bXffRLhk/LL4wQ3ceGRrBGSpI3sFraWsOSgfXRAplmP1 MmpbDiFCaOarAtf4XB2U341s70tnyDhvVunOtI9eBOoFAqu0pj6AqqY0P4DtmiG0z9t4 C1sHzYF367QsltzJrlEF/j+tQ4BOUU1zviIQA+X31QMtJPzYwKRPH4V+LA484mOUmW62 vnTHZ7Uu2QzCPvYlx9Jkh+XsWGkOA6kzOf4cCtSli//vm9NWnRBsLFZCEttSQDUsbFkj Agbw== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@sirena.org.uk header.s=20170815-heliosphere header.b=f/X5ehUl; 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 r2-v6si20655353pgq.157.2018.05.09.01.48.16; Wed, 09 May 2018 01:48:31 -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=fail header.i=@sirena.org.uk header.s=20170815-heliosphere header.b=f/X5ehUl; 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 S934185AbeEIIj2 (ORCPT + 99 others); Wed, 9 May 2018 04:39:28 -0400 Received: from heliosphere.sirena.org.uk ([172.104.155.198]:39288 "EHLO heliosphere.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934035AbeEIIjZ (ORCPT ); Wed, 9 May 2018 04:39:25 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sirena.org.uk; s=20170815-heliosphere; h=In-Reply-To:Content-Type: MIME-Version:References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=46CM/jq6LkUlbr1XG3KrDYGs3eiPNRBUta61j+ojQfw=; b=f/X5ehUlYE5E4fmSgj1Jhbd5C dTHIMbb+Xa1Mhsr5I+yugJoatboJm+/gJsrs4l13LE6TAMVBsBBR+94GYN1Qq2mS/2JcKLCfYdoZG pcGA8jsZfazSTl8t2lGLAIfSgW8gy9YAEukwNy//kuRyq8r1rxaqF6z4FQXdgQ2VDxbHw=; Received: from [2001:268:c0d0:8b7f:9590:ade9:80e5:b26d] (helo=finisterre.ee.mobilebroadband) by heliosphere.sirena.org.uk with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1fGKdA-0007fH-6r; Wed, 09 May 2018 08:39:24 +0000 Received: by finisterre.ee.mobilebroadband (Postfix, from userid 1000) id F39A044007A; Wed, 9 May 2018 09:39:19 +0100 (BST) Date: Wed, 9 May 2018 17:39:19 +0900 From: Mark Brown To: Jorge Ramirez-Ortiz Cc: linux-kernel@vger.kernel.org Subject: Re: [RFC] regmap: allow volatile register writes with cached only read maps Message-ID: <20180509083919.GU13402@sirena.org.uk> References: <1525817169-29233-1-git-send-email-jramirez@baylibre.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="+OVWeTxrbAwQuiek" Content-Disposition: inline In-Reply-To: <1525817169-29233-1-git-send-email-jramirez@baylibre.com> X-Cookie: Advancement in position. User-Agent: Mutt/1.9.5 (2018-04-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --+OVWeTxrbAwQuiek Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, May 09, 2018 at 12:06:09AM +0200, Jorge Ramirez-Ortiz wrote: > Regmap only allows volatile access to registers when the client > supports both reads and writes. >=20 > This commit bypasses that limitation and enables volatile writes to > selected registers while maintaining cached accesses on all reads. For > this, the client does not need to configure the reg_read callback. I don't understand what voltile access means for write only devices. Volatile means that we don't read the cache but go direct to the hardware so if we can't read the hardware that's pretty redundant, a volatile read that goes to the cache is just a default read. --+OVWeTxrbAwQuiek Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAlrys7cACgkQJNaLcl1U h9AobQf9EBlENS1fT0Wg4oW1Rxs8fVvO+tOXm+xCt7VSxAeLVtTaVzWUKRbK7fVh XlgOcFlB36w1S+naDAs0yBhtcniGPcXgOCBobPplSthoYgycvqoFLdmDxdAHRQed cG1PUQJf9iVJy7jhTyJiC2XcmuR21Mm0ooM3baVekXRDlejnmXvlQkA4ov7kkkiu 4Dog73pdpa3SeKWPCNIHlYbwQvJ+YWVvLXvRICVUu5AfxEO+8Vz2wzQ29SZdkSX5 WpqR+mE8h2uUx+BdIb17PC2FSb2bTVwxnpXuRyB9jPD6YVevXgpSE1I1dkwQUyji XOEyQBNV+ZAUFTrK2jo7EiCJ9GfWPA== =1fX7 -----END PGP SIGNATURE----- --+OVWeTxrbAwQuiek--