diff options
author | Masahiro Yamada <yamada.masahiro@socionext.com> | 2020-01-27 21:39:34 +0900 |
---|---|---|
committer | Miquel Raynal <miquel.raynal@bootlin.com> | 2020-03-09 14:49:14 +0100 |
commit | 9afbe7c0140f663586edb6e823b616bd7076c00a (patch) | |
tree | a4db220b9f5a74e4da8cc4520aaedfc3ecaa323a /scripts/basic | |
parent | 009264605cdf1b12962c3a46f75818d05452e890 (diff) |
mtd: rawnand: denali: deassert write protect pin
If the write protect signal from this IP is connected to the NAND
device, this IP can handle the WP# pin via the WRITE_PROTECT
register.
The Denali NAND Flash Memory Controller User's Guide describes
this register like follows:
When the controller is in reset, the WP# pin is always asserted
to the device. Once the reset is removed, the WP# is de-asserted.
The software will then have to come and program this bit to
assert/de-assert the same.
1 - Write protect de-assert
0 - Write protect assert
The default value is 1, so the write protect is de-asserted after
the reset is removed. The driver can write to the device unless
someone has explicitly cleared register before booting the kernel.
The boot ROM of some UniPhier SoCs (LD4, Pro4, sLD8, Pro5) is the
case; the boot ROM clears the WRITE_PROTECT register when the system
is booting from the NAND device, so the NAND device becomes read-only.
Set it to 1 in the driver in order to allow the write access to the
device.
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
Link: https://lore.kernel.org/linux-mtd/20200127123934.11847-1-yamada.masahiro@socionext.com
Diffstat (limited to 'scripts/basic')
0 files changed, 0 insertions, 0 deletions