[PATCH] misc: atmel-secumod: Driver for Atmel "security module".

David Mosberger davidm at egauge.net
Mon Jan 25 08:24:04 PST 2016


Alexandre,

On Mon, Jan 25, 2016 at 4:09 AM, Alexandre Belloni
<alexandre.belloni at free-electrons.com> wrote:

> I know this does more than that but I think those thre sections should
> be registered using the nvmem framework. The sysfs file creation and
> accesses then comes for free.

I think Finn's patches would have to go in for that first, since the
existing nvram code is a mess.
Even with Finn's patches in, I think it could go either way.  I'm not
exactly sure how some of the
features of the security module would be used: key management, auto
erasing, there is a strange
"backup mode" vs "normal mode" which is not well documented, etc.  So
I think it may well end up
being sufficiently different to warrant a separate driver.

> Another idea is also to expose it using a genpool so it can be accessed
> as sram from inside the kernel.

That may be a fine idea, but as far as our application is concerned,
we need user-level access
to the battery-backed RAM.

Best regards,

  --david
-- 
eGauge Systems LLC, http://egauge.net/, 1.877-EGAUGE1, fax 720.545.9768



More information about the linux-arm-kernel mailing list