Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Eric Miao <eric.y.miao@gmail.com>
Cc: alsa-devel@alsa-project.org, Mark Brown <broonie@sirena.org.uk>,
	Philipp Zabel <philipp.zabel@gmail.com>,
	Paul Shen <bshen9@marvell.com>,
	linux-arm-kernel <linux-arm-kernel@lists.arm.linux.org.uk>,
	Daniel Ribeiro <drwyrm@gmail.com>
Subject: Re: [RFC PATCH 3/5] pxa: clean up the legacy SSP API
Date: Thu, 30 Apr 2009 08:08:58 +0100	[thread overview]
Message-ID: <20090430070858.GA3242@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <f17812d70904291931o7bbf4df6g2827bdb28920f82b@mail.gmail.com>

On Thu, Apr 30, 2009 at 10:31:53AM +0800, Eric Miao wrote:
> On Thu, Apr 30, 2009 at 2:51 AM, Russell King - ARM Linux
> <linux@arm.linux.org.uk> wrote:
> > The transfers happen under control of PCON not the PXA; PCON asserts a
> > GPIO to activate the DMA to control when the transfer happens.
> 
> That's too bad then. Does that GPIO act like a chip select or it's just a
> signal to inform the host to do a transfer? And it also depends on the
> SCLK direction.
> 
> If the GPIO behaves like an IRQ to inform the host for a transfer, maybe
> the driver can arrange a transfer initiated by that event.

I don't know what the timing requirement is.  What I do know is what
the current code does, which is to use the signal to control the
transmit DMA when PCON wants to transfer data.

Now, remember that PCON has a habbit of resetting the PXA when things
happen that it doesn't like, I really don't want to go round
experimenting with this thing; as already stated it's really not worth
trying to merge this code if that's what will be required.

      reply	other threads:[~2009-04-30  7:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-23  5:06 [RFC PATCH 3/5] pxa: clean up the legacy SSP API Eric Miao
2009-04-23  8:24 ` Mark Brown
2009-04-28 22:20 ` Russell King - ARM Linux
2009-04-28 23:06   ` Daniel Ribeiro
2009-04-29  2:18     ` Eric Miao
2009-04-29  7:27     ` Russell King - ARM Linux
2009-04-29  8:21       ` Mark Brown
2009-04-29  8:41         ` Russell King - ARM Linux
2009-04-29  9:14           ` Eric Miao
2009-04-29 18:51             ` Russell King - ARM Linux
2009-04-30  2:31               ` Eric Miao
2009-04-30  7:08                 ` Russell King - ARM Linux [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=20090430070858.GA3242@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@sirena.org.uk \
    --cc=bshen9@marvell.com \
    --cc=drwyrm@gmail.com \
    --cc=eric.y.miao@gmail.com \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=philipp.zabel@gmail.com \
    /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