diff options
| author | Miquel Raynal <miquel.raynal@bootlin.com> | 2025-06-18 11:48:00 +0300 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2025-06-27 13:13:43 +0300 |
| commit | caa9654112d94eb47f57ae5c35b6fe8d85f5cb38 (patch) | |
| tree | 5dfe07ff38d622dfa4695dde546bf187516ab333 /scripts/gdb/linux/xarray.py | |
| parent | 8995cf53e66285f62412cc031ff9fb3a34061975 (diff) | |
| download | linux-caa9654112d94eb47f57ae5c35b6fe8d85f5cb38.tar.xz | |
mtd: spinand: winbond: Prevent unsupported frequencies on dual/quad I/O variants
[ Upstream commit dba90f5a79c13936de4273a19e67908a0c296afe ]
Dual and quad capable chips natively support dual and quad I/O variants
at up to 104MHz (1-2-2 and 1-4-4 operations). Reaching the maximum speed
of 166MHz is theoretically possible (while still unsupported in the
field) by adding a few more dummy cycles. Let's be accurate and clearly
state this limit.
Setting a maximum frequency implies adding the frequency parameter to
the macro, which is done using a variadic argument to avoid impacting
all the other drivers which already make use of this macro.
Fixes: 1ea808b4d15b ("mtd: spinand: winbond: Update the *JW chip definitions")
Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'scripts/gdb/linux/xarray.py')
0 files changed, 0 insertions, 0 deletions