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 X-Spam-Level: X-Spam-Status: No, score=-3.8 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 37445C4361B for ; Tue, 15 Dec 2020 18:45:52 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id F24AA22B2D for ; Tue, 15 Dec 2020 18:45:51 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731655AbgLOSp2 (ORCPT ); Tue, 15 Dec 2020 13:45:28 -0500 Received: from mail.kernel.org ([198.145.29.99]:49192 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731267AbgLOSo5 (ORCPT ); Tue, 15 Dec 2020 13:44:57 -0500 Date: Tue, 15 Dec 2020 18:44:07 +0000 From: Catalin Marinas To: Nicolas Saenz Julienne 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 Subject: Re: [PATCH 0/6] Expose RPi4'd bootloader configuration Message-ID: <20201215184407.GA44849@C02TF0J2HF1T.local> References: <20201215155627.2513-1-nsaenzjulienne@suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20201215155627.2513-1-nsaenzjulienne@suse.de> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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. > > An alternative approach, less nice IMO, would be to create a > platform-specific 'soc' driver. What kind of information is this and how would the kernel use it? -- Catalin