mirror of
https://github.com/AuxXxilium/linux_dsm_epyc7002.git
synced 2024-12-22 20:43:23 +07:00
e93cafe45f
Timeouts are currently given by the typical operation time times 8. It works in the general well-behaved case but not when an erase block is failing. For erase operations, it seems that a failing erase block will keep the device state machine in erasing state until the vendor specified maximum timeout period has passed. By this time the driver would have long since timed out, left erasing state and attempted further operations which all fail. This patch implements timeouts using values from the CFI Query structure when available. The patch also sets a longer timeout for locking operations. The current value used for locking/unlocking given by 1000000/HZ microseconds is too short for devices like J3 and J5 Strataflash which have a typical clear lock-bits time of 0.5 seconds. Signed-off-by: Anders Grafström <grfstrm@users.sourceforge.net> Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
93 lines
2.2 KiB
C
93 lines
2.2 KiB
C
|
|
/*
|
|
* struct flchip definition
|
|
*
|
|
* Contains information about the location and state of a given flash device
|
|
*
|
|
* (C) 2000 Red Hat. GPLd.
|
|
*/
|
|
|
|
#ifndef __MTD_FLASHCHIP_H__
|
|
#define __MTD_FLASHCHIP_H__
|
|
|
|
/* For spinlocks. sched.h includes spinlock.h from whichever directory it
|
|
* happens to be in - so we don't have to care whether we're on 2.2, which
|
|
* has asm/spinlock.h, or 2.4, which has linux/spinlock.h
|
|
*/
|
|
#include <linux/sched.h>
|
|
|
|
typedef enum {
|
|
FL_READY,
|
|
FL_STATUS,
|
|
FL_CFI_QUERY,
|
|
FL_JEDEC_QUERY,
|
|
FL_ERASING,
|
|
FL_ERASE_SUSPENDING,
|
|
FL_ERASE_SUSPENDED,
|
|
FL_WRITING,
|
|
FL_WRITING_TO_BUFFER,
|
|
FL_OTP_WRITE,
|
|
FL_WRITE_SUSPENDING,
|
|
FL_WRITE_SUSPENDED,
|
|
FL_PM_SUSPENDED,
|
|
FL_SYNCING,
|
|
FL_UNLOADING,
|
|
FL_LOCKING,
|
|
FL_UNLOCKING,
|
|
FL_POINT,
|
|
FL_XIP_WHILE_ERASING,
|
|
FL_XIP_WHILE_WRITING,
|
|
FL_SHUTDOWN,
|
|
FL_UNKNOWN
|
|
} flstate_t;
|
|
|
|
|
|
|
|
/* NOTE: confusingly, this can be used to refer to more than one chip at a time,
|
|
if they're interleaved. This can even refer to individual partitions on
|
|
the same physical chip when present. */
|
|
|
|
struct flchip {
|
|
unsigned long start; /* Offset within the map */
|
|
// unsigned long len;
|
|
/* We omit len for now, because when we group them together
|
|
we insist that they're all of the same size, and the chip size
|
|
is held in the next level up. If we get more versatile later,
|
|
it'll make it a damn sight harder to find which chip we want from
|
|
a given offset, and we'll want to add the per-chip length field
|
|
back in.
|
|
*/
|
|
int ref_point_counter;
|
|
flstate_t state;
|
|
flstate_t oldstate;
|
|
|
|
unsigned int write_suspended:1;
|
|
unsigned int erase_suspended:1;
|
|
unsigned long in_progress_block_addr;
|
|
|
|
spinlock_t *mutex;
|
|
spinlock_t _spinlock; /* We do it like this because sometimes they'll be shared. */
|
|
wait_queue_head_t wq; /* Wait on here when we're waiting for the chip
|
|
to be ready */
|
|
int word_write_time;
|
|
int buffer_write_time;
|
|
int erase_time;
|
|
|
|
int word_write_time_max;
|
|
int buffer_write_time_max;
|
|
int erase_time_max;
|
|
|
|
void *priv;
|
|
};
|
|
|
|
/* This is used to handle contention on write/erase operations
|
|
between partitions of the same physical chip. */
|
|
struct flchip_shared {
|
|
spinlock_t lock;
|
|
struct flchip *writing;
|
|
struct flchip *erasing;
|
|
};
|
|
|
|
|
|
#endif /* __MTD_FLASHCHIP_H__ */
|