Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 77487C64ED6 for ; Tue, 21 Feb 2023 21:39:00 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229992AbjBUVi7 (ORCPT ); Tue, 21 Feb 2023 16:38:59 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41884 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229839AbjBUVi4 (ORCPT ); Tue, 21 Feb 2023 16:38:56 -0500 Received: from mail-ed1-x52f.google.com (mail-ed1-x52f.google.com [IPv6:2a00:1450:4864:20::52f]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D23DC2DE55; Tue, 21 Feb 2023 13:38:25 -0800 (PST) Received: by mail-ed1-x52f.google.com with SMTP id cq23so22504172edb.1; Tue, 21 Feb 2023 13:38:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20210112; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=g2x4QxJv4nKAQD6nmh3v1P/gvRFcvPZ/+reUMK1IHmk=; b=hvcbbxjHy3yfhZZaSoQ20ukzgEnIfEyrMlnC1c8Mj23mZ7Z3onoLj/8XHMhGA9BGdj 2e55K/WV6r5hQDtRQOvv6Luyw8hQYXkV9vDaxVFsHD77eysOg2nkgkw+/JjpTCkAeFBN lznssBgKnma18h7wVh5jhzY5IReazXSbGL9j8s7utXvSkeXZmD8s6kMSM7EcRgZLCYyG yYnuxUfUfSGSdRy10QjagUJAF3urpw1t3CZN0Gk6ajP79qxMM1PpbRMsSgckdZqlRUJa cllc8OuefC+uCPx2sarqRn+81n7w22uOi37fJj34mGr+UEKjzYlRxX8OQjb0wgqBB63z ZHhA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=g2x4QxJv4nKAQD6nmh3v1P/gvRFcvPZ/+reUMK1IHmk=; b=cGrDUPUYh6tJgtK9uY2LzRprp9wzIpCraYt/681iTtfO+o/0p17YmzY+PiUmDPUUBD kHkd/79eWqzVsVVw9q/wQ5ajhrz0/iM720JAmWvkrZrZCjOu5P6BXfxD8V0Oxz9CLYOt 5UDMWBm26ychWX1vqfj/08n6zjv4176+YLT1c9Q/289E6MGZGf1co5m2fSV9ZW/uONWF siRY0iIUyCIKCBhDsMuoMoLXmyBIJ68HasMFrT1/LHo73fQSKHYaxDQyX8TwBc2EVqA8 VRrF8W71EfsIL79shXLIqy3cVavH/wpfh/MfWVrr2US3v7GOLpx9GDm3/7Ru1wwqytAf Y8/g== X-Gm-Message-State: AO0yUKWi2kvNdDXP89K5xNAVZZLym2lkPP9Xvr5MLW38vhDhE5ZGCrBW VugcCQpSzVqlXXxLhuM3jf5ZrWLohA8EG3JZnzA= X-Google-Smtp-Source: AK7set+WgWx80yG+IPD6BZtc2LM511WxHd/1uNy9RyymaByA5DzDe9ltu/NxF8DAR1dqIEJxGGjio8OxlPTpsYlt4UQ= X-Received: by 2002:a17:907:3d91:b0:8af:2e89:83df with SMTP id he17-20020a1709073d9100b008af2e8983dfmr13559381ejc.6.1677015504149; Tue, 21 Feb 2023 13:38:24 -0800 (PST) MIME-Version: 1.0 References: <20230221145021.31993-1-zajec5@gmail.com> In-Reply-To: <20230221145021.31993-1-zajec5@gmail.com> From: Martin Blumenstingl Date: Tue, 21 Feb 2023 22:38:13 +0100 Message-ID: Subject: Re: [PATCH] nvmem: add explicit config option to read OF fixed cells To: =?UTF-8?B?UmFmYcWCIE1pxYJlY2tp?= Cc: Srinivas Kandagatla , Miquel Raynal , Richard Weinberger , Vignesh Raghavendra , Hector Martin , Sven Peter , Alyssa Rosenzweig , Shawn Guo , Sascha Hauer , Pengutronix Kernel Team , Fabio Estevam , NXP Linux Team , Neil Armstrong , Kevin Hilman , Jerome Brunet , Claudiu Beznea , Matthias Brugger , AngeloGioacchino Del Regno , Andy Gross , Bjorn Andersson , Konrad Dybcio , Heiko Stuebner , Orson Zhai , Baolin Wang , Chunyan Zhang , Maxime Coquelin , Alexandre Torgue , Vincent Shih , Chen-Yu Tsai , Jernej Skrabec , Samuel Holland , Kunihiko Hayashi , Masami Hiramatsu , Michal Simek , Alessandro Zummo , Alexandre Belloni , Evgeniy Polyakov , linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org, asahi@lists.linux.dev, linux-arm-kernel@lists.infradead.org, linux-amlogic@lists.infradead.org, linux-mediatek@lists.infradead.org, linux-arm-msm@vger.kernel.org, linux-rockchip@lists.infradead.org, linux-stm32@st-md-mailman.stormreply.com, linux-sunxi@lists.linux.dev, linux-rtc@vger.kernel.org, =?UTF-8?B?UmFmYcWCIE1pxYJlY2tp?= Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello Rafa=C5=82, On Tue, Feb 21, 2023 at 3:50 PM Rafa=C5=82 Mi=C5=82ecki = wrote: > > From: Rafa=C5=82 Mi=C5=82ecki > > NVMEM subsystem looks for fixed NVMEM cells (specified in DT) by > default. This behaviour made sense in early days before adding support > for dynamic cells. > > With every new supported NVMEM device with dynamic cells current > behaviour becomes non-optimal. It results in unneeded iterating over DT > nodes and may result in false discovery of cells (depending on used DT > properties). I am not familiar with the recent changes around dynamic cells. Is there any discussion/summary that I can read to get up to speed? My main thought is: if there are many "fixed OF cells" implementations and only a few "dynamic" ones - does it make sense to flip the logic and introduce a new "use_dynamic_of_cells" flag instead? Best regards, Martin