Received: by 2002:a05:6a10:1a4d:0:0:0:0 with SMTP id nk13csp3692689pxb; Fri, 11 Feb 2022 05:52:07 -0800 (PST) X-Google-Smtp-Source: ABdhPJx2npFEBx6Sp5qtD9wf2ch8Hw+Om0vgmR7RAiVtJJB0j2yrZjRw4kTBz6hbvLhpQm2EDeUS X-Received: by 2002:a63:1954:: with SMTP id 20mr1406876pgz.339.1644587527021; Fri, 11 Feb 2022 05:52:07 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1644587527; cv=none; d=google.com; s=arc-20160816; b=ImF0Mzr01/8iw6nr5cenznN5Y5QQq3BI2cYwFak5EjU6QNq0ZYctZWBZrfQ2UL6GXF QvN0PTe9wsEZvfP2gsrTaJOQJZXqTtuKHICcgy1E9QlYKbuiHwjoTck59QRaf5O3Zya2 KjDBW/G1/ORw6Tgtglk/Nl9gX8jSWRx0ZFLgQY45yEIyaQiWUjkmeqeu9oo1GjpS20h2 TTU/+1Siq3xDqNJWAKi/6vwYyxE9+H/vHl7b0jzze5GYCxp/vj11rZNbIQpRAZKMDRBq XgEoSPY2iq+BBdT9SIpjZkaHPEBxc/LoqCTz3lANLoaieNAlaWNw+vkEv6rrpNgnUIHD MRDg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=tX9YbbK4wZDYd/1rJF+Fsl9cu8MwUvaAy3wkrzRgdck=; b=WEzpLmStCqHvps96wkgFiHkVcOt1NZE6gNeghN1oC2bIC98YuXMiXu6XPK5tKrdcpo nvsS95wp9yQ8aqnA7OAIpzJd9DoLjakGlHUfHyUTPbUZDlNcslfCHhM2RUQDHe0viC2h 0qL/LwXaBQ7hbBGFVqiaprKb4BAEOAI//QTP+5DqdxUsWtVSvtcx6N2fYvm/9OVhQD1N wRGmlbpv5bjWEV81rXHfk/N0oknUq4TKFaV7CiT2EmPpKVM/wJL6bEFgZKtbSv2Gstrk VLkER24PqOEw5YJ/7Rg07PiYiYbWL3V3/jnIX7N4J+B/5ExMWpH1IGd81BcwJxxl8MOe GoPw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b=EYhftBej; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id m10si2682825pls.598.2022.02.11.05.51.52; Fri, 11 Feb 2022 05:52:06 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b=EYhftBej; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1350424AbiBKNG0 (ORCPT + 99 others); Fri, 11 Feb 2022 08:06:26 -0500 Received: from mxb-00190b01.gslb.pphosted.com ([23.128.96.19]:40990 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1350401AbiBKNGP (ORCPT ); Fri, 11 Feb 2022 08:06:15 -0500 Received: from mail-lj1-x22f.google.com (mail-lj1-x22f.google.com [IPv6:2a00:1450:4864:20::22f]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 6241DF3E; Fri, 11 Feb 2022 05:06:14 -0800 (PST) Received: by mail-lj1-x22f.google.com with SMTP id h18so8524888lja.13; Fri, 11 Feb 2022 05:06:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=tX9YbbK4wZDYd/1rJF+Fsl9cu8MwUvaAy3wkrzRgdck=; b=EYhftBejqCnc8+Xc8fkkRb1kgXnwY9DZicwijRuZEMwqwLctCSRnWT3czltZ1Oe7Vi RRYXVlpSymNMkx85YtOHjmuCrs4Rw1nSL9N5I1CLdYMj78PYUCVl0FtUgXFjgJTHx9TZ HQdK1nrxeRo/nseosHSxIJdwwgSttMcTBwBK7BVq95O65zEO9lyQT5Ko+tFf1bS7VG3S OQuJYPPe3DOGMSto56n04z06eUyBmXcgu4jxGd9GtAbNNXNIKURGrny0I2FNPa2g2E7a O6NltEOPRVDIM2iBU+78Qa4FgjfDX3ggUzOcjIBgqXnASsQX3Yep9azAufzehByV5hAI a6KQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=tX9YbbK4wZDYd/1rJF+Fsl9cu8MwUvaAy3wkrzRgdck=; b=sxdRVAgcay7x932FOLqpu8IKS8tJAH61RI0iTGIyIXQWg1hum1sIML9xRurSn5ttAh 52tNGjhsU3XvsX7h1hCdq8cpqvJysvskI8RlWQVlstxrsSnCWZ51+PcOyq33iw551C4a zuvA0N9cT4ftutDU2Tk1Ss/4ev3AcaZZknsRqKvYxKKGMLKHTcNR4ctp4sAnqQ8ElATF th/xTFKm7btdFLhF3q3enxYT/hZZX04sWUDbDcP9hJEFtzSE+R8q2DupNquYSzHB6hA1 XGY+fcdr6kjVw3MRHVxJ7a7VfJKIiLB0EvnLzK9Hl9/ZJLLyk7dDO8ajmoHaipWrsw71 0iww== X-Gm-Message-State: AOAM5336HN8ixAEcr/M25PWO1UF7TIBDyB1FaecmB3CEV+zkZiykNPFT FvbUCF6hrl0nOHRQ8IhNWZc= X-Received: by 2002:a2e:9d96:: with SMTP id c22mr976389ljj.293.1644584772698; Fri, 11 Feb 2022 05:06:12 -0800 (PST) Received: from localhost.lan (ip-194-187-74-233.konfederacka.maverick.com.pl. [194.187.74.233]) by smtp.gmail.com with ESMTPSA id b13sm3111094lfv.175.2022.02.11.05.06.11 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 11 Feb 2022 05:06:12 -0800 (PST) From: =?UTF-8?q?Rafa=C5=82=20Mi=C5=82ecki?= To: Srinivas Kandagatla , Rob Herring Cc: Krzysztof Kozlowski , Florian Fainelli , Hauke Mehrtens , bcm-kernel-feedback-list@broadcom.com, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, =?UTF-8?q?Rafa=C5=82=20Mi=C5=82ecki?= Subject: [PATCH V2 3/3] nvmem: core: add cell name based matching of DT cell nodes Date: Fri, 11 Feb 2022 14:05:54 +0100 Message-Id: <20220211130554.13062-4-zajec5@gmail.com> X-Mailer: git-send-email 2.34.1 In-Reply-To: <20220211130554.13062-1-zajec5@gmail.com> References: <20220124160300.25131-1-zajec5@gmail.com> <20220211130554.13062-1-zajec5@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_ENVFROM_END_DIGIT, FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Rafał Miłecki When adding NVMEM cells defined by driver it's important to match them with DT nodes that specify matching names. That way other bindings & drivers can reference such "dynamic" NVMEM cells. Signed-off-by: Rafał Miłecki --- drivers/nvmem/core.c | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) diff --git a/drivers/nvmem/core.c b/drivers/nvmem/core.c index 53a43d843743..a891449c52f1 100644 --- a/drivers/nvmem/core.c +++ b/drivers/nvmem/core.c @@ -499,6 +499,31 @@ static int nvmem_cell_info_to_nvmem_cell_entry(struct nvmem_device *nvmem, return 0; } +/** + * nvmem_find_cell_of_node() - Find DT node matching nvmem cell + * + * @nvmem: nvmem provider + * @name: nvmem cell name + * + * Runtime created nvmem cells (those not coming from DT) may still need to be + * referenced in DT. This function allows finding DT node referencing nvmem cell + * by its name. Such a DT node can be then used by nvmem consumers. + * + * Return: NULL or pointer to DT node + */ +static struct device_node *nvmem_find_cell_of_node(struct nvmem_device *nvmem, + const char *name) +{ + struct device_node *child; + + for_each_child_of_node(nvmem->dev.of_node, child) { + if (!strcmp(child->name, name)) + return child; + } + + return NULL; +} + /** * nvmem_add_cells() - Add cell information to an nvmem device * @@ -532,6 +557,8 @@ static int nvmem_add_cells(struct nvmem_device *nvmem, goto err; } + cells[i]->np = nvmem_find_cell_of_node(nvmem, cells[i]->name); + nvmem_cell_entry_add(cells[i]); } -- 2.34.1