On Fri, Feb 3, 2023 at 2:20 AM Mukesh Ojha <quic_mojha@xxxxxxxxxxx> wrote: > > > > On 2/3/2023 5:29 AM, Rob Herring wrote: > > On Thu, Feb 02, 2023 at 02:58:00PM +0530, Mukesh Ojha wrote: > >> The reserved memory region for ramoops is assumed to be at a > >> fixed and known location when read from the devicetree. This > >> is not desirable in an environment where it is preferred the > >> region to be dynamically allocated at runtime, as opposed to > >> being fixed at compile time. > >> > >> So, update the ramoops binding by using some reserve memory > >> property to allocate the ramoops region dynamically. > > > > Sorry, but I still don't think this belongs in DT as I commented on v4 > Do you mean, we should not even document this here ? or are you against > the size property mentioned in this patch. I don't think dynamic ramoops location should be defined in DT. Rob
