Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1298790

Adding OTP-only device to MTD or CHAR subsystem?

Show all headers | View raw

Greg/Brian/Arnd,

We have OTP device drivers for accessing OTP memory in our SoCs.

I looking for the right place and model to place such OTP device drivers.

1) Should we follow the bfin-otp model in drivers/char?  This doesn't 
seem like the right place to put it although following the bfin example 
is quite simple to implement.  We actually had a custom set of Ioctl's 
that I changed to use the standard file access model used by the bfin 
driver.  But a custom util is still needed to issue an OTPLOCK command. 
  I'm guess mtd-utils has such abilities (or should).

2) Instead, should we start adding OTP-only drivers into the MTD 
subsystem?  Onenand and CFI based MTD devices already have OTP 
programmable regions.  If we created a new OTP device type in the MTD 
subsystem this looks like a good thing to do.  mtd-utils could/should be 
used to access the OTP device then along with standard fileio operations.

3) Or some other suggestion of where to place OTP device drivers?

Regards,
  Scott
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

Adding OTP-only device to MTD or CHAR subsystem? Scott Branden <sbranden@broadcom.com> - 2015-12-29 00:30 +0100
  Re: Adding OTP-only device to MTD or CHAR subsystem? Arnd Bergmann <arnd@arndb.de> - 2015-12-29 00:40 +0100
    Re: Adding OTP-only device to MTD or CHAR subsystem? Scott Branden <sbranden@broadcom.com> - 2015-12-29 01:40 +0100

csiph-web