All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marek.vasut@gmail.com>
To: Eric Miao <eric.y.miao@gmail.com>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
	linux-arm-kernel@lists.arm.linux.org.uk,
	linux-ide@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 4/6] PalmLD IDE
Date: Tue, 21 Apr 2009 16:01:18 +0200	[thread overview]
Message-ID: <200904211601.19232.marek.vasut@gmail.com> (raw)
In-Reply-To: <f17812d70904202102m6ea8c701xa7aa04b234c062d3@mail.gmail.com>

On Tuesday 21 of April 2009 06:02:59 Eric Miao wrote:
> On Mon, Mar 23, 2009 at 5:23 AM, Marek Vasut <marek.vasut@gmail.com> wrote:
> >> Dne Saturday 16 of August 2008 11:08:03 Russell King - ARM Linux 
napsal(a):
> >> > On Wed, Aug 13, 2008 at 10:52:23PM +0200, Marek Vasut wrote:
> >> > > This patch adds palmld ide channel support, same as previous patch,
> >> > > I think this can be merged since it wont break anything.
> >> >
> >> > I think this one also needs review by the Linux ATA folk.  Mention to
> >> > them that it's part of a patchset for ARM and that you'd prefer it
> >> > to be merged into the ARM tree.
> >> >
> >> > > +static const char drvname[] = "pata_palmld";
> >> > > +MODULE_ALIAS("platform: "drvname);
> >> >
> >> > Have you tried building this as a module?  Also, IIRC, there isn't
> >> > supposed to be a space after the colon...
> >>
> >> Ok, I fixed the issues and CCed linux-ide and the maintainer.
> >>
> >> Thanks
> >
> > Hi, Im resending this patch since it was totally ignored last time. It
> > still applies correctly. It'd be for the best to push this through
> > arm-kernel tree.
>
> I wonder if this driver can be implemented in a more generic way so
> that other boards can be benefited. The only specific things I see are:
>
> 1. I/O mapping address space
> 2. IRQ
> 3. PowerON
>
> IRQ can be specified by platform_data, and power_on can be implemented
> by callbacks in platform_data. I/O mapping should be OK by resources in
> platform_device.
>
> So what's else to make this specific to PalmLD?

Will there be anyone who would use that other than palmld then ? I doubt 
anyone has that obscure hardware. That's why I see no point in making this 
generic.

  reply	other threads:[~2009-04-21 14:01 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-22 21:23 [PATCH 4/6] PalmLD IDE Marek Vasut
2009-04-19 16:14 ` Marek Vasut
2009-04-20 20:38   ` Bartlomiej Zolnierkiewicz
2009-04-20 20:53     ` Marek Vasut
2009-04-20 21:01       ` Bartlomiej Zolnierkiewicz
2009-04-20 21:17       ` Alan Cox
2009-04-21  4:02 ` Eric Miao
2009-04-21 14:01   ` Marek Vasut [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-04-21  0:05 Marek Vasut
2009-04-21 14:27 ` Alan Cox
2009-04-21 14:52   ` Marek Vasut
2009-04-21 15:19     ` Alan Cox
2009-04-21 17:44       ` Marek Vasut
2009-04-21 19:35         ` Alan Cox
2009-04-21 19:38           ` Jeff Garzik
     [not found] <200808132252.23732.marek.vasut@gmail.com>
     [not found] ` <20080816090803.GI5946@flint.arm.linux.org.uk>
2008-08-16 14:30   ` Marek Vasut

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=200904211601.19232.marek.vasut@gmail.com \
    --to=marek.vasut@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=eric.y.miao@gmail.com \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.