From: Srinivas Kandagatla <email@example.com> To: Vadym Kochan <firstname.lastname@example.org> Cc: email@example.com, Greg Kroah-Hartman <firstname.lastname@example.org>, Taras Chornyi <email@example.com> Subject: Re: [PATCH v2 2/2] nvmem: add ONIE NVMEM cells support Date: Mon, 15 Jun 2020 12:06:11 +0100 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <20200605105351.GA1118@plvision.eu> On 05/06/2020 11:53, Vadym Kochan wrote: >> One of the example is atmel eeprom (at24), but there might be different >> devices. >> >> But can you please explain what is the technical/conceptual issue with >> this approach ? >> >> Thanks, > I just I'd like to clarify if there is a way it can be acceptable. The > problem is that there is TLV format which might be used on any nvmem > device which contains for example mac address which needs to be exposed > as nvmem cell. If to populate cells via nvmem_config then anyway I need > to parse these cells from the "target" nvmem device. As a first step this need to be part of the provider logic to parse this before nvmem provider is registered. If there are more users for such parsing, we can think of adding some level of parsing to nvmem core itself. Hope this answers your query. Thanks, srini
next prev parent reply other threads:[~2020-06-15 11:06 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-29 23:04 [PATCH v2 0/2] nvmem: add ONIE NVMEM cells provider Vadym Kochan 2020-05-29 23:04 ` [PATCH v2 1/2] nvmem: core: allow to register cells for existing device Vadym Kochan 2020-05-29 23:04 ` [PATCH v2 2/2] nvmem: add ONIE NVMEM cells support Vadym Kochan 2020-06-01 8:50 ` Srinivas Kandagatla 2020-06-01 9:03 ` Vadym Kochan 2020-06-01 9:13 ` Srinivas Kandagatla 2020-06-01 10:27 ` Vadym Kochan 2020-06-05 10:53 ` Vadym Kochan 2020-06-15 11:06 ` Srinivas Kandagatla [this message] 2020-08-14 11:56 ` Vadym Kochan
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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [PATCH v2 2/2] nvmem: add ONIE NVMEM cells support' \ /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
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).