Re: [PATCH 3/3] nvmem: qfprom: Don't touch certain fuses

2020-10-05 Thread Srinivas Kandagatla
On 01/10/2020 22:49, Evan Green wrote: Oh no, I realized this isn't nearly as beautiful when I try to move it into the core. The low level read/write interface between the nvmem core and the driver is a range. So to move this into the core I'd have to implement all the overlap computation logi

Re: [PATCH 3/3] nvmem: qfprom: Don't touch certain fuses

2020-10-01 Thread Evan Green
On Thu, Oct 1, 2020 at 9:30 AM Srinivas Kandagatla wrote: > > > > On 01/10/2020 17:27, Evan Green wrote: > > On Thu, Oct 1, 2020 at 7:17 AM Srinivas Kandagatla > > wrote: > >> > >> Hi Evan, > >> > >> On 29/09/2020 21:58, Evan Green wrote: > >>> Some fuse ranges are protected by the XPU such that

Re: [PATCH 3/3] nvmem: qfprom: Don't touch certain fuses

2020-10-01 Thread Srinivas Kandagatla
On 01/10/2020 17:27, Evan Green wrote: On Thu, Oct 1, 2020 at 7:17 AM Srinivas Kandagatla 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 pe

Re: [PATCH 3/3] nvmem: qfprom: Don't touch certain fuses

2020-10-01 Thread Evan Green
On Thu, Oct 1, 2020 at 7:17 AM Srinivas Kandagatla 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 a

Re: [PATCH 3/3] nvmem: qfprom: Don't touch certain fuses

2020-10-01 Thread Srinivas Kandagatla
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 regi