In data lunedì 22 marzo 2010 11:31:30, Fabio Giovagnini ha scritto:
: > But for making it owrking I needed to comment
> linux-2.6.17-sh7203/drivers/mtd/chips
> 
> static void put_chip(struct map_info *map, struct flchip *chip, unsigned
>  long adr)
> {
>       struct cfi_private *cfi = map->fldrv_priv;
> 
>       switch(chip->oldstate) {
>       case FL_ERASING:
>               chip->state = chip->oldstate;
>               map_write(map, CMD(0x30), chip->in_progress_block_addr);
>               chip->oldstate = FL_READY;
>               chip->state = FL_ERASING;
>               break;
> 
>       case FL_XIP_WHILE_ERASING:
>               chip->state = chip->oldstate;
>               chip->oldstate = FL_READY;
>               break;
> 
>       case FL_READY:
>       case FL_STATUS:
>               /* We should really make set_vpp() count, rather than doing 
> this */
>               DISABLE_VPP(map);
>               break;
>       default:
>               printk(KERN_ERR "MTD: put_chip() called with oldstate %d!!\n", 
> chip-
> 
> >oldstate);
> 
>       }
>       // FABIO
>       //wake_up(&chip->wq);
> }
> 
> 
> The question is:
> Does the MTD driver and the substanding chip flash handler uses the IRQ? If
>  yes what is the interrupt handler?
> Why with wakeup I have call trace?
> 
> Thanks a lot
> 

-- 
Fabio Giovagnini

Aurion s.r.l.
P.I e C.F.
00885711200
Tel. +39.051.594.78.24
Cell. +39.335.83.50.919
_______________________________________________
uClinux-dev mailing list
uClinux-dev@uclinux.org
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by uclinux-dev@uclinux.org
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev

Reply via email to