linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Kumar Gala <galak@kernel.crashing.org>
To: Timur Tabi <timur@freescale.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] powerpc: add fsl, fifo-depth property to Freescale SSI device nodes
Date: Mon, 9 Mar 2009 10:52:28 -0500	[thread overview]
Message-ID: <A811318D-E6DB-4DDB-A8F5-50A076F1C013@kernel.crashing.org> (raw)
In-Reply-To: <1236200130-12012-1-git-send-email-timur@freescale.com>


On Mar 4, 2009, at 2:55 PM, Timur Tabi wrote:

> The Freescale Serial Synchronous Interface (SSI) is an audio device  
> present on
> some Freescale SOCs.  Various implementations of the SSI have a  
> different
> transmit and receive FIFO depth, but are otherwise identical.  To  
> support
> these variations, add a new property fsl,fifo-depth to the SSI node  
> that
> specifies the depth of the FIFOs.
>
> Also update the MPC8610 HPCD device tree with this property.
>
> Signed-off-by: Timur Tabi <timur@freescale.com>
> ---
>
> Updates to the SSI audio driver will come later.  Currently, this  
> driver
> supports only one Freescale SOC, and so it's hard-coded to use the  
> value 8.
> If/when this driver is updated to support other SOCs (e.g. the i.MX  
> parts
> that have a FIFO depth of 15), the driver will check for this  
> property.  I
> just want to get this DTS change in now.
>
> Documentation/powerpc/dts-bindings/fsl/ssi.txt |    2 ++
> arch/powerpc/boot/dts/mpc8610_hpcd.dts         |    2 ++
> 2 files changed, 4 insertions(+), 0 deletions(-)

applied to next

- k

      reply	other threads:[~2009-03-09 15:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-04 20:55 [PATCH] powerpc: add fsl, fifo-depth property to Freescale SSI device nodes Timur Tabi
2009-03-09 15:52 ` Kumar Gala [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=A811318D-E6DB-4DDB-A8F5-50A076F1C013@kernel.crashing.org \
    --to=galak@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=timur@freescale.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;
as well as URLs for NNTP newsgroup(s).