mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: unsik Kim <donari75@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, hch@infradead.org,
	alan@lxorguk.ukuu.org.uk, shdl@zakalwe.fi,
	harvey.harrison@gmail.com, minchan.kim@gmail.com
Subject: Re: [PATCH] mflash: Initial support
Date: Thu, 5 Mar 2009 18:24:47 +0900	[thread overview]
Message-ID: <57afda040903050124h30bff6fflb9d8dedde966d18c@mail.gmail.com> (raw)
In-Reply-To: <20090226133509.27b58014.akpm@linux-foundation.org>

Hello?

First of all, thanks for your kind review and sorry for very late reply.

>
> Have we fully explored the option of controlling this device with the
> current ATA or IDE code, rather than creating a whole new parallel
> block device implementation?
>

As you see, this driver quite similar with ATA code. (especially PATA
platform device driver) I think integrating with ATA is possible. But, I
think integration is not adequate at this time.

Because,

1. ATA layer deals standard ATA protocol. ATA layer have many low-
level device specific interface, but data transfer keeps ATA rule. But,
mflash IO mode doesn't.

2. Even though currently not used in mflash driver code, mflash has
some custom command and modes. (nand fusing, firmware patch,
etc) If this feature supported in linux kernel, ATA layer more altered.

3. Currently PATA platform device driver doesn't support interrupt.
(I'm not sure) But, mflash uses interrupt (polling mode is just for debug).

4. mflash is somewhat under-develop product. Even though some
company already using mflash their own product, I think more time is
needed for standardization of custom command and mode. That time
(maybe October) I will talk to with ATA people. If they accept integration,
I will integrate.

All the other requests will be reflected with upcoming patch.

-- 
unsik Kim <donari75@gmail.com>

  reply	other threads:[~2009-03-05  9:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-25  9:31 unsik Kim
2009-02-26 21:35 ` Andrew Morton
2009-03-05  9:24   ` unsik Kim [this message]
2009-03-05 22:27     ` Andrew Morton
2009-03-06  2:26       ` unsik Kim
2009-03-06  2:29       ` [PATCH v2] mflash: Initial support v2 unsik Kim
2009-03-06 21:46         ` Andrew Morton

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=57afda040903050124h30bff6fflb9d8dedde966d18c@mail.gmail.com \
    --to=donari75@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=harvey.harrison@gmail.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=minchan.kim@gmail.com \
    --cc=shdl@zakalwe.fi \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®