Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1353460
| From | Andrey Smirnov <andrew.smirnov@gmail.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [RESEND RFC 2/3] nvmem: Add 'nvmem-blob' driver |
| Date | 2016-03-08 23:50 +0100 |
| Message-ID | <rayBY-7hS-17@gated-at.bofh.it> (permalink) |
| References | (2 earlier) <r8ftM-8on-3@gated-at.bofh.it> <r8iL1-2in-31@gated-at.bofh.it> <r9Yyu-jj-7@gated-at.bofh.it> <rah86-493-7@gated-at.bofh.it> <rayiB-7ah-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
>> >> I don't think I understand what you mean, could you give me an example >> of how I'd use local-mac-address property for that use case? AFAIK, >> local-mac-address is just an array of bytes embedded into device tree, > > Well, yeah, but the nvmem-blob is also just an array of bytes embedded > into the DT, right? One is accessible via "nvmem" API and the other one isn't. > >> how would it get populated with data from OTP memory of SoC? > > In the bootloader, or Linux, read the OTP, patch the DT to add that > node, done. No, it's not really "done", because if you read my previous messages, "read the OTP, patch the DT" is exactly the problem I am trying to solve. The overall goal is to be able to read a certain "nvmem" cell and patch DT with that data as MAC address, however in it's current incarnation "nvmem" doesn't have provisions to make cells that are just combination of other cells (patch #3) and to embed certain data in DT and then access it as "nvmem" cell (patch #2)
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: [RESEND RFC 2/3] nvmem: Add 'nvmem-blob' driver Maxime Ripard <maxime.ripard@free-electrons.com> - 2016-03-07 09:20 +0100
Re: [RESEND RFC 2/3] nvmem: Add 'nvmem-blob' driver Andrey Smirnov <andrew.smirnov@gmail.com> - 2016-03-08 05:10 +0100
Re: [RESEND RFC 2/3] nvmem: Add 'nvmem-blob' driver Maxime Ripard <maxime.ripard@free-electrons.com> - 2016-03-08 23:30 +0100
Re: [RESEND RFC 2/3] nvmem: Add 'nvmem-blob' driver Andrey Smirnov <andrew.smirnov@gmail.com> - 2016-03-08 23:50 +0100
Re: [RESEND RFC 2/3] nvmem: Add 'nvmem-blob' driver Trent Piepho <tpiepho@kymetacorp.com> - 2016-03-09 00:40 +0100
Re: [RESEND RFC 2/3] nvmem: Add 'nvmem-blob' driver Maxime Ripard <maxime.ripard@free-electrons.com> - 2016-03-09 11:20 +0100
Re: [RESEND RFC 2/3] nvmem: Add 'nvmem-blob' driver Trent Piepho <tpiepho@kymetacorp.com> - 2016-03-09 21:00 +0100
Re: [RESEND RFC 2/3] nvmem: Add 'nvmem-blob' driver Maxime Ripard <maxime.ripard@free-electrons.com> - 2016-03-09 11:00 +0100
Re: [RESEND RFC 2/3] nvmem: Add 'nvmem-blob' driver Andrey Smirnov <andrew.smirnov@gmail.com> - 2016-03-09 18:10 +0100
Re: [RESEND RFC 2/3] nvmem: Add 'nvmem-blob' driver Sascha Hauer <s.hauer@pengutronix.de> - 2016-03-09 09:10 +0100
csiph-web