| To: | "Vladimir A. Barinov" <vbarinov@ru.mvista.com> |
|---|---|
| Subject: | Re: [PATCH] PNX8550 NAND flash driver |
| From: | Thomas Gleixner <tglx@linutronix.de> |
| Date: | Mon, 10 Jul 2006 11:53:16 +0200 |
| Cc: | Todd Poynor <tpoynor@mvista.com>, linux-mtd@lists.infradead.org, linux-mips@linux-mips.org |
| In-reply-to: | <43F1D439.60205@ru.mvista.com> |
| Organization: | linutronix |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <43A2F819.1040106@ru.mvista.com> <43C69EC2.2070601@mvista.com> <43F1D439.60205@ru.mvista.com> |
| Sender: | linux-mips-bounce@linux-mips.org |
On Tue, 2006-02-14 at 15:59 +0300, Vladimir A. Barinov wrote:
> >> + }
> >> +
> >> + if (((bytes & 3) || (bytes < 16)) || ((u32) to & 3) || ((u32)
> >> from & 3)) {
> >> + if (((bytes & 1) == 0) &&
> >> + (((u32) to & 1) == 0) && (((u32) from & 1) == 0)) {
> >> + int words = bytes / 2;
> >> +
> >> + local_irq_disable();
> >> + for (i = 0; i < words; i++) {
> >> + to16[i] = from16[i];
> >> + }
> >> + local_irq_enable();
> >
> >
> > Really necessary to disable all irqs around this transfer? How long
> > can interrupts be off during that time?
>
> That is needed since the NAND device is binded to the external XIO bus
> that could be used by another devices.
Err, you have to protect the whole access sequence then. What protects
the chip against access between the command write and data read ?
If this really is a bus conflict problem, then you need some more
protection than this.
Can you please describe in detail why you think this is necessary.
tglx
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH] sparsemem fix, Franck Bui-Huu |
|---|---|
| Next by Date: | Re: [PATCH] do not count pages in holes with sparsemem, Franck Bui-Huu |
| Previous by Thread: | [PATCH] IP22: fix serial console hangs, Julien BLACHE |
| Next by Thread: | Re: [PATCH] PNX8550 NAND flash driver, Jurgen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |