Christian Lamparter <chunkeey@xxxxxxxxx> writes: > On most embedded ath9k devices (like range extenders, > routers, accesspoints, ...) the calibration data for > the RF/PHY is simply stored in a MTD partition named > "ART", "caldata"/"calibration", etc. > > Any mtd partition is automatically registered in the > nvmem subsystem. This makes is possible to fetch the > necessary calibration directly from there at the low > cost of adding nvmem cell information via the > device-tree or via similar means. > > This speeds up the driver's initialization a lot, > because the driver doesn't have to wait for userspace > to provide the data via helpers. > > Signed-off-by: Christian Lamparter <chunkeey@xxxxxxxxx> The series looks good to me. But I'm curious, why you marked this as RFC? Is there something controversial I missed? -- https://patchwork.kernel.org/project/linux-wireless/list/ https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
