netdev - Re: [PATCH 0/4] dt-bindings: imx: add nvmem property

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: <ecc8cee6-e890-278e-2916-e7fd45276e6f@pengutronix.de>
Date:   Thu, 24 Mar 2022 12:16:58 +0100
From:   Ahmad Fatoum <a.fatoum@...gutronix.de>
To:     Uwe Kleine-König <u.kleine-koenig@...gutronix.de>,
        "Peng Fan (OSS)" <peng.fan@....nxp.com>
Cc:     linux-arm-kernel@...ts.infradead.org, devicetree@...r.kernel.org,
        ulf.hansson@...aro.org, Peng Fan <peng.fan@....com>,
        netdev@...r.kernel.org, s.hauer@...gutronix.de,
        linux-mmc@...r.kernel.org, qiangqing.zhang@....com,
        linux-kernel@...r.kernel.org, linux-can@...r.kernel.org,
        robh+dt@...nel.org, mkl@...gutronix.de, linux-imx@....com,
        kernel@...gutronix.de, kuba@...nel.org, krzk+dt@...nel.org,
        pabeni@...hat.com, shawnguo@...nel.org, davem@...emloft.net,
        wg@...ndegger.com, festevam@...il.com,
        Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
Subject: Re: [PATCH 0/4] dt-bindings: imx: add nvmem property

Hi,

On 24.03.22 12:11, Uwe Kleine-König wrote:
> I'd rather not have that in an official binding as the syntax is
> orthogonal to status = "..." but the semantic isn't. Also if we want
> something like that, I'd rather not want to adapt all bindings, but
> would like to see this being generic enough to be described in a single
> catch-all binding.

Cc += Srini who maintains the NVMEM bindings.

> I also wonder if it would be nicer to abstract that as something like:
> 
> 	/ {
> 		fuse-info {
> 			compatible = "otp-fuse-info";
> 
> 			flexcan {
> 				devices = <&flexcan1>, <&flexcan2>;
> 				nvmem-cells = <&flexcan_disabled>;
> 				nvmem-cell-names = "disabled";
> 			};
> 
> 			m7 {
> 				....
> 			};
> 		};
> 	};
> 
> as then the driver evaluating this wouldn't need to iterate over the
> whole dtb but just over this node. But I'd still keep this private to
> the bootloader and not describe it in the generic binding.

I like this, but being for bootloader consumption only doesn't mean that
this shouldn't be documented upstream. It's fine to have the binding,
even if Linux isn't expected to implement it.

Cheers,
Ahmad

> 
> Just my 0.02€
> Uwe


-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |