All of lore.kernel.org
 help / color / mirror / Atom feed
From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/5] ASoC: split pxa ssp for reusing code
Date: Thu, 18 Mar 2010 12:09:08 +0000	[thread overview]
Message-ID: <20100318120907.GH3080@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <771cded01003171929t5364eafblf2bd734e2fd1202@mail.gmail.com>

On Wed, Mar 17, 2010 at 10:29:46PM -0400, Haojian Zhuang wrote:
> From ffd197865a1114b46cc7d6b0442e4c6ece962f8b Mon Sep 17 00:00:00 2001
> From: Haojian Zhuang <haojian.zhuang@marvell.com>
> Date: Wed, 17 Mar 2010 10:45:30 -0400
> Subject: [PATCH] ASoC: split pxa ssp for reusing code
> 
> Since basic SSP features are shared between PXA2xx and PXA168, the difference
> is focused on clock generating. Now split ssp code into two parts. One is for
> general ssp feature. The other is for pxa2xx parts.

Could you please provide a more detailed description of what the
differences between the two SSP implementations.  This description is
rather vauge and doesn't appear to 100% tie in with the implemenation -
for example, the hw_params() implementations for the two variants seem
*very* close to each other.

It may be that some of this stuff can be handled by having a common
hw_params() which can be called by device specific code that handles the
differences.  Given how fiddly the configuration of the framing is
having two different implementations to keep in sync doesn't seem good.

  reply	other threads:[~2010-03-18 12:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-18  2:29 [PATCH 1/5] ASoC: split pxa ssp for reusing code Haojian Zhuang
2010-03-18 12:09 ` Mark Brown [this message]
2010-03-19 15:51   ` Haojian Zhuang

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=20100318120907.GH3080@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=linux-arm-kernel@lists.infradead.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 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.