[alsa-devel] Need Help About Submitting Updates to Existing ASoC Codec Driver [Re Post]

[Stephen Warren]

Ashish P. Chavan wrote at Tuesday, June 14, 2011 11:46 PM:
> Hi,
>    We are in the process of upgrading codec driver for Dialog's DA7210 codec
> (sound/soc/codecs/da7210.c). Existing driver in mainline is just bare minimum
> and doesn't support many of the chip's features. Our update would be a major
> functionality update in nature.
> 
> Our final goal is to get the updated driver merged into mainline kernel.
> For this we just want to make sure that we follow correct process. As far as I
> understood from alsa-project.org and other resources, the normal process is to
> submit the patch against alsa-kenel (git.alsa-project.org:alsa-kernel.git alsa-kernel)
> and get it reviewed by maintainers there. Once all maintainers are satisfied
> with the patch, it will be eventually put in to for-linus branch and get
> in to mainline.

For ASoC drivers specifically, you'll probably want to work off the
following git repository:

git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound-2.6.git

and in particular, branch for-3.1.

Yes, you'll want to post your changes to the mailing list, explicitly
CC'ing the maintainers of the ASoC subsystem (Mark and Liam; see the
MAINTAINERS file in the root of the kernel source tree).

Once the change is approved, Mark will check it into his repository.
Later, the overall ALSA maintainers will pull those changes into their
repository, and from there will be merged into Linus' mainline kernel
during the next merge window.

Good background reading can be found in the kernel source tree in the
Documentation/ directory:

SubmittingPatches
SubmitChecklist
development-process/*

-- 
nvpublic