Received: by 10.192.165.156 with SMTP id m28csp1127603imm; Wed, 18 Apr 2018 04:44:31 -0700 (PDT) X-Google-Smtp-Source: AIpwx48V9b2OsDHmRZAdJUDbOVvBRcSmjBoRbjqwzOuhx0zvOIycI8YAGfqMhxloLdeSsJvftRI4 X-Received: by 10.99.127.9 with SMTP id a9mr1498115pgd.347.1524051871229; Wed, 18 Apr 2018 04:44:31 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1524051871; cv=none; d=google.com; s=arc-20160816; b=DatBtDhecsjunc/OtCLCR7FCMG8AoDhf68Q4gFMJvmUDAo7XgYZjuueimoxyzXUf0A THoPLYpcIBWoxPxTgaX2Piz9JxaK037pH6F2G2uU33djlKPV+G+Mkobbbn5rPwV+b4kT d7UoCY0KaysWvzvcVMKlP85MjZY29wvAUG+ve1QocAKZc7V7/fqPfTm8d6IjVWRvNQVh ZNgsQZ3iRZa/6y9A/KysRlOlTufqCtOUyunmhd1rwB6TVpLZd5ftv25UTKsG0iaTyeH2 jKfmT6FTl8jzwj8UYTWUWHlikKbTlFnWtvbLMzRNnweDLjeNky8+5WNlKtRhTpMaoN78 ptdg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:arc-authentication-results; bh=wRfaT6L2hlTOPOH9A41xYxHzaVsn677x0K/qs7kmMQ0=; b=yjbR2H+rZm7itGFLOuYgKpL2TARWzFiAlZia8vr1JfF9JUmzY2AwVhzOnY47Dv8USV 6tGLXueErAoxY3Evq4q7FNcAnVaHOA97aIFRagaHu+iNFd8y3LzIs0ObE70hDhtacpIQ BpB5HO+PZuibdek/1D3/xDnMXeg7xgbT2slmtg0YTB+szm7I9kl9x0i/pfNOeJ4sPoVk Eg5eiko9aoZ70cZJHoWs8jNqEdutRy1uVsm79Ry+OquSy/Rrl2EWpBngtk3qApbtj1vF SQ+AbASwIbHXU1NqJVr5Fj2kHWRyZgzTvxbO0cQmtU1ZOex216ccHyz4Pix/Q80IxqN3 LsoQ== 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id s36-v6si1089141pld.114.2018.04.18.04.44.17; Wed, 18 Apr 2018 04:44: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; 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 S1753993AbeDRLlv (ORCPT + 99 others); Wed, 18 Apr 2018 07:41:51 -0400 Received: from smtp1-g21.free.fr ([212.27.42.1]:27247 "EHLO smtp1-g21.free.fr" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753971AbeDRLlt (ORCPT ); Wed, 18 Apr 2018 07:41:49 -0400 Received: from avionic-0020 (unknown [80.151.56.191]) (Authenticated sender: albeu@free.fr) by smtp1-g21.free.fr (Postfix) with ESMTPSA id 3EAB8B0058D; Wed, 18 Apr 2018 13:41:22 +0200 (CEST) Date: Wed, 18 Apr 2018 13:41:19 +0200 From: Alban To: Srinivas Kandagatla Cc: Alban , linux-kernel@vger.kernel.org, Rob Herring , Mark Rutland , David Woodhouse , Brian Norris , Boris Brezillon , Marek Vasut , Richard Weinberger , Cyrille Pitchen , devicetree@vger.kernel.org, linux-mtd@lists.infradead.org Subject: Re: [PATCH v3 1/3] nvmem: Update the OF binding to use a subnode for the cells list Message-ID: <20180418134119.2e587621@avionic-0020> In-Reply-To: <20180417180040.04f53495@avionic-0020> References: <1521933899-362-1-git-send-email-albeu@free.fr> <1521933899-362-2-git-send-email-albeu@free.fr> <344e0087-7410-aebb-8a66-c6976064df10@linaro.org> <20180417165420.423a691b@avionic-0020> <8c4b48ad-e99e-030a-a4ee-b6df0fa59c79@linaro.org> <20180417180040.04f53495@avionic-0020> X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.30; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/6UANJLWS_b0VD=xXkYsV.zT"; protocol="application/pgp-signature" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --Sig_/6UANJLWS_b0VD=xXkYsV.zT Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Tue, 17 Apr 2018 18:00:40 +0200 Alban wrote: > On Tue, 17 Apr 2018 16:44:01 +0100 > Srinivas Kandagatla wrote: >=20 > > Thanks for explaining, > >=20 > > On 17/04/18 15:54, Alban wrote: =20 > > > This will not only allow reading the calibration data from nvmem, but > > > will also create a partition on the MTD device, which is not acceptab= le. > > > With my proposed binding this would become: > > >=20 > > > flash@0 { > > > #address-cells =3D <1>; > > > #size-cells =3D <1>; > > > compatible =3D "s25sl064a"; > > > reg =3D <0>; > > >=20 > > > nvmem-cells { > > > compatible =3D "nvmem-cells"; > > > #address-cells =3D <1>; > > > #address-cells =3D <1>; > > >=20 > > > calibration: calib@404 { > > > reg =3D <0x404 0x10>; > > > }; > > > }; =20 > >=20 > > Why can't we make nvmem-cells node a nvmem provider in this case? > > Which should work! =20 >=20 > TBH I just copied what have been done to fix the same problem with the > MTD partitions. But yes we could also just extend the current binding > to require a compatible string on each nvmem-cell, which would not > require any code change to support. However this scheme will not work if the device node binding already have subnodes with addresses. The addressing, as specified by #address-cells and #size-cells, might be incompatible or might overlap. Using the nvmem-cells subnode solve this problem. Alban --Sig_/6UANJLWS_b0VD=xXkYsV.zT Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJa1y7gAAoJEHSUmkuduC286NAP/1mYRWkrmms4OOs0JteVDswv xo+aBOqxH2ju4yUUOlkt9VBNmt+HSmHPM+Wn/MEEQXrkY+fgK5ai+sz/RXGgAhu2 aq+5ZrsgDORpHpljPNAYMEmXSAud7lXzKlYBiEn7UiuA1nuJTxKhrsMJ35UQmBx7 A0DJDcDreXJqI09rVja0oU1IESkxZD9Aazl/36rvSrC2ZtOg977oMbagWaNHPhwb 4PGuW1MqVAxfR5dyBsKixiGhz2mLMnpO7sn+EpLoe/jez7OnjEMHKTG9BcrRAu7n /OjjanxuZ/k6ISDXtcoHO5wrIvzdCLmemRXehuQ5OwgLZdKRr5CPmgBsc9Hp+82z XAMJOhAvGl1q4J2bVm3GyNN8HepGwZSp8c0bp6/2ButkHVsFy1fO7qxNS0AcQsMt bIEIEHTmYC/L80h/l8wQQXii3MvtP0SSCCHdoSXyukg2QGIof1WWeXW9VjQ3kp2a 7R4zodG7Px5SWRRuXuHQ+Uw5eYfxiBzRwt1NCyT6tns1cTD95UJhsMkc4kn8k82S sUnkIuGlUIzIYdR9u5ANb7TEoqvnMbLhB0L5EquZKQ9pk/+UD2nbvU8Cdx9reOVQ EaySaKuplXm1a4qASx8PeUw4bP6EAwu6RCxHZ0SlS9EYdgAlNykR2DOTExb8qWng xpgYJQEaCm3JytPF9Kwy =b649 -----END PGP SIGNATURE----- --Sig_/6UANJLWS_b0VD=xXkYsV.zT--