Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1171193 > unrolled thread
| Started by | Maxime Ripard <maxime.ripard@free-electrons.com> |
|---|---|
| First post | 2015-06-24 10:50 +0200 |
| Last post | 2015-06-24 10:50 +0200 |
| Articles | 1 — 1 participant |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [RFC PATCH v6 2/2] nvmem: Add Vybrid OCOTP and OCROM support Maxime Ripard <maxime.ripard@free-electrons.com> - 2015-06-24 10:50 +0200
| From | Maxime Ripard <maxime.ripard@free-electrons.com> |
|---|---|
| Date | 2015-06-24 10:50 +0200 |
| Subject | Re: [RFC PATCH v6 2/2] nvmem: Add Vybrid OCOTP and OCROM support |
| Message-ID | <pEOxB-4Lc-21@gated-at.bofh.it> |
[Multipart message — attachments visible in raw view] — view raw
Hi,
On Tue, Jun 23, 2015 at 07:14:57PM +0530, Sanchayan Maity wrote:
> +static struct nvmem_config ocotp_config = {
> + .name = "soc_id",
> +};
> +
> +static struct nvmem_config rom_config = {
> + .name = "rom_rev",
> +};
Srinivas, shouldn't we use the DT to setup these names, just like
clock-output-names does for example?
This is very likely to change from one board to another, and defining
a new compatible and/or driver for each board seems a bit fishy.
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
Back to top | Article view | linux.kernel
csiph-web