devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
	"Peng Fan (OSS)" <peng.fan@oss.nxp.com>
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	ulf.hansson@linaro.org, Peng Fan <peng.fan@nxp.com>,
	netdev@vger.kernel.org, s.hauer@pengutronix.de,
	linux-mmc@vger.kernel.org, qiangqing.zhang@nxp.com,
	linux-kernel@vger.kernel.org, linux-can@vger.kernel.org,
	robh+dt@kernel.org, mkl@pengutronix.de, linux-imx@nxp.com,
	kernel@pengutronix.de, kuba@kernel.org, krzk+dt@kernel.org,
	pabeni@redhat.com, shawnguo@kernel.org, davem@davemloft.net,
	wg@grandegger.com, festevam@gmail.com,
	Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Subject: Re: [PATCH 0/4] dt-bindings: imx: add nvmem property
Date: Thu, 24 Mar 2022 12:16:58 +0100	[thread overview]
Message-ID: <ecc8cee6-e890-278e-2916-e7fd45276e6f@pengutronix.de> (raw)
In-Reply-To: <20220324111104.cd7clpkzzedtcrja@pengutronix.de>

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 |

  reply	other threads:[~2022-03-24 11:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-24  4:20 [PATCH 0/4] dt-bindings: imx: add nvmem property Peng Fan (OSS)
2022-03-24  4:20 ` [PATCH 1/4] dt-bindings: can: fsl,flexcan: introduce " Peng Fan (OSS)
2022-03-24  4:20 ` [PATCH 2/4] dt-bindings: net: fsl,fec: " Peng Fan (OSS)
2022-03-24 14:18   ` Rob Herring
2022-03-24  4:20 ` [PATCH 3/4] dt-bindings: mmc: imx-esdhc: " Peng Fan (OSS)
2022-03-24  4:20 ` [PATCH 4/4] dt-bindings: net: imx-dwmac: " Peng Fan (OSS)
2022-03-24 14:18   ` Rob Herring
2022-03-24 11:11 ` [PATCH 0/4] dt-bindings: imx: add " Uwe Kleine-König
2022-03-24 11:16   ` Ahmad Fatoum [this message]
2022-03-24 12:21   ` Peng Fan
2022-04-01  0:15   ` Rob Herring
2022-04-02  1:52     ` Peng Fan
2022-04-04 15:15       ` Rob Herring

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ecc8cee6-e890-278e-2916-e7fd45276e6f@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=krzk+dt@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-can@vger.kernel.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=mkl@pengutronix.de \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=peng.fan@nxp.com \
    --cc=peng.fan@oss.nxp.com \
    --cc=qiangqing.zhang@nxp.com \
    --cc=robh+dt@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.org \
    --cc=srinivas.kandagatla@linaro.org \
    --cc=u.kleine-koenig@pengutronix.de \
    --cc=ulf.hansson@linaro.org \
    --cc=wg@grandegger.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).