diff options
| author | Bryan O'Donoghue <[email protected]> | 2019-06-26 10:27:30 +0000 |
|---|---|---|
| committer | Greg Kroah-Hartman <[email protected]> | 2019-06-26 12:26:47 +0000 |
| commit | 159dbaf57b2f4f67ecb59b2c87d071e45ed41d7e (patch) | |
| tree | 07e82f11ca9cf91a0f00826038b481ba9fe73091 /drivers/android/binder_alloc.c | |
| parent | nvmem: imx-ocotp: Ensure WAIT bits are preserved when setting timing (diff) | |
| download | kernel-159dbaf57b2f4f67ecb59b2c87d071e45ed41d7e.tar.gz kernel-159dbaf57b2f4f67ecb59b2c87d071e45ed41d7e.zip | |
nvmem: imx-ocotp: Change TIMING calculation to u-boot algorithm
The RELAX field of the OCOTP block is turning out as a zero on i.MX8MM.
This messes up the subsequent re-load of the fuse shadow registers.
After some discussion with people @ NXP its clear we have missed a trick
here in Linux.
The OCOTP fuse programming time has a physical minimum 'burn time' that is
not related to the ipg_clk.
We need to define the RELAX, STROBE_READ and STROBE_PROG fields in terms of
desired timings to allow for the burn-in to safely complete. Right now only
the RELAX field is calculated in terms of an absolute time and we are
ending up with a value of zero.
This patch inherits the u-boot timings for the OCOTP_TIMING calculation on
the i.MX6 and i.MX8. Those timings are known to work and critically specify
values such as STROBE_PROG as a minimum timing.
Fixes: 0642bac7da42 ("nvmem: imx-ocotp: add write support")
Signed-off-by: Bryan O'Donoghue <[email protected]>
Suggested-by: Leonard Crestez <[email protected]>
Reviewed-by: Leonard Crestez <[email protected]>
Signed-off-by: Srinivas Kandagatla <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
Diffstat (limited to 'drivers/android/binder_alloc.c')
0 files changed, 0 insertions, 0 deletions