On Thu, Oct 1, 2020 at 7:17 AM Srinivas KandagatlaOfcourse these can come from driver directly based on compatible!
<srinivas.kandagatla@xxxxxxxxxx> wrote:
Hi Evan,
On 29/09/2020 21:58, Evan Green wrote:
Some fuse ranges are protected by the XPU such that the AP cannot
access them. Attempting to do so causes an SError. Use the newly
introduced per-soc compatible string to attach the set of regions
we should not access. Then tiptoe around those regions.
This is a generic feature that can be used by any nvmem provider, can
you move this logic to nvmem core instead of having it in qfprom!
Sure! I'd prefer to keep this data in the driver for now rather than
trying to define DT bindings for the keepout zones. So then I'll pass
in my keepout array via struct nvmem_config at registration time, and
then the core can handle the keepout logic instead of qfprom.c.
-Evan