linux-spi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Miguel Ángel Álvarez" <gotzoncabanes-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: "David Brownell" <david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
Cc: spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: SPI in IXP4XX
Date: Fri, 21 Nov 2008 10:29:09 +0100	[thread overview]
Message-ID: <b0438a630811210129y2d517f12n43e9b11da726af55@mail.gmail.com> (raw)
In-Reply-To: <200811210048.28842.david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>

Hi

On Fri, Nov 21, 2008 at 9:48 AM, David Brownell <david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org> wrote:
> On Friday 21 November 2008, Miguel Ángel Álvarez wrote:
>> > Eventually the mach-pxa/*ssp*c code should vanish.
>> >
>> Vanish? Into what?
>
> It's basically a nonstandard SPI interface; so, into
> the standard interface.
>
> (Of course SSP can be used for stuff that's not SPI.
> Like I2S, in sound/soc ...)
>
>
>> Who is working on it, and how can I help him
>> introduce my modifications for ixp4xx?
>
> I don't know that anyone is working on it.  Which is
> why I said "eventually".
>

So... Returning to the main question. I have code for using SSP and
SPI in IXP4XX, and it is based in the PXA2XX. The main problem is that
I do not want to add whole new files for what is clearly just a
modification. However the original code is not accesible because it is
in the mach-pxa2xx directories.

Which decision should I take so that my changes have greater chances
of been accepted? Moving the files of pxa2xx or creating new ones? Or
this is just a bad decision and I should not use the code of pxa2xx at
all?

Thanks

Miguel Ángel

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

      parent reply	other threads:[~2008-11-21  9:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-12 12:24 SPI in IXP4XX Miguel Ángel Álvarez
     [not found] ` <b0438a630811120424j76289a0ag8cb9e72bc30ff11f-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-11-20 20:56   ` David Brownell
     [not found]     ` <200811201256.44429.david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
2008-11-21  8:03       ` Miguel Ángel Álvarez
     [not found]         ` <b0438a630811210003v4d81c9d4g33c851f489c1743f-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-11-21  8:48           ` David Brownell
     [not found]             ` <200811210048.28842.david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
2008-11-21  9:29               ` Miguel Ángel Álvarez [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=b0438a630811210129y2d517f12n43e9b11da726af55@mail.gmail.com \
    --to=gotzoncabanes-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org \
    --cc=spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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).