alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: "Reddy, MR Swami" <MR.Swami.Reddy@nsc.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: Process of sumit the Audio driver code to ALSA
Date: Wed, 19 Jan 2011 08:36:35 +0100	[thread overview]
Message-ID: <s5htyh5l4zg.wl%tiwai@suse.de> (raw)
In-Reply-To: <290463D19D2E064191F1F96ECA480A8943287370CB@EXMAIL02.scwf.nsc.com>

At Tue, 18 Jan 2011 23:20:15 -0800,
Reddy, MR Swami wrote:
> 
> Thanks for quick response!
> Yes, it  ASOC based and currently, the audio drivers supported for Samsung 6410 target.

OK, then just post your patches to alsa-devel ML, Cc'ed to ASoC
maintainers (Liam Girdwood <lrg@slimlogic.co.uk> and
 Mark Brown <broonie@opensource.wolfsonmicro.com>).

But I guess there have been quite many changes in ASoC core
(e.g. multi-core support) that are no longer compatible with
2.6.24-based code.  These have to be fixed, of course, before
merging.

It's up to you -- you can first pot the original patch and ask some
hints for forward-porting, or first start reading the latest ASoC API
changes, do port your driver then post the revised patch.


thanks,

Takashi

> 
> Thanks
> Swami
> 
> -----Original Message-----
> From: Takashi Iwai [mailto:tiwai@suse.de] 
> Sent: Wednesday, January 19, 2011 12:39 PM
> To: Reddy, MR Swami
> Subject: Re: Process of sumit the Audio driver code to ALSA
> 
> At Tue, 18 Jan 2011 20:58:28 -0800,
> Reddy, MR Swami wrote:
> > 
> > Hello,
> > We (National Semi) have developed ALSA based audio drivers for our Audio subsystem. Could you please let me know the process to submit and include as part of ALSA project.
> > 
> > The ALSA audio driver version info as follows:
> >   - Linux - 2.6.24 base
> >   - Andorid- 2.1   base
> 
> Is this based on ASoC?  If not, I recommend you to port the code to ASoC, thus it's the standard for embedded devices.
> If you have any questions, just post to alsa-devel ML.
> 
> 
> thanks,
> 
> Takashi
> 
> 

  reply	other threads:[~2011-01-19  7:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-18 14:12 [PATCH - [hdspm] 0/3] Support for RME RayDAT and AIO Adrian Knoth
2011-01-18 14:12 ` [PATCH - [hdspm] 1/3] Add headers for RayDAT and AIO support Adrian Knoth
2011-01-18 14:40   ` Takashi Iwai
2011-01-18 15:00     ` Adrian Knoth
     [not found]     ` <290463D19D2E064191F1F96ECA480A89432873706D@EXMAIL02.scwf.nsc.com>
     [not found]       ` <s5hwrm1l68q.wl%tiwai@suse.de>
2011-01-19  7:20         ` Process of sumit the Audio driver code to ALSA Reddy, MR Swami
2011-01-19  7:36           ` Takashi Iwai [this message]
2011-03-07 11:26             ` Reddy, MR Swami
2011-01-19 22:55           ` Seungwhan Youn
2011-01-18 14:12 ` [PATCH - [hdspm] 3/3] Add RayDAT and AIO strings to Kconfig Adrian Knoth
2011-01-18 14:36 ` [PATCH - [hdspm] 0/3] Support for RME RayDAT and AIO Takashi Iwai
2011-01-18 17:06   ` Adrian Knoth
2011-01-19  6:41     ` Takashi Iwai
     [not found] ` <1295359939-14673-3-git-send-email-adi@drcomp.erfurt.thur.de>
2011-01-18 14:55   ` [PATCH - [hdspm] 2/3] Enable " Takashi Iwai
2011-01-18 15:24     ` Adrian Knoth
2011-01-21  7:07       ` Takashi Iwai

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=s5htyh5l4zg.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=MR.Swami.Reddy@nsc.com \
    --cc=alsa-devel@alsa-project.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).