From mboxrd@z Thu Jan 1 00:00:00 1970 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 94369C0502F for ; Sun, 28 Aug 2022 14:33:11 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229704AbiH1OdK (ORCPT ); Sun, 28 Aug 2022 10:33:10 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:59384 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229470AbiH1OdI (ORCPT ); Sun, 28 Aug 2022 10:33:08 -0400 Received: from mail.3ffe.de (0001.3ffe.de [IPv6:2a01:4f8:c0c:9d57::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4B4A632DAC; Sun, 28 Aug 2022 07:33:05 -0700 (PDT) Received: from 3ffe.de (0001.3ffe.de [IPv6:2a01:4f8:c0c:9d57::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mail.3ffe.de (Postfix) with ESMTPSA id 8858222D1; Sun, 28 Aug 2022 16:33:03 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=walle.cc; s=mail2022082101; t=1661697183; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=bwtC9ZIuYAB2A3TteH5zPFKqQJ2DrJO4wxsda0FFBrE=; b=KznYoTy9iue5vF7/hSESEctDdioSRs8n4n2hqBIDkzR7gvg4gOF0YLYEo9M5XjBBVFBc/X bU11LaqPWiz4z+BoPkufiLDYa+HiuGL2Sq1Fc3j8sG/eGpvcyWAiEKM8oApVhSkmH4mO8f 8XcTEiX0GMUblPaZ8SNao8Y9aPFl51d8qW7ggOFodL1Uzu1WSo3Yag7EjaYaSZhr93Qsst 5DBd99KMGwJECymKB9uiNax2rIiQ7zZI8UkzAtyWEZFhZ5hir3Fna0Jtg8oZvrZWM5i16h OJE9ct0u+HOyIY5TVijhw2FvVap8jhHovp/qpW8PcVtpFIKSaqkdsDFWtps3bw== MIME-Version: 1.0 Date: Sun, 28 Aug 2022 16:33:03 +0200 From: Michael Walle To: =?UTF-8?Q?Rafa=C5=82_Mi=C5=82ecki?= Cc: Miquel Raynal , Richard Weinberger , Vignesh Raghavendra , Rob Herring , Krzysztof Kozlowski , Srinivas Kandagatla , Shawn Guo , Li Yang , "David S . Miller" , Eric Dumazet , Jakub Kicinski , Paolo Abeni , Frank Rowand , linux-mtd@lists.infradead.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, netdev@vger.kernel.org, Ahmad Fatoum Subject: Re: [PATCH v1 06/14] nvmem: core: introduce NVMEM layouts In-Reply-To: References: <20220825214423.903672-1-michael@walle.cc> <20220825214423.903672-7-michael@walle.cc> User-Agent: Roundcube Webmail/1.4.13 Message-ID: X-Sender: michael@walle.cc Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Am 2022-08-28 16:06, schrieb Rafał Miłecki: > On 25.08.2022 23:44, Michael Walle wrote: >> For now, the content can be >> described by a device tree or a board file. But this only works if the >> offsets and lengths are static and don't change. > > Not really true (see Broadcom's NVRAM and U-Boot's env data). All except those two drivers don't add cells on their own. And for these it is not possible to add non static cells, except in board code maybe. This series make it possible to add this runtime parsing to any NVMEM device. -michael