Re: [RFC PATCH v1 0/3] device property: Support MAC address in VPD
From: Brian Norris
Date: Fri Aug 31 2018 - 17:28:20 EST
On Fri, Aug 31, 2018 at 09:43:30AM +0100, Srinivas Kandagatla wrote:
> On 31/08/18 02:26, Brian Norris wrote:
> > > Seems to me that nvmem needs to be extended to allow providers to
> > > retrieve and interpret data. Not everything is at some fixed offset and
> > > size. Something like this is valid dts:
> > >
> > > nvmem = <&phandle> "a-string";
> > >
> There has been some discussion on extending nvmem support to MTD and non-DT
> users in https://patchwork.kernel.org/cover/10562365/
> One of the thing which we discussed in this thread is adding compatible
> strings to cells mainly to
> 1> Differentiate between actual cells and partitions for MTD case.
I'm not particularly worried about the MTD case. As I mentioned earlier,
while VPD is stored on flash (and could be exposed as an MTD), coreboot
places these tables in memory, and we currently just read them from
there instead of from flash.
> 2> Allow provider specific bindings for each cell, in VPD instance key
> string & value length could be one them.
I'm not sure we'd need to have a binding for value length -- VPD encodes
the length itself, and for many properties, the length is understood by
both sides anyway (2x6 bytes for a MAC address).
> This means that we would endup adding xlate callback support to the
OK, but that's not in the current series, correct?
> AFAIU, From consumer side old bindings should still work!
I'm still trying to wrap my head around all the existing and proposed
behaviors of nvmem, but I see a few things lacking (IIUC):
(1) for the new "lookup" method, you would only support a single MAC
address, identified by looking up for "mac-address" -- this means
you can't support two devices (e.g., we have systems with VPD
entries for "ethernet_mac0" and "etherent_mac1")
(2) the consumer API isn't very flexible -- it assumes that the data you
read out of an NVMEM cell is directly usable as a MAC address; this
fails for VPD, because VPD uses ASCII encoding. To resolve this,
you'd need the consumer/provider relationship to know something
about the data type -- to know that we should decode the ASCII
> From non-dt or ACPI side these cells can be parsed by the provider driver
> and add it to the nvmem_config.
I think that might work, except for the above problems. But perhaps I'm
> Does this make sense? Or Did I miss anything obvious ?
> > > But that's pretty uncommon (I can't think of a binding that actually
> > > uses that). Perhaps the provider has an array of keys defined and the
> > > consumer just provides the index.
> > In the case of VPD, all keys are 0-terminated strings (there's also a
> > length field, but the key is still 0-terminated), so that scheme could
> > work. (I'm not sure an indexed provider is extremely relevant right now,
> > although it probably could be supported if I expand the of_nvmem
> > retrieval to support a generic of_xlate() override anyway.) The
> > information represented is almost the same as in my proposal, except that:
I forgot about problem (2) above -- NVMEM is not very expressive about
the *type* of information. My proposal makes it explicit that the
provider is presenting MAC addresses. To make a generic VPD NVMEM
provider, I'd need to do ASCII decoding on some fields but not on
> > (a) now I have to give the VPD a phandle -- so far, I've avoided that,
> > as it's just an auto-enumerated device underneath the
> > /firmware/coreboot device (see drivers/firmware/google/vpd.c)
> > (b) this is no longer directly useful to ACPI systems -- I'm not
> > actually sure how (if at all) nvmem provider/consumer is supposed to
> > work there
> > But maybe this isn't really that useful to ACPI, and it's sufficient to
> > just have fwnode_get_mac_address() call of_get_nvmem_mac_address() when
> > we're using DT.
> > > Or we could do '<key>-nvmem = <&phandle>', but parsing that is a bit
> > > more complicated.
> > That doesn't seem to have much advantage to me.