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 phobos.denx.de (phobos.denx.de [85.214.62.61]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id B33C3C43219 for ; Mon, 11 Apr 2022 10:05:10 +0000 (UTC) Received: from h2850616.stratoserver.net (localhost [IPv6:::1]) by phobos.denx.de (Postfix) with ESMTP id 6F2B381DD0; Mon, 11 Apr 2022 12:05:07 +0200 (CEST) Authentication-Results: phobos.denx.de; dmarc=pass (p=reject dis=none) header.from=bootlin.com Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=u-boot-bounces@lists.denx.de Authentication-Results: phobos.denx.de; dkim=pass (2048-bit key; unprotected) header.d=bootlin.com header.i=@bootlin.com header.b="LjGlxuAS"; dkim-atps=neutral Received: by phobos.denx.de (Postfix, from userid 109) id D868B83D07; Mon, 11 Apr 2022 12:05:04 +0200 (CEST) Received: from relay1-d.mail.gandi.net (relay1-d.mail.gandi.net [217.70.183.193]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by phobos.denx.de (Postfix) with ESMTPS id 30C0B8191C for ; Mon, 11 Apr 2022 12:05:01 +0200 (CEST) Authentication-Results: phobos.denx.de; dmarc=pass (p=reject dis=none) header.from=bootlin.com Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=miquel.raynal@bootlin.com Received: (Authenticated sender: miquel.raynal@bootlin.com) by mail.gandi.net (Postfix) with ESMTPSA id 9035F24000C; Mon, 11 Apr 2022 10:04:57 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bootlin.com; s=gm1; t=1649671500; 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=tbYj23K6jfuxj8TlVhbvMc+NFVh8TGna4cbWn2gXvfo=; b=LjGlxuAS+8lEZjBd1Z3IfJcpClR4X7Gistt7AQq+NgaeCMlVCkTK7N5+KG0/9RsLQqjtzO MBYF2FjKIsUzjTx7yHqq2bVhSrzUZ1XFzksIuoFAG9zL4EbBqo/y9Crl6XlbR5Xhw0lCZD P0tmVR9Aap+3OP6SNsDaCFJFQbW0BFfv7TpY7WMqbQB9IpPX0CnUYQyyOANqGAGKN8Nzmx BKnaGzS5FR8PG3XNdgAXFfPUQcTK/9UQoSWAazSoosjnDjyMsrpP1ImZD6SqnmD3OncxUj 0UfN0FHRAxEf4LYFWYBl+pmJoF1vTToDPcehE1xHg+faEzuVwokH05/v+c+JkQ== Date: Mon, 11 Apr 2022 12:04:56 +0200 From: Miquel Raynal To: Srinivas Kandagatla Cc: =?UTF-8?B?UmFmYcWCIE1pxYJlY2tp?= , Richard Weinberger , Vignesh Raghavendra , Tom Rini , linux-mtd@lists.infradead.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, u-boot@lists.denx.de, devicetree@vger.kernel.org, =?UTF-8?B?UmFmYcWCIE1p?= =?UTF-8?B?xYJlY2tp?= Subject: Re: [PATCH 2/2] nvmem: add driver handling U-Boot environment variables Message-ID: <20220411120456.16edb643@xps13> In-Reply-To: References: <20220411085926.10925-1-miquel.raynal@bootlin.com> Organization: Bootlin X-Mailer: Claws Mail 3.17.7 (GTK+ 2.24.32; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: u-boot@lists.denx.de X-Mailman-Version: 2.1.39 Precedence: list List-Id: U-Boot discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: u-boot-bounces@lists.denx.de Sender: "U-Boot" X-Virus-Scanned: clamav-milter 0.103.5 at phobos.denx.de X-Virus-Status: Clean Hi Srinivas, srinivas.kandagatla@linaro.org wrote on Mon, 11 Apr 2022 10:45:53 +0100: > On 11/04/2022 09:59, Miquel Raynal wrote: > > On Wed, 2022-04-06 at 14:32:25 UTC, =3D?utf-8?b?UmFmYcWCIE1pxYJlY2tp?= =3D wrote: =20 > >> From: Rafa=C5=82 Mi=C5=82ecki > >> > >> U-Boot stores its setup as environment variables. It's a list of > >> key-value pairs stored on flash device with a custom header. > >> > >> This commit adds an NVMEM driver that: > >> 1. Provides NVMEM access to environment vars binary data > >> 2. Extracts variables as NVMEM cells > >> > >> It can be used for: > >> 1. Accessing env variables from user-space > >> 2. Reading NVMEM cells by Linux drivers > >> > >> Signed-off-by: Rafa=C5=82 Mi=C5=82ecki =20 > >=20 > > Applied to https://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux.gi= t mtd/next, thanks. =20 >=20 > Hi Miquel, >=20 > Any reason why this nvmem driver is taken via mtd tree? >=20 > This is going to conflict with other nvmem patches that are touching KCon= fig and Makefile Sorry I selected it by mistake. I'll let you take it through nvmem unless there is still something missing on your side? Anyway, it's now dropped from mtd. Thanks, Miqu=C3=A8l