Re: [PATCH v2 2/6] ASoC: Allow the DAPM routes to be stored in device tree

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Dec 07, 2011 at 01:58:26PM -0700, Stephen Warren wrote:

> +	audio-routing =
> +		"Headphone Jack", "HPOUTR",
> +		"Headphone Jack", "HPOUTL",
> +		"Int Spk", "ROP",
> +		"Int Spk", "RON",
> +		"Int Spk", "LOP",
> +		"Int Spk", "LON",
> +		"Mic Jack", "MICBIAS",
> +		"IN1L", "Mic Jack";

Before we do this we first need to come up with a way of specifying the
DAPM nodes.  For the CODEC pins I'm fairly comfortable with just
documenting the fact that we want to use the pins as labelled on the
CODEC datsheet but for other objects on the board we need to come up
with something.  The tricky bit here is jacks - we need to be able to
express headsets, translate them into the separate input and output
widgets that DAPM uses while coping with multiple biases and custom
detection methods.
--
To unsubscribe from this list: send the line "unsubscribe linux-tegra" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [ARM Kernel]     [Linux ARM]     [Linux ARM MSM]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux