public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Brian Masney <bmasney@redhat.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Bjorn Andersson <quic_bjorande@quicinc.com>,
	Eric Chanudet <echanude@redhat.com>,
	Ninad Naik <quic_ninanaik@quicinc.com>,
	andersson@kernel.org, konrad.dybcio@linaro.org,
	robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
	conor+dt@kernel.org, linux-arm-msm@vger.kernel.org,
	devicetree@vger.kernel.org, quic_psodagud@quicinc.com,
	quic_kprasan@quicinc.com, quic_ymg@quicinc.com,
	kernel@quicinc.com
Subject: Re: [PATCH] arm64: dts: qcom: sa8775p: Add new memory map updates to SA8775P
Date: Mon, 22 Jan 2024 08:45:51 -0500	[thread overview]
Message-ID: <Za5xj8S3Gs7N-UUc@x1> (raw)
In-Reply-To: <CAA8EJppLNFReZn1HK_radSkKkf5L584fx3FCuqG0FoUt4+H=nw@mail.gmail.com>

Hi Dmitry,

On Fri, Jan 19, 2024 at 10:35:43PM +0200, Dmitry Baryshkov wrote:
> This kind of change sets a very bad precedent. This way old kernels
> become incompatible with the updated firmware. For me it looks like
> Linux kernel suddenly being unable to boot after the BIOS upgrade.
> Generally memory map updates should be disallowed after the board hits
> the production and the DT is published and merged. There can be other
> users of DT. BSD systems, U-Boot. We spend sensible efforts in making
> sure that DT is an ABI: newer kernel remain compatible with older DT
> files. We expect the same kind of efforts from device manufacturers.
> 
> I think unless there is a good reason, the memory map update should be
> reverted on the Qualcomm side as a breaking change.
> If this kind of update is absolutely necessary, it might be better to
> define a new set of board files utilising the new memory map, marking
> existing DT files as legacy.

This is on a development board that's not in production yet, so
personally I think this change is fine. It's in all of our best
interests to have SoC vendors push their code upstream early, even if
it means that later on we need to make memory map changes like this.

Once this is in production, then I agree with you that changes like
this should be avoided if possible.

Brian


  reply	other threads:[~2024-01-22 13:45 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-18 15:57 [PATCH] arm64: dts: qcom: sa8775p: Add new memory map updates to SA8775P Ninad Naik
2024-01-18 20:28 ` Brian Masney
2024-01-23  8:25   ` Krzysztof Kozlowski
2024-01-18 23:58 ` Eric Chanudet
2024-01-19 19:11   ` Bjorn Andersson
2024-01-19 20:35     ` Dmitry Baryshkov
2024-01-22 13:45       ` Brian Masney [this message]
2024-01-22 20:02         ` Bjorn Andersson
2024-01-23  0:41           ` Brian Masney
2024-01-23  2:58           ` Trilok Soni
2024-01-23  6:23             ` Dmitry Baryshkov
2024-01-23 16:02               ` Bjorn Andersson
2024-01-23 16:53                 ` Dmitry Baryshkov
2024-01-25  6:05               ` Trilok Soni
2024-01-25  9:53                 ` Konrad Dybcio
2024-01-22 21:15         ` Dmitry Baryshkov
2024-01-19 23:14     ` Eric Chanudet
2024-01-23  8:26 ` Krzysztof Kozlowski
2024-01-23 10:15   ` Ninad Naik

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=Za5xj8S3Gs7N-UUc@x1 \
    --to=bmasney@redhat.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=echanude@redhat.com \
    --cc=kernel@quicinc.com \
    --cc=konrad.dybcio@linaro.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=quic_bjorande@quicinc.com \
    --cc=quic_kprasan@quicinc.com \
    --cc=quic_ninanaik@quicinc.com \
    --cc=quic_psodagud@quicinc.com \
    --cc=quic_ymg@quicinc.com \
    --cc=robh+dt@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