[alsa-devel] Developing a ti-pcm1863 (adc) codec driver

[Mark Brown]

On Fri, Aug 25, 2017 at 11:24:24AM +0200, Oleksandr Müller wrote:

> >  Use a route, that's the more modern way.
> Would then this be correct?

Yes.

> >  I'm not sure I understand the question here.

> I mean by default the adc takes VIN1 as an input and I need him to take
> VIN4. If I put my switch under sound controls do I have to trigger it, and
> if yes how? The corrected line should look like this?

That sounds like a DAPM mux?

> > This looks like you've got most of a driver here, probably the easiest
> > thing to do is submit it using the process outlined in
> > SubmittingPatches. The code looks mostly fine so this shouldn't be too
> > much of an issue.

> I dont know this process. At first I would want to get it working with my
> hardware before I would begin with a more detailed development with a lot
> more functionalities.

Like I say the process is documented in SubmittingPatches (in the kernel
tree).
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
URL: <http://mailman.alsa-project.org/pipermail/alsa-devel/attachments/20170825/e8e91929/attachment.sig>