⭐ 欢迎来到虫虫下载站! | 📦 资源下载 📁 资源专辑 ℹ️ 关于我们
⭐ 虫虫下载站

📄 ide.c

📁 《嵌入式系统设计与实例开发实验教材II:基于ARM9微处理器与Linux操作系统》IDE—CF卡模块读写实验
💻 C
📖 第 1 页 / 共 5 页
字号:
	   possibly killing some innocent following sector */	if (block == 0 && drive->remap_0_to_1 == 1)		block = 1;  /* redirect MBR access to EZ-Drive partn table */#if (DISK_RECOVERY_TIME > 0)	while ((read_timer() - hwif->last_time) < DISK_RECOVERY_TIME);#endif	SELECT_DRIVE(hwif, drive);	if (ide_wait_stat(&startstop, drive, drive->ready_stat, BUSY_STAT|DRQ_STAT, WAIT_READY)) {		printk("%s: drive not ready for command\n", drive->name);		return startstop;	}	if (!drive->special.all) {		if (rq->cmd == IDE_DRIVE_CMD || rq->cmd == IDE_DRIVE_TASK) {			return execute_drive_cmd(drive, rq);		}		if (drive->driver != NULL) {			return (DRIVER(drive)->do_request(drive, rq, block));		}		printk("%s: media type %d not supported\n", drive->name, drive->media);		goto kill_rq;	}	return do_special(drive);kill_rq:	if (drive->driver != NULL)		DRIVER(drive)->end_request(0, HWGROUP(drive));	else		ide_end_request(0, HWGROUP(drive));	return ide_stopped;}ide_startstop_t restart_request (ide_drive_t *drive){	ide_hwgroup_t *hwgroup = HWGROUP(drive);	unsigned long flags;	spin_lock_irqsave(&io_request_lock, flags);	hwgroup->handler = NULL;	del_timer(&hwgroup->timer);	spin_unlock_irqrestore(&io_request_lock, flags);	return start_request(drive);}/* * ide_stall_queue() can be used by a drive to give excess bandwidth back * to the hwgroup by sleeping for timeout jiffies. */void ide_stall_queue (ide_drive_t *drive, unsigned long timeout){	if (timeout > WAIT_WORSTCASE)		timeout = WAIT_WORSTCASE;	drive->sleep = timeout + jiffies;}#define WAKEUP(drive)	((drive)->service_start + 2 * (drive)->service_time)/* * choose_drive() selects the next drive which will be serviced. */static inline ide_drive_t *choose_drive (ide_hwgroup_t *hwgroup){	ide_drive_t *drive, *best;repeat:		best = NULL;	drive = hwgroup->drive;	do {		if (!list_empty(&drive->queue.queue_head) && (!drive->sleep || 0 <= (signed long)(jiffies - drive->sleep))) {			if (!best			 || (drive->sleep && (!best->sleep || 0 < (signed long)(best->sleep - drive->sleep)))			 || (!best->sleep && 0 < (signed long)(WAKEUP(best) - WAKEUP(drive))))			{				if( !drive->queue.plugged )					best = drive;			}		}	} while ((drive = drive->next) != hwgroup->drive);	if (best && best->nice1 && !best->sleep && best != hwgroup->drive && best->service_time > WAIT_MIN_SLEEP) {		long t = (signed long)(WAKEUP(best) - jiffies);		if (t >= WAIT_MIN_SLEEP) {			/*			 * We *may* have some time to spare, but first let's see if			 * someone can potentially benefit from our nice mood today..			 */			drive = best->next;			do {				if (!drive->sleep				 && 0 < (signed long)(WAKEUP(drive) - (jiffies - best->service_time))				 && 0 < (signed long)((jiffies + t) - WAKEUP(drive)))				{					ide_stall_queue(best, IDE_MIN(t, 10 * WAIT_MIN_SLEEP));					goto repeat;				}			} while ((drive = drive->next) != best);		}	}	return best;}/* * Issue a new request to a drive from hwgroup * Caller must have already done spin_lock_irqsave(&io_request_lock, ..); * * A hwgroup is a serialized group of IDE interfaces.  Usually there is * exactly one hwif (interface) per hwgroup, but buggy controllers (eg. CMD640) * may have both interfaces in a single hwgroup to "serialize" access. * Or possibly multiple ISA interfaces can share a common IRQ by being grouped * together into one hwgroup for serialized access. * * Note also that several hwgroups can end up sharing a single IRQ, * possibly along with many other devices.  This is especially common in * PCI-based systems with off-board IDE controller cards. * * The IDE driver uses the single global io_request_lock spinlock to protect * access to the request queues, and to protect the hwgroup->busy flag. * * The first thread into the driver for a particular hwgroup sets the * hwgroup->busy flag to indicate that this hwgroup is now active, * and then initiates processing of the top request from the request queue. * * Other threads attempting entry notice the busy setting, and will simply * queue their new requests and exit immediately.  Note that hwgroup->busy * remains set even when the driver is merely awaiting the next interrupt. * Thus, the meaning is "this hwgroup is busy processing a request". * * When processing of a request completes, the completing thread or IRQ-handler * will start the next request from the queue.  If no more work remains, * the driver will clear the hwgroup->busy flag and exit. * * The io_request_lock (spinlock) is used to protect all access to the * hwgroup->busy flag, but is otherwise not needed for most processing in * the driver.  This makes the driver much more friendlier to shared IRQs * than previous designs, while remaining 100% (?) SMP safe and capable. *//* --BenH: made non-static as ide-pmac.c uses it to kick the hwgroup back *         into life on wakeup from machine sleep. */ void ide_do_request(ide_hwgroup_t *hwgroup, int masked_irq){	ide_drive_t	*drive;	ide_hwif_t	*hwif;	ide_startstop_t	startstop;	ide_get_lock(&ide_lock, ide_intr, hwgroup);	/* for atari only: POSSIBLY BROKEN HERE(?) */	__cli();	/* necessary paranoia: ensure IRQs are masked on local CPU */	while (!hwgroup->busy) {		hwgroup->busy = 1;		drive = choose_drive(hwgroup);		if (drive == NULL) {			unsigned long sleep = 0;			hwgroup->rq = NULL;			drive = hwgroup->drive;			do {				if (drive->sleep && (!sleep || 0 < (signed long)(sleep - drive->sleep)))					sleep = drive->sleep;			} while ((drive = drive->next) != hwgroup->drive);			if (sleep) {				/*				 * Take a short snooze, and then wake up this hwgroup again.				 * This gives other hwgroups on the same a chance to				 * play fairly with us, just in case there are big differences				 * in relative throughputs.. don't want to hog the cpu too much.				 */				if (0 < (signed long)(jiffies + WAIT_MIN_SLEEP - sleep)) 					sleep = jiffies + WAIT_MIN_SLEEP;#if 1				if (timer_pending(&hwgroup->timer))					printk("ide_set_handler: timer already active\n");#endif				hwgroup->sleeping = 1;	/* so that ide_timer_expiry knows what to do */				mod_timer(&hwgroup->timer, sleep);				/* we purposely leave hwgroup->busy==1 while sleeping */			} else {				/* Ugly, but how can we sleep for the lock otherwise? perhaps from tq_disk? */				ide_release_lock(&ide_lock);	/* for atari only */				hwgroup->busy = 0;			}			return;		/* no more work for this hwgroup (for now) */		}		hwif = HWIF(drive);		if (hwgroup->hwif->sharing_irq && hwif != hwgroup->hwif && hwif->io_ports[IDE_CONTROL_OFFSET]) {			/* set nIEN for previous hwif */			SELECT_INTERRUPT(hwif, drive);		}		hwgroup->hwif = hwif;		hwgroup->drive = drive;		drive->sleep = 0;		drive->service_start = jiffies;		if ( drive->queue.plugged )	/* paranoia */			printk("%s: Huh? nuking plugged queue\n", drive->name);		hwgroup->rq = blkdev_entry_next_request(&drive->queue.queue_head);		/*		 * Some systems have trouble with IDE IRQs arriving while		 * the driver is still setting things up.  So, here we disable		 * the IRQ used by this interface while the request is being started.		 * This may look bad at first, but pretty much the same thing		 * happens anyway when any interrupt comes in, IDE or otherwise		 *  -- the kernel masks the IRQ while it is being handled.		 */		if (masked_irq && hwif->irq != masked_irq)			disable_irq_nosync(hwif->irq);		spin_unlock(&io_request_lock);		ide__sti();	/* allow other IRQs while we start this request */		startstop = start_request(drive);		spin_lock_irq(&io_request_lock);		if (masked_irq && hwif->irq != masked_irq)			enable_irq(hwif->irq);		if (startstop == ide_stopped)			hwgroup->busy = 0;	}}/* * ide_get_queue() returns the queue which corresponds to a given device. */request_queue_t *ide_get_queue (kdev_t dev){	ide_hwif_t *hwif = (ide_hwif_t *)blk_dev[MAJOR(dev)].data;	return &hwif->drives[DEVICE_NR(dev) & 1].queue;}/* * Passes the stuff to ide_do_request */void do_ide_request(request_queue_t *q){	ide_do_request(q->queuedata, 0);}/* * un-busy the hwgroup etc, and clear any pending DMA status. we want to * retry the current request in pio mode instead of risking tossing it * all away */void ide_dma_timeout_retry(ide_drive_t *drive){	ide_hwif_t *hwif = HWIF(drive);	struct request *rq;	/*	 * end current dma transaction	 */	(void) hwif->dmaproc(ide_dma_end, drive);	/*	 * complain a little, later we might remove some of this verbosity	 */	printk("%s: timeout waiting for DMA\n", drive->name);	(void) hwif->dmaproc(ide_dma_timeout, drive);	/*	 * disable dma for now, but remember that we did so because of	 * a timeout -- we'll reenable after we finish this next request	 * (or rather the first chunk of it) in pio.	 */	drive->retry_pio++;	drive->state = DMA_PIO_RETRY;	(void) hwif->dmaproc(ide_dma_off_quietly, drive);	/*	 * un-busy drive etc (hwgroup->busy is cleared on return) and	 * make sure request is sane	 */	rq = HWGROUP(drive)->rq;	HWGROUP(drive)->rq = NULL;	rq->errors = 0;	rq->sector = rq->bh->b_rsector;	rq->current_nr_sectors = rq->bh->b_size >> 9;	rq->buffer = rq->bh->b_data;}/* * ide_timer_expiry() is our timeout function for all drive operations. * But note that it can also be invoked as a result of a "sleep" operation * triggered by the mod_timer() call in ide_do_request. */void ide_timer_expiry (unsigned long data){	ide_hwgroup_t	*hwgroup = (ide_hwgroup_t *) data;	ide_handler_t	*handler;	ide_expiry_t	*expiry; 	unsigned long	flags;	unsigned long	wait;	spin_lock_irqsave(&io_request_lock, flags);	del_timer(&hwgroup->timer);	if ((handler = hwgroup->handler) == NULL) {		/*		 * Either a marginal timeout occurred		 * (got the interrupt just as timer expired),		 * or we were "sleeping" to give other devices a chance.		 * Either way, we don't really want to complain about anything.		 */		if (hwgroup->sleeping) {			hwgroup->sleeping = 0;			hwgroup->busy = 0;		}	} else {		ide_drive_t *drive = hwgroup->drive;		if (!drive) {			printk("ide_timer_expiry: hwgroup->drive was NULL\n");			hwgroup->handler = NULL;		} else {			ide_hwif_t *hwif;			ide_startstop_t startstop;			if (!hwgroup->busy) {				hwgroup->busy = 1;	/* paranoia */				printk("%s: ide_timer_expiry: hwgroup->busy was 0 ??\n", drive->name);			}			if ((expiry = hwgroup->expiry) != NULL) {				/* continue */				if ((wait = expiry(drive)) != 0) {					/* reset timer */					hwgroup->timer.expires  = jiffies + wait;					add_timer(&hwgroup->timer);					spin_unlock_irqrestore(&io_request_lock, flags);					return;				}			}			hwgroup->handler = NULL;			/*			 * We need to simulate a real interrupt when invoking			 * the handler() function, which means we need to globally			 * mask the specific IRQ:			 */			spin_unlock(&io_request_lock);			hwif  = HWIF(drive);#if DISABLE_IRQ_NOSYNC			disable_irq_nosync(hwif->irq);#else			disable_irq(hwif->irq);	/* disable_irq_nosync ?? */#endif /* DISABLE_IRQ_NOSYNC */			__cli();	/* local CPU only, as if we were handling an interrupt */			if (hwgroup->poll_timeout != 0) {				startstop = handler(drive);			} else if (drive_is_ready(drive)) {				if (drive->waiting_for_dma)					(void) hwgroup->hwif->dmaproc(ide_dma_lostirq, drive);				(void)ide_ack_intr(hwif);				printk("%s: lost interrupt\n", drive->name);				startstop = handler(drive);			} else {				if (drive->waiting_for_dma) {					startstop = ide_stopped;					ide_dma_timeout_retry(drive);				} else					startstop = ide_error(drive, "irq timeout", GET_STAT());			}			set_recovery_timer(hwif);			drive->service_time = jiffies - drive->service_start;			enable_irq(hwif->irq);			spin_lock_irq(&io_request_lock);			if (startstop == ide_stopped)				hwgroup->busy = 0;		}	}	ide_do_request(hwgroup, 0);	spin_unlock_irqrestore(&io_request_lock, flags);}/* * There's nothing really useful we can do with an unexpected interrupt, * other than reading the status register (to clear it), and logging it. * There should be no way that an irq can happen before we're ready for it, * so we needn't worry much about losing an "important" interrupt here. * * On laptops (and "green" PCs), an unexpected interrupt occurs whenever the * drive enters "idle", "standby", or "sleep" mode, so if the status looks * "good", we just ignore the interrupt completely. * * This routine assumes __cli() is in effect when called. * * If an unexpected interrupt happens on irq15 while we are handling irq14 * and if the two interfaces are "serialized" (CMD640), then it looks like * we could screw up by interfering with a new request being set up for irq15. * * In reality, this is a non-issue.  The new command is not sent unless the * drive is ready to accept one, in which case we know the drive is not * trying to interrupt us.  And ide_set_handler() is always invoked before * completing the issuance of any new drive command, so we will not be * accidently invoked as a result of any valid command completion interrupt. * */static void unexpected_intr (int irq, ide_hwgroup_t *hwgroup){	byte stat;	ide_hwif_t *hwif = hwgroup->hwif;	/*	 * handle the unexpected interrupt	 */	do {		if (hwif->irq == irq) {			stat = IN_BYTE(hwif->io_ports[IDE_STATUS_OFFSET]);			if (!OK_STAT(stat, READY_STAT, BAD_STAT)) {				/* Try to not flood the console with msgs */				static unsigned long last_msgtime, count;				++count;				if (0 < (signed long)(jiffies - (last_msgtime + HZ))) {					last_msgtime = jiffies;					printk("%s%s: unexpected interrupt, status=0x%02x, count=%ld\n",					 hwif->name, (hwif->next == hwgroup->hwif) ? "" : "(?)", stat, count);				}			}		}	} while ((hwif = hwif->next) != hwgroup->hwif);}/* * entry point for all interrupts, caller does __cli() for us

⌨️ 快捷键说明

复制代码 Ctrl + C
搜索代码 Ctrl + F
全屏模式 F11
切换主题 Ctrl + Shift + D
显示快捷键 ?
增大字号 Ctrl + =
减小字号 Ctrl + -