linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: chasedouglas@gmail.com (Chase Douglas)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH v2 1/3] ep93xx i2s audio driver
Date: Wed, 26 May 2010 08:54:50 -0400	[thread overview]
Message-ID: <1274878490.9346.38.camel@cndougla-ubuntu> (raw)
In-Reply-To: <1274850588-30460-2-git-send-email-ryan@bluewatersys.com>

On Wed, 2010-05-26 at 17:09 +1200, Ryan Mallon wrote:
> diff --git a/sound/soc/ep93xx/ep93xx-i2s.h b/sound/soc/ep93xx/ep93xx-i2s.h
> new file mode 100644
> index 0000000..830c793
> --- /dev/null
> +++ b/sound/soc/ep93xx/ep93xx-i2s.h
> @@ -0,0 +1,25 @@
> +/*
> + * linux/sound/soc/ep93xx-i2s.h
> + * EP93xx I2S driver
> + *
> + * Copyright (C) 2010 Ryan Mallon <ryan@bluewatersys.com>
> + *  
> + * This program is free software; you can redistribute it and/or modify
> + * it under the terms of the GNU General Public License version 2 as
> + * published by the Free Software Foundation.
> + *
> + */
> +
> +#ifndef _EP93XX_SND_SOC_I2S_H
> +#define _EP93XX_SND_SOC_I2S_H
> +
> +/*
> + * These are the offsets for the LRDIV and SDIV fields in the syscon i2sclkdiv
> + * register.
> + */
> +#define EP93XX_I2S_LRDIV	17
> +#define EP93XX_I2S_SDIV		16

Looks like a minor ugly whitespace issue above.

-- Chase

  parent reply	other threads:[~2010-05-26 12:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-26  5:09 [RFC PATCH v2 0/3] ep93xx i2s audio Ryan Mallon
2010-05-26  5:09 ` [RFC PATCH v2 1/3] ep93xx i2s audio driver Ryan Mallon
2010-05-26 11:07   ` [alsa-devel] " Liam Girdwood
2010-05-26 11:16   ` Peter Ujfalusi
2010-05-26 12:54   ` Chase Douglas [this message]
2010-05-26 13:08     ` Lothar Waßmann
2010-05-27  2:13   ` Mark Brown
2010-05-26  5:09 ` [RFC PATCH v2 2/3] ep93xx i2s core support Ryan Mallon
2010-05-26  5:09 ` [RFC PATCH v2 3/3] ep93xx i2s audio snapper cl15 support Ryan Mallon
2010-05-26 12:59 ` [RFC PATCH v2 0/3] ep93xx i2s audio Chase Douglas

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=1274878490.9346.38.camel@cndougla-ubuntu \
    --to=chasedouglas@gmail.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 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).