Message-ID: <d2af0b0c-718a-a625-3630-05631d0e310c@quicinc.com>
Date:   Fri, 3 Feb 2023 13:50:34 +0530
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101
 Thunderbird/91.13.1
Subject: Re: [PATCH v5 1/2] dt-bindings: ramoops: Add support to get the
 region dynamically
Content-Language: en-US
To:     Rob Herring <robh@kernel.org>
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>
References: <1675330081-15029-1-git-send-email-quic_mojha@quicinc.com>
 <20230202235916.GA2931100-robh@kernel.org>
From:   Mukesh Ojha <quic_mojha@quicinc.com>
In-Reply-To: <20230202235916.GA2931100-robh@kernel.org>
Content-Type: text/plain; charset="UTF-8"; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk


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.

-Mukesh