lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Tue, 27 Jun 2023 17:27:32 +0200
From:   Johan Hovold <johan@...nel.org>
To:     Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>
Cc:     Johan Hovold <johan+linaro@...nel.org>,
        Bjorn Andersson <andersson@...nel.org>,
        Andy Gross <agross@...nel.org>,
        Konrad Dybcio <konrad.dybcio@...aro.org>,
        Rob Herring <robh+dt@...nel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
        Conor Dooley <conor+dt@...nel.org>,
        linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org,
        linux-kernel@...r.kernel.org, Patrick Wildt <patrick@...eri.se>
Subject: Re: [PATCH] arm64: dts: qcom: sc8280xp-pmics: add explicit rtc
 interrupt parent

On Tue, Jun 27, 2023 at 06:54:06PM +0530, Manivannan Sadhasivam wrote:
> On Tue, Jun 27, 2023 at 10:53:06AM +0200, Johan Hovold wrote:
> > Unless explicitly specified the interrupt-parent property is inherited
> > from the parent node on Linux even though this may not be in full
> > compliance with the devicetree specification.
> > 
> > Following commit 2d5cab9232ba ("arm64: dts: qcom: sc8280xp-pmics:
> > Specify interrupt parent explicitly"), add an explicit interrupt parent
> > also for the PMIC RTC node for the benefit of other operating systems
> > which may be confused by this omission.
> > 
> > Note that any such OS must still implement a fallback to the root
> > interrupt domain as most devicetrees are written under the assumption
> > that the interrupt parent is inherited.
> > 
> > Reported-by: Patrick Wildt <patrick@...eri.se>
> > Signed-off-by: Johan Hovold <johan+linaro@...nel.org>
> 
> It is good to encode this in the binding and fix other such instances.

Not sure about that. Perhaps the spec should be updated to match reality
instead... We have many more instances like this, even for this very
SoC, but apparently OpenBSD or whatever OS needs this falls back to the
root domain then.

Changing this for the rtc node for consistency after you changed the
others is a no-brainer, but not sure about trying to do this tree-wide.
We already have too many of these one-line DT cleanups...

Johan

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ