On Mon, Jul 23, 2018 at 4:35 AM, Sakari Ailus <sakari.ailus@xxxxxx> wrote: > Hi Matt, > > On Sun, Jul 15, 2018 at 11:05:42PM -0700, Matt Ranostay wrote: >> Hello et all, >> >> So currently working with some thermal sensors that have coefficients >> that needs to be passed back to userspace that aren't related to the >> pixel data but are required to normalize to remove scan patterns and >> temp gradients. Was wondering the best way to do this, and hope it >> isn't some is kludge of the close captioning, or just passing raw data >> as another column line. > > Are you referring to the EEPROM content or something else? > > For EEPROM, I could think of just exposing the EEPROM to the user space > as-is using the NVMEM API. This information is very, very device specific > and therefore using a generic interface to access individual values there > isn't really useful. > Actually that is okay for the EEPROM data that is per sensor, and nvram does seem like it would work. But there is per video frame data that is required along with the static EEPROM data to calculate the actual end result. - Matt > -- > Sakari Ailus > e-mail: sakari.ailus@xxxxxx
