[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240415180247696-0700.eberman@hu-eberman-lv.qualcomm.com>
Date: Mon, 15 Apr 2024 18:11:02 -0700
From: Elliot Berman <quic_eberman@...cinc.com>
To: Konrad Dybcio <konrad.dybcio@...aro.org>
CC: Dmitry Baryshkov <dmitry.baryshkov@...aro.org>,
Bjorn Andersson
<andersson@...nel.org>,
Sebastian Reichel <sre@...nel.org>, Rob Herring
<robh@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Conor Dooley <conor+dt@...nel.org>, Vinod Koul <vkoul@...nel.org>,
Andy Yan
<andy.yan@...k-chips.com>,
Lorenzo Pieralisi <lpieralisi@...nel.org>,
"Mark
Rutland" <mark.rutland@....com>,
Bartosz Golaszewski
<bartosz.golaszewski@...aro.org>,
Satya Durga Srinivasu Prabhala
<quic_satyap@...cinc.com>,
Melody Olvera <quic_molvera@...cinc.com>,
Shivendra Pratap <quic_spratap@...cinc.com>,
<devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>,
Florian Fainelli <florian.fainelli@...adcom.com>,
<linux-pm@...r.kernel.org>, <linux-arm-msm@...r.kernel.org>
Subject: Re: [PATCH v2 4/4] arm64: dts: qcom: Add PSCI SYSTEM_RESET2 types
for qcm6490-idp
On Mon, Apr 15, 2024 at 09:42:40PM +0200, Konrad Dybcio wrote:
>
>
> On 4/15/24 02:32, Elliot Berman wrote:
> > On Mon, Apr 15, 2024 at 02:13:29AM +0300, Dmitry Baryshkov wrote:
> > > On Sun, 14 Apr 2024 at 22:32, Elliot Berman <quic_eberman@...cinc.com> wrote:
> > > >
> > > > Add nodes for the vendor-defined system resets. "bootloader" will cause
> > > > device to reboot and stop in the bootloader's fastboot mode. "edl" will
> > > > cause device to reboot into "emergency download mode", which permits
> > > > loading images via the Firehose protocol.
> > > >
> > > > Co-developed-by: Shivendra Pratap <quic_spratap@...cinc.com>
> > > > Signed-off-by: Shivendra Pratap <quic_spratap@...cinc.com>
> > > > Signed-off-by: Elliot Berman <quic_eberman@...cinc.com>
> > > > ---
> > > > arch/arm64/boot/dts/qcom/qcm6490-idp.dts | 5 +++++
> > > > 1 file changed, 5 insertions(+)
> > > >
> > > > diff --git a/arch/arm64/boot/dts/qcom/qcm6490-idp.dts b/arch/arm64/boot/dts/qcom/qcm6490-idp.dts
> > > > index e4bfad50a669..a966f6c8dd7c 100644
> > > > --- a/arch/arm64/boot/dts/qcom/qcm6490-idp.dts
> > > > +++ b/arch/arm64/boot/dts/qcom/qcm6490-idp.dts
> > > > @@ -126,6 +126,11 @@ debug_vm_mem: debug-vm@...00000 {
> > > > };
> > > > };
> > > >
> > > > + psci {
> > >
> > > Please use a label instead. Otherwise it looks as if you are adding
> > > new device node.
> > >
> >
> > Right. Fixed for the next revision.
>
> Are you guys planning to make this sorta ABI-like?
>
> If so (which would be greatly appreciated by the way..), perhaps you
> could stick these magic values in dt-bindings and give them cool names
>
> FWIW DEN0022 (my second-favorite book) suggests these values are almost
> totally vendor-defined, so if I were Qualcomm, I'd take the creative
> liberty to come up with a set of numbers and never ever ever change
> them
This is my goal as well. I'd like to keep the magic values out of
dt-bindings until we get the vendor SYSTEM_RESET2 spread across more
devices, as things might need a bit of settling. Since having stable
vendor reset2 is (IMO) primarily a benefit to Qualcomm, I expect this
will happen naturally.
Powered by blists - more mailing lists