From: Rob Herring <robh@kernel.org>
To: Mukesh Ojha <quic_mojha@quicinc.com>
Cc: linux-hardening@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
keescook@chromium.org, tony.luck@intel.com, gpiccoli@igalia.com,
krzysztof.kozlowski+dt@linaro.org, corbet@lwn.net
Subject: Re: [PATCH v5 1/2] dt-bindings: ramoops: Add support to get the region dynamically
Date: Fri, 3 Feb 2023 08:59:38 -0600 [thread overview]
Message-ID: <CAL_JsqKV6EEpsDNdj1BTN6nODb=hsHkzsdkCzzWwnTrygn0K-A@mail.gmail.com> (raw)
In-Reply-To: <d2af0b0c-718a-a625-3630-05631d0e310c@quicinc.com>
On Fri, Feb 3, 2023 at 2:20 AM Mukesh Ojha <quic_mojha@quicinc.com> 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
prev parent reply other threads:[~2023-02-03 14:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 9:28 [PATCH v5 1/2] dt-bindings: ramoops: Add support to get the region dynamically Mukesh Ojha
2023-02-02 9:28 ` [PATCH v5 2/2] pstore/ram: Rework logic for detecting ramoops Mukesh Ojha
2023-02-14 13:44 ` Mukesh Ojha
2023-02-02 23:59 ` [PATCH v5 1/2] dt-bindings: ramoops: Add support to get the region dynamically Rob Herring
2023-02-03 8:20 ` Mukesh Ojha
2023-02-03 14:59 ` Rob Herring [this message]
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='CAL_JsqKV6EEpsDNdj1BTN6nODb=hsHkzsdkCzzWwnTrygn0K-A@mail.gmail.com' \
--to=robh@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=gpiccoli@igalia.com \
--cc=keescook@chromium.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_mojha@quicinc.com \
--cc=tony.luck@intel.com \
/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).