Received: by 2002:a05:6a10:f347:0:0:0:0 with SMTP id d7csp3618885pxu; Tue, 15 Dec 2020 11:07:12 -0800 (PST) X-Google-Smtp-Source: ABdhPJwHWb44ujoYZ2+KpVpgEv6CCwJMqbRxcAUn01Yu3g90S5X7e0XXMtK7Rbz7tNEXcw0oFSt9 X-Received: by 2002:a17:906:b096:: with SMTP id x22mr7034089ejy.471.1608059231769; Tue, 15 Dec 2020 11:07:11 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1608059231; cv=none; d=google.com; s=arc-20160816; b=jThFZUnpYS9l1IuBbf8LdPLlZ+XH/cU0xpf19u+8SZU/pp5x0AafBmo6lGQrJT+4Hf dCieYDX1Gs1GlryJIiF7QBIcTD5FGF7ThtqAC4RdaECaBQTvlMzmt9E4XsmcVe1mJYCD niBXfo4hkeEU/EuTIFQHoL4/AF+vfeMZ6D1BksWTveAVPg3HG0Syz74b19aOZCNCyq5v UVq8k4y2kz03CPRCkacKfqa7ZuKqqdu0fan7DohS6cT5F2P5TqYqNdTK2gXS9uB0rU7j 3c3PP5UzSHlIzemV5dK44Rap3XiF2p9JCamBGELRgvHDOJh1zIa5Gf1gFxwP+wyWsR68 avvg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:user-agent:references:in-reply-to :date:cc:to:from:subject:message-id; bh=V8nxeP62vgX39ieVk+JsZNVOjSjY5Oo3PmjLnsrMpPk=; b=f/OabHDRV2sQqsd+2Z8VXl3F4sJ+Sdue6HWpdkrlwijz431E9NUMmHtGQbchYtcOBM PoQ0XPISsUWPQ+qX9ODCgSl/GDOHruEkR6tmqoXQfAMQ+W2z4JDQ7OUahmfTlB7l6DNj Yr90iiNesQFAJA/GEo9gUPq4mNKmCXs4m5n0N2F15fhw2O7MarCqtMI0h0V7rPGyvUZX oPQIWybjw3kuY2vAA0r5QDhB3W+JQdDoMiEgu/Zn984ZlD4s1K3a2KDZ5N12tUYIuUXm gA4iwdS4KjuoswEwdGEiQVLBZ27f/EXdhw0oKfBmXu4QhY8Fee/sHPnmFG+qyq0pit2C kMfQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id m24si1297921eda.455.2020.12.15.11.06.42; Tue, 15 Dec 2020 11:07:11 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731859AbgLOTCy (ORCPT + 99 others); Tue, 15 Dec 2020 14:02:54 -0500 Received: from mx2.suse.de ([195.135.220.15]:52666 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731771AbgLOTCh (ORCPT ); Tue, 15 Dec 2020 14:02:37 -0500 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id 31A66ACC4; Tue, 15 Dec 2020 19:01:56 +0000 (UTC) Message-ID: <1e0ad098ca7b1c13dbc6602285b77790b9cd54a1.camel@suse.de> Subject: Re: [PATCH 0/6] Expose RPi4'd bootloader configuration From: Nicolas Saenz Julienne To: Catalin Marinas Cc: srinivas.kandagatla@linaro.org, devicetree@vger.kernel.org, bcm-kernel-feedback-list@broadcom.com, linux-rpi-kernel@lists.infradead.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux@armlinux.org.uk, will@kernel.org, robh+dt@kernel.org, tim.gover@raspberrypi.com, phil@raspberrypi.com Date: Tue, 15 Dec 2020 20:01:54 +0100 In-Reply-To: <20201215184407.GA44849@C02TF0J2HF1T.local> References: <20201215155627.2513-1-nsaenzjulienne@suse.de> <20201215184407.GA44849@C02TF0J2HF1T.local> Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="=-33igFDZ5wcGZ+YxGdMIV" User-Agent: Evolution 3.38.2 MIME-Version: 1.0 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --=-33igFDZ5wcGZ+YxGdMIV Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Catalin, On Tue, 2020-12-15 at 18:44 +0000, Catalin Marinas wrote: > On Tue, Dec 15, 2020 at 04:56:20PM +0100, Nicolas Saenz Julienne wrote: > > Soon to be released versions of RPi4's firmware will take of care > > passing their bootloader's configuration to the OS by copying it into > > memory and creating a reserved memory node in the board's DT. In order > > to make use of this information, this series introduces a new generic > > nvmem driver that maps reserved-memory nodes into nvmem devices. > >=20 > > An alternative approach, less nice IMO, would be to create a > > platform-specific 'soc' driver. >=20 > What kind of information is this and how would the kernel use it? Sorry, I wasn't clear enough, the ultimate goal is to use this information = from user-space, through nvmem's sysfs interface. The kernel itself has no use f= or it. Regards, Nicolas --=-33igFDZ5wcGZ+YxGdMIV Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- iQEzBAABCAAdFiEErOkkGDHCg2EbPcGjlfZmHno8x/4FAl/ZCCIACgkQlfZmHno8 x/5EWgf/TGaMzSV0k6I2BL4PJYiyOgo9Uq8iEQR3MAxBBSA9qoCwHPnqjElHIMg6 JsyizxB7068wZfkRFvl3V6qW9BqE+HtJvoeT6yHwNqxcV9E1vqWrg6iWIvVLT1kI POU7D73OsKqjmIc2rjD+VEx5BZckvuGAOAncngk64f2MfUFKr5xCi5oj68jC8fXS s+bWzrgXURYjcZKTkAsiDH6OodzkLMm1OOP/Mpp3y4yN314CebvH7h2TBSXEXiW5 0w5FxD9HndtTWhRX/pANNPmb+8ZhBKgfN2X2dUF2V+jgKHkXsj5Q5dUeYeH28nPl MqfB0uhWKHPwiBc9ocDOC1vCDkd1vQ== =2fYn -----END PGP SIGNATURE----- --=-33igFDZ5wcGZ+YxGdMIV--