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]
Message-ID: <febca3a6-9681-4dc5-b254-e011df85a38c@kernel.org>
Date: Sat, 18 Oct 2025 18:50:45 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Kaustabh Chakraborty <kauschluss@...root.org>,
 Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
 Conor Dooley <conor+dt@...nel.org>, Alim Akhtar <alim.akhtar@...sung.com>
Cc: devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
 linux-samsung-soc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 2/6] dt-bindings: soc: samsung: exynos-pmu: allow
 mipi-phy subnode for Exynos7 PMU

On 28/09/2025 19:56, Kaustabh Chakraborty wrote:
> Add Exynos7's PMU compatible to the list of nodes which allow a MIPI
> PHY driver. This helps defining the phy node on SoC DTSIs such as
> exynos7870's as it has a compatibility fallback on Exynos7's PMU (and
> others in future if support is added).
> 
> Signed-off-by: Kaustabh Chakraborty <kauschluss@...root.org>
> ---
>  Documentation/devicetree/bindings/soc/samsung/exynos-pmu.yaml | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/Documentation/devicetree/bindings/soc/samsung/exynos-pmu.yaml b/Documentation/devicetree/bindings/soc/samsung/exynos-pmu.yaml
> index f0fb24156da9b8980dcfd5339ae75f12a71cf6d6..9293c5eeaaedf1704a48c19226d35d183d34fcd1 100644
> --- a/Documentation/devicetree/bindings/soc/samsung/exynos-pmu.yaml
> +++ b/Documentation/devicetree/bindings/soc/samsung/exynos-pmu.yaml
> @@ -172,6 +172,7 @@ allOf:
>                - samsung,exynos5250-pmu
>                - samsung,exynos5420-pmu
>                - samsung,exynos5433-pmu
> +              - samsung,exynos7-pmu

This should be rather exynos7870, unless you are sure that all devices
compatible with exynos7 (see the binding) have it. If that's the case,
please add such details to commit msg, e.g. which devices have it,
except exynos7870.

Best regards,
Krzysztof

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ