linux-kernel - Re: [PATCH 1/2] dt-bindings: memory-controller: Document rev c.1.5 compatible

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] [day] [month] [year] [list]

Message-ID: <2e33t7ft5ermsfr7c4ympxrn6l5sqdef3wml4hlbnhdupoouwj@gfjpbmowjadi>
Date: Wed, 18 Dec 2024 12:37:59 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Florian Fainelli <florian.fainelli@...adcom.com>
Cc: linux-arm-kernel@...ts.infradead.org, Rob Herring <robh@...nel.org>, 
	Conor Dooley <conor+dt@...nel.org>, 
	Broadcom internal kernel review list <bcm-kernel-feedback-list@...adcom.com>, 
	"open list:MEMORY CONTROLLER DRIVERS" <linux-kernel@...r.kernel.org>, 
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" <devicetree@...r.kernel.org>
Subject: Re: [PATCH 1/2] dt-bindings: memory-controller: Document rev c.1.5
 compatible

On Tue, Dec 17, 2024 at 11:44:38AM -0800, Florian Fainelli wrote:
> Document the revision c.1.5 compatible string that is present on newer
> Broadcom STB memory controllers (74165 and onwards).
> 
> Signed-off-by: Florian Fainelli <florian.fainelli@...adcom.com>
> ---
>  .../bindings/memory-controllers/brcm,brcmstb-memc-ddr.yaml       | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/Documentation/devicetree/bindings/memory-controllers/brcm,brcmstb-memc-ddr.yaml b/Documentation/devicetree/bindings/memory-controllers/brcm,brcmstb-memc-ddr.yaml
> index 4b072c879b02..99d79ccd1036 100644
> --- a/Documentation/devicetree/bindings/memory-controllers/brcm,brcmstb-memc-ddr.yaml
> +++ b/Documentation/devicetree/bindings/memory-controllers/brcm,brcmstb-memc-ddr.yaml
> @@ -29,6 +29,7 @@ properties:
>            - brcm,brcmstb-memc-ddr-rev-c.1.2
>            - brcm,brcmstb-memc-ddr-rev-c.1.3
>            - brcm,brcmstb-memc-ddr-rev-c.1.4
> +          - brcm,brcmstb-memc-ddr-rev-c.1.5

You should use v2.1 fallback and drop driver patch. Or explain in
commit briefly why different approach is suitable.

Best regards,
Krzysztof