devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
To: 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
Cc: linux-kernel@vger.kernel.org, linux@armlinux.org.uk,
	catalin.marinas@arm.com, will@kernel.org, robh+dt@kernel.org,
	tim.gover@raspberrypi.com, phil@raspberrypi.com
Subject: Re: [PATCH 0/6] Expose RPi4'd bootloader configuration
Date: Tue, 15 Dec 2020 17:05:15 +0100	[thread overview]
Message-ID: <2f4968f856bb8d1181079869c0af6306b5cec8e8.camel@suse.de> (raw)
In-Reply-To: <20201215155627.2513-1-nsaenzjulienne@suse.de>

[-- Attachment #1: Type: text/plain, Size: 680 bytes --]

On Tue, 2020-12-15 at 16:56 +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.
> 
> Regards,
> Nicolas

There's a typo in the Subject, it should look like this:

'Expose RPi4's bootloader configuration'

Regards,
Nicolas


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  parent reply	other threads:[~2020-12-15 16:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-15 15:56 [PATCH 0/6] Expose RPi4'd bootloader configuration Nicolas Saenz Julienne
2020-12-15 15:56 ` [PATCH 1/6] dt-bindings: nvmem: Add bindings for rmem driver Nicolas Saenz Julienne
2020-12-15 20:25   ` Rob Herring
2020-12-15 21:16     ` Nicolas Saenz Julienne
2020-12-15 15:56 ` [PATCH 2/6] nvmem: Add driver to expose reserved memory as nvmem Nicolas Saenz Julienne
2020-12-15 15:56 ` [PATCH 3/6] ARM: dts: bcm2711: Add reserved memory template to hold firmware configuration Nicolas Saenz Julienne
2020-12-15 20:27   ` Rob Herring
2020-12-15 15:56 ` [PATCH 4/6] ARM: dts: bcm2711: Expose boot-loader configuration Nicolas Saenz Julienne
2020-12-15 15:56 ` [PATCH 5/6] arm64: defconfig: Enable nvmem's rmem driver Nicolas Saenz Julienne
2020-12-15 15:56 ` [PATCH 6/6] ARM: multi_v7_defconfig: " Nicolas Saenz Julienne
2020-12-15 16:05 ` Nicolas Saenz Julienne [this message]
2020-12-15 18:44 ` [PATCH 0/6] Expose RPi4'd bootloader configuration Catalin Marinas
2020-12-15 19:01   ` Nicolas Saenz Julienne
2020-12-15 19:54     ` Rob Herring
2020-12-15 21:21       ` Nicolas Saenz Julienne

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2f4968f856bb8d1181079869c0af6306b5cec8e8.camel@suse.de \
    --to=nsaenzjulienne@suse.de \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=catalin.marinas@arm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rpi-kernel@lists.infradead.org \
    --cc=linux@armlinux.org.uk \
    --cc=phil@raspberrypi.com \
    --cc=robh+dt@kernel.org \
    --cc=srinivas.kandagatla@linaro.org \
    --cc=tim.gover@raspberrypi.com \
    --cc=will@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).