On Mon, May 08, 2023 at 05:58:20PM +0200, Rafał Miłecki wrote: > From: Rafał Miłecki <rafal@xxxxxxxxxx> > > All kind of calibration data should be described as NVMEM cells of NVMEM > devices. That is more generic solution than "mediatek,mtd-eeprom" which > is MTD specific. > > Add support for EEPROM NVMEM cells and deprecate existing MTD-based > property. > > Cc: Christian Marangi <ansuelsmth@xxxxxxxxx> > Signed-off-by: Rafał Miłecki <rafal@xxxxxxxxxx> > --- > Ansuel is working on mt76 driver support for NVMEM based EEPROM access: > https://github.com/openwrt/mt76/pull/765 > > I took the liberty to propose this binding patch. > > One important difference: my binding uses "eeprom" while Ansuel went > with "precal". I found a lot of "eeprom" references and only one > "precal". If you think however "precal" fits better please comment. The name is totally "to decide". I feel eeprom might be also way too much generic... I was thinking to something like cal or precal following ath10k or ath11k pattern. Also in the code itself I notice there can be different calibration hence the idea of precal and cal... (currently we define the entire mtd partition and call it eeprom but on some card different data are referenced with an offset... that will be dropped since nvmem cell will reference directly the data without using offset, which seems an hack to me) -- Ansuel
