Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Daniel Ribeiro <drwyrm@gmail.com>
Cc: alsa-devel@alsa-project.org, Eric Miao <eric.y.miao@gmail.com>,
	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>
Subject: Re: [RFC PATCH 3/5] pxa: clean up the legacy SSP API
Date: Wed, 29 Apr 2009 08:27:06 +0100	[thread overview]
Message-ID: <20090429072706.GA31566@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1240959968.30410.1.camel@brutus>

On Tue, Apr 28, 2009 at 08:06:08PM -0300, Daniel Ribeiro wrote:
> Em Ter, 2009-04-28 às 23:20 +0100, Russell King - ARM Linux escreveu:
> > On Thu, Apr 23, 2009 at 01:06:12PM +0800, Eric Miao wrote:
> > > Actually, due to the number of possible SSP configurations, it's quite a
> > > difficult job to maintain an API that can be well re-used. The guideline
> > > here is to keep only a list of SSP devices and their basic information,
> > > and it's up to the user driver (like SPI or Audio SSP) to configure the
> > > SSP in a desired way.
> > 
> > Hmm, the LX battery driver uses this API for its rudimentary battery
> > communication channel with the PCON.
> > 
> > What are you suggesting as the replacement API?  Direct register access?
> 
> The SPI subsystem?

Can the SPI system cope with the other chip being the master of the
interface.  In other words, can SPI sit around primed for a transfer,
and notify the user of SPI that new data has arrived?

If not, the SPI subsystem is totally unsuitable for this.

  parent reply	other threads:[~2009-04-29  7:27 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 [this message]
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

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=20090429072706.GA31566@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