From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alexander Graf Date: Sun, 6 Nov 2016 05:27:25 -0500 Subject: [U-Boot] [PATCH v3 3/3] bcm2835: Reserve the spin table in efi memory map In-Reply-To: <991fd3a7-1af5-a71d-a730-dfd7b2543bf1@wwwdotorg.org> References: <1478079380-176304-1-git-send-email-agraf@suse.de> <1478079380-176304-4-git-send-email-agraf@suse.de> <991fd3a7-1af5-a71d-a730-dfd7b2543bf1@wwwdotorg.org> Message-ID: <1cb749ec-b41c-ef93-684f-bf1de27095c7@suse.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 05/11/2016 23:07, Stephen Warren wrote: > On 11/02/2016 03:36 AM, Alexander Graf wrote: >> Firmware provides a spin table on the raspberry pi. This table shouldn't >> get overwritten by payloads, so we need to mark it as reserved. > > This is probably fine for now so, > Acked-by: Stephen Warren > > However in the long term I wonder if U-Boot shouldn't find out the spin > table address from the FW-provided DTB, then boot all CPUs into a > spin-table implementation that's provided by U-Boot. That would avoid > having to hard-code the address/size of the spin table code/data in > U-Boot, which in theory at least could change to an arbitrary location > in a future FW release. I think in the long term, it would make much more sense to use PSCI on the RPi3. Then we wouldn't have to worry about any of the above, except for an EL3 reserved memory region that we could also enquire using PSCI. For 32bit systems, yes, probably :). Alex