public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: tony@atomide.com
To: lamikr <lamikr@cc.jyu.fi>
Cc: OMAP-Linux <linux-omap-open-source@linux.omap.com>
Subject: Re: [PATCH] Alsa modularisations and support for tsc2101 3/3 (round 2)
Date: Wed, 22 Mar 2006 08:03:59 -0800	[thread overview]
Message-ID: <20060322160357.GD5748@atomide.com> (raw)
In-Reply-To: <440C9D00.7060902@cc.jyu.fi>

* lamikr <lamikr@cc.jyu.fi> [060306 12:36]:
> OMAP Alsa Patch (3/3)
> 
> This 3/3 patch adds the tsc2101 alsa driver support for the omap-h2.
> Just like the aic23 alsa driver, the codec
> specific functionality is separated from the common alsa driver
> functionality that is in the omap-alsa.c.
> tsc2101 mixer supports currently the playback selection between
> loudspeaker and headset/handset.
> Addon of others input and targets should be possible to do afterwards.
> 
> In addition it should be possible to add later the support for the
> dynamic clocks on top of this series of patches, as discussed
> in the omap-linux mailing list.

Leaving out the following irda chunk: 
  
> @@ -255,12 +256,6 @@ static int h2_transceiver_mode(struct de
>  
>  static struct omap_irda_config h2_irda_data = {
>  	.transceiver_cap	= IR_SIRMODE | IR_MIRMODE | IR_FIRMODE,
> -	.rx_channel		= OMAP_DMA_UART3_RX,
> -	.tx_channel		= OMAP_DMA_UART3_TX,
> -	.dest_start		= UART3_THR,
> -	.src_start		= UART3_RHR,
> -	.tx_trigger		= 0,
> -	.rx_trigger		= 0,
>  };
>  
>  static struct resource h2_irda_resources[] = {

Regards,

Tony

      reply	other threads:[~2006-03-22 16:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-06 20:35 [PATCH] Alsa modularisations and support for tsc2101 3/3 (round 2) lamikr
2006-03-22 16:03 ` tony [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=20060322160357.GD5748@atomide.com \
    --to=tony@atomide.com \
    --cc=lamikr@cc.jyu.fi \
    --cc=linux-omap-open-source@linux.omap.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