From: Vitaly Bordug <vitb@kernel.crashing.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 1/2] [ide] mmio ide support
Date: Tue, 10 Jul 2007 15:02:28 +0400 [thread overview]
Message-ID: <20070710150228.15008b53@localhost.localdomain> (raw)
In-Reply-To: <20070707211306.2ef074cf@the-village.bc.nu>
On Sat, 7 Jul 2007 21:13:06 +0100
Alan Cox wrote:
> On Sat, 07 Jul 2007 13:48:52 +0400
> Vitaly Bordug <vitb@kernel.crashing.org> wrote:
>
> >
> > This adds support for MMIO IDE device like CompactFlash
> > in TrueIDE mode.
>
> Really we should be working towards libata support for all new
> devices. This looks like a candidate for the existing (or a little
> enhanced) pata_platform driver.
>
Yes I am aware of it, yet, the code was created for IDE subsystem due to internal reasons,
and I thought to better make it available for others at least. We'll prolly pick it up to move
to libata/pata_platform but not instantly afaict now.
> > +config BLK_DEV_MMIOIDE
> > + tristate "Memory Mapped IDE support"
>
> Please pick a better description. This isn't a generic option for
> enabling MMIO based IDE as you make it sound.
>
>
> Also we have an accepted match name for ATA platform devices - and
> adding another one messes it up irrespective of whether you want
> libata or legacy IDE support. If you use the same matches then your
> platform code, and everyone elses platform code can work with both
> drivers, except for hotpluggability.
>
> Other bugs
>
> - Your remove code releases the resources before the hwif which means
> it races another user trying to claim the resource
> - Be careful with ide_unregister. It exists and you can call it but
> its actually not very safe and there are lots of unfixed races in the
> IDE layer if you do
>
OK, makes sense.
>
> The "should we have a legacy ide driver that matches the libata
> pata_platform" question I don't really care about. Its a waste of
> effort in many ways but if you've written the code the work is done
> so why not use it.
>
> However it needs to be *compatible* so that platform devices can be
> claimed by either so the kernel build can pick legacy IDE v libata and
> not have to #ifdef all the platform code.
>
Sounds good. I'll look forward to address the issues, thanks.
> Alan
--
Sincerely, Vitaly
prev parent reply other threads:[~2007-07-11 10:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-07 9:48 [PATCH 1/2] [ide] mmio ide support Vitaly Bordug
2007-07-07 9:49 ` [PATCH 2/2] [POWERPC] mmio ide support for mpc8349-itx target Vitaly Bordug
2007-07-07 15:07 ` Olof Johansson
2007-07-07 15:12 ` Arnd Bergmann
2007-07-07 16:46 ` Sergei Shtylyov
2007-07-08 13:31 ` Segher Boessenkool
2007-07-10 10:52 ` Vitaly Bordug
2007-07-11 19:02 ` Sergei Shtylyov
2007-07-07 12:19 ` [PATCH 1/2] [ide] mmio ide support Arnd Bergmann
2007-07-07 16:51 ` Sergei Shtylyov
2007-07-07 18:07 ` Arnd Bergmann
2007-07-08 13:15 ` Bartlomiej Zolnierkiewicz
2007-07-10 18:49 ` Linas Vepstas
2007-07-07 20:02 ` Alan Cox
2007-07-08 0:54 ` Benjamin Herrenschmidt
2007-07-07 15:01 ` Olof Johansson
2007-07-10 10:53 ` Vitaly Bordug
2007-07-07 18:15 ` Sergei Shtylyov
2007-07-07 20:13 ` Alan Cox
2007-07-10 11:02 ` Vitaly Bordug [this message]
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=20070710150228.15008b53@localhost.localdomain \
--to=vitb@kernel.crashing.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
/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;
as well as URLs for NNTP newsgroup(s).