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: <AM9PR04MB8487997B859BFC9ED36D4E59E3019@AM9PR04MB8487.eurprd04.prod.outlook.com>
Date:   Thu, 10 Nov 2022 11:18:00 +0000
From:   Andrei Stefanescu <andrei.stefanescu@....com>
To:     Linus Walleij <linus.walleij@...aro.org>,
        Chester Lin <clin@...e.com>
CC:     Rob Herring <robh+dt@...nel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
        dl-S32 <S32@....com>,
        "linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
        "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "linux-arm-kernel@...ts.infradead.org" 
        <linux-arm-kernel@...ts.infradead.org>,
        Larisa Ileana Grigore <larisa.grigore@....com>,
        Ghennadi Procopciuc <ghennadi.procopciuc@....com>,
        Andreas Färber <afaerber@...e.de>,
        Matthias Brugger <mbrugger@...e.com>
Subject: Re: [PATCH 1/2] dt-bindings: pinctrl: add schema for NXP S32 SoCs

Hi Chester and Linus,

> > > If you have the compatible, surely you know these indexes from that 
> > > compatible string?
> >
> > The nxp,pins property is more like a common language that both kernel 
> > and u-boot can share with. Of course hardcoding indexes can be 
> > achieved as well but that also means the index matrices in both kernel 
> > driver and u-boot driver must be revised and synchronized if new 
> > boards may have different reg and nxp,pins.
> 
> Is it new *BOARDS* that need a new table really or new *SOC:s*?
> 
> I was under the impression that this is per-soc and then it can be derived from the compatible string and should be in the driver.

Yes, the "nxp,pins" property only depends on the SoC. It will not change from board to board(boards using the same SoC). It can be derived from the compatible string.

Best regards,
Andrei

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ