On Tue, Feb 03, 2015 at 08:31:30PM +0100, Jean-Francois Moine wrote:
> Mark Brown wrote:
> > So how does the simple controller interact with a more complex one given
> > that it's somehow picking some controller node to start from?
> A way to solve this problem could be to create only one card
On Tue, Feb 03, 2015 at 08:31:30PM +0100, Jean-Francois Moine wrote:
Mark Brown broo...@kernel.org wrote:
So how does the simple controller interact with a more complex one given
that it's somehow picking some controller node to start from?
A way to solve this problem could be to create
On Tue, 3 Feb 2015 16:47:48 +
Mark Brown wrote:
> On Sat, Jan 24, 2015 at 08:30:27AM +0100, Jean-Francois Moine wrote:
> > Mark Brown wrote:
> > > On Fri, Jan 23, 2015 at 07:34:56PM +0100, Jean-Francois Moine wrote:
>
> > > > The simple card builder, 'dt-card' (maybe a better name would
On Sat, Jan 24, 2015 at 08:30:27AM +0100, Jean-Francois Moine wrote:
> Mark Brown wrote:
> > On Fri, Jan 23, 2015 at 07:34:56PM +0100, Jean-Francois Moine wrote:
> > > The simple card builder, 'dt-card' (maybe a better name would have been
> > > 'graph-card'), acts just like the simple-card
On Sat, Jan 24, 2015 at 08:30:27AM +0100, Jean-Francois Moine wrote:
Mark Brown broo...@kernel.org wrote:
On Fri, Jan 23, 2015 at 07:34:56PM +0100, Jean-Francois Moine wrote:
The simple card builder, 'dt-card' (maybe a better name would have been
'graph-card'), acts just like the
On Tue, 3 Feb 2015 16:47:48 +
Mark Brown broo...@kernel.org wrote:
On Sat, Jan 24, 2015 at 08:30:27AM +0100, Jean-Francois Moine wrote:
Mark Brown broo...@kernel.org wrote:
On Fri, Jan 23, 2015 at 07:34:56PM +0100, Jean-Francois Moine wrote:
The simple card builder, 'dt-card'
On Mon, 26 Jan 2015 12:53:53 +0100
Lars-Peter Clausen wrote:
> > - a generic sound node in the case of multi controllers or multi codec
> >levels (after dt-card extension):
> >
> > sound {
> > compatible = "linux,dt-card";
> > audio-root = <>; /* starting point of
On 01/24/2015 02:18 PM, Jean-Francois Moine wrote:
On Sat, 24 Jan 2015 12:27:35 +0100
Lars-Peter Clausen wrote:
On 01/23/2015 07:34 PM, Jean-Francois Moine wrote:
On Fri, 23 Jan 2015 14:56:04 +0100
Lars-Peter Clausen wrote:
On 01/23/2015 01:15 PM, Jean-Francois Moine wrote:
There is no
On Mon, 26 Jan 2015 12:53:53 +0100
Lars-Peter Clausen l...@metafoo.de wrote:
- a generic sound node in the case of multi controllers or multi codec
levels (after dt-card extension):
sound {
compatible = linux,dt-card;
audio-root = audio1; /* starting
On 01/24/2015 02:18 PM, Jean-Francois Moine wrote:
On Sat, 24 Jan 2015 12:27:35 +0100
Lars-Peter Clausen l...@metafoo.de wrote:
On 01/23/2015 07:34 PM, Jean-Francois Moine wrote:
On Fri, 23 Jan 2015 14:56:04 +0100
Lars-Peter Clausen l...@metafoo.de wrote:
On 01/23/2015 01:15 PM,
On Sat, 24 Jan 2015 12:27:35 +0100
Lars-Peter Clausen wrote:
> On 01/23/2015 07:34 PM, Jean-Francois Moine wrote:
> > On Fri, 23 Jan 2015 14:56:04 +0100
> > Lars-Peter Clausen wrote:
> >
> >> On 01/23/2015 01:15 PM, Jean-Francois Moine wrote:
> > There is no first or second output in the
On 01/23/2015 07:34 PM, Jean-Francois Moine wrote:
On Fri, 23 Jan 2015 14:56:04 +0100
Lars-Peter Clausen wrote:
On 01/23/2015 01:15 PM, Jean-Francois Moine wrote:
[...]
The DT should describe the hardware, and the simple-card mixes hardware
and software.
For example, the kirkwood controller
On 01/23/2015 07:34 PM, Jean-Francois Moine wrote:
On Fri, 23 Jan 2015 14:56:04 +0100
Lars-Peter Clausen l...@metafoo.de wrote:
On 01/23/2015 01:15 PM, Jean-Francois Moine wrote:
[...]
The DT should describe the hardware, and the simple-card mixes hardware
and software.
For example, the
On Sat, 24 Jan 2015 12:27:35 +0100
Lars-Peter Clausen l...@metafoo.de wrote:
On 01/23/2015 07:34 PM, Jean-Francois Moine wrote:
On Fri, 23 Jan 2015 14:56:04 +0100
Lars-Peter Clausen l...@metafoo.de wrote:
On 01/23/2015 01:15 PM, Jean-Francois Moine wrote:
There is no first or second
On Fri, 23 Jan 2015 19:13:43 +
Mark Brown wrote:
> On Fri, Jan 23, 2015 at 07:34:56PM +0100, Jean-Francois Moine wrote:
>
> > A card builder is a device which
> > - scans the graph of ports,
> > - fills the struct snd_soc_card according to the links between the
> > ports and their
On Fri, Jan 23, 2015 at 07:34:56PM +0100, Jean-Francois Moine wrote:
> A card builder is a device which
> - scans the graph of ports,
> - fills the struct snd_soc_card according to the links between the
> ports and their properties,
> - and, eventually, calls snd_soc_register_card().
> The
On Fri, 23 Jan 2015 14:56:04 +0100
Lars-Peter Clausen wrote:
> On 01/23/2015 01:15 PM, Jean-Francois Moine wrote:
> [...]
> > The DT should describe the hardware, and the simple-card mixes hardware
> > and software.
> > For example, the kirkwood controller may create 2 CPU DAIs. With the
> >
On Fri, Jan 23, 2015 at 02:56:04PM +0100, Lars-Peter Clausen wrote:
> On 01/23/2015 01:15 PM, Jean-Francois Moine wrote:
> >>Your example is a relative simple one where you do not have any additional
> >>audio fabric on the board itself.
> >Right, and that's why I'd be glad to have quickly
On 01/23/2015 01:15 PM, Jean-Francois Moine wrote:
[...]
The DT should describe the hardware, and the simple-card mixes hardware
and software.
For example, the kirkwood controller may create 2 CPU DAIs. With the
simple-card, the DT contains a number to reference these DAIs (for
example,
On Thu, 22 Jan 2015 20:25:39 +0100
Lars-Peter Clausen wrote:
> On 01/22/2015 09:07 AM, Jean-Francois Moine wrote:
> > On Wed, 21 Jan 2015 21:14:07 +0100
> > Lars-Peter Clausen wrote:
> >
> >> [...]
> >>> + card->dai_link->dai_fmt =
> >>> + snd_soc_of_parse_daifmt(of_cpu,
On Fri, 23 Jan 2015 14:56:04 +0100
Lars-Peter Clausen l...@metafoo.de wrote:
On 01/23/2015 01:15 PM, Jean-Francois Moine wrote:
[...]
The DT should describe the hardware, and the simple-card mixes hardware
and software.
For example, the kirkwood controller may create 2 CPU DAIs. With the
On Fri, Jan 23, 2015 at 02:56:04PM +0100, Lars-Peter Clausen wrote:
On 01/23/2015 01:15 PM, Jean-Francois Moine wrote:
Your example is a relative simple one where you do not have any additional
audio fabric on the board itself.
Right, and that's why I'd be glad to have quickly something in
On Fri, Jan 23, 2015 at 07:34:56PM +0100, Jean-Francois Moine wrote:
A card builder is a device which
- scans the graph of ports,
- fills the struct snd_soc_card according to the links between the
ports and their properties,
- and, eventually, calls snd_soc_register_card().
The simple
On 01/23/2015 01:15 PM, Jean-Francois Moine wrote:
[...]
The DT should describe the hardware, and the simple-card mixes hardware
and software.
For example, the kirkwood controller may create 2 CPU DAIs. With the
simple-card, the DT contains a number to reference these DAIs (for
example,
On Thu, 22 Jan 2015 20:25:39 +0100
Lars-Peter Clausen l...@metafoo.de wrote:
On 01/22/2015 09:07 AM, Jean-Francois Moine wrote:
On Wed, 21 Jan 2015 21:14:07 +0100
Lars-Peter Clausen l...@metafoo.de wrote:
[...]
+ card-dai_link-dai_fmt =
+ snd_soc_of_parse_daifmt(of_cpu,
On Fri, 23 Jan 2015 19:13:43 +
Mark Brown broo...@kernel.org wrote:
On Fri, Jan 23, 2015 at 07:34:56PM +0100, Jean-Francois Moine wrote:
A card builder is a device which
- scans the graph of ports,
- fills the struct snd_soc_card according to the links between the
ports and their
On 01/22/2015 09:07 AM, Jean-Francois Moine wrote:
On Wed, 21 Jan 2015 21:14:07 +0100
Lars-Peter Clausen wrote:
[...]
+ card->dai_link->dai_fmt =
+ snd_soc_of_parse_daifmt(of_cpu, "dt-audio-card,",
+ NULL, NULL) &
+
On Thu, Jan 22, 2015 at 09:07:23AM +0100, Jean-Francois Moine wrote:
> I was also wondering about some of these properties, as widgets and
> routing. They seem to be software information and Linux specific.
> Must these properties appear in the DTs?
What's Linux specific about them? The widgets
On Wed, 21 Jan 2015 21:14:07 +0100
Lars-Peter Clausen wrote:
> [...]
> > + card->dai_link->dai_fmt =
> > + snd_soc_of_parse_daifmt(of_cpu, "dt-audio-card,",
> > + NULL, NULL) &
> > + ~SND_SOC_DAIFMT_MASTER_MASK;
>
>
> This one
On Wed, 21 Jan 2015 21:14:07 +0100
Lars-Peter Clausen l...@metafoo.de wrote:
[...]
+ card-dai_link-dai_fmt =
+ snd_soc_of_parse_daifmt(of_cpu, dt-audio-card,,
+ NULL, NULL)
+ ~SND_SOC_DAIFMT_MASTER_MASK;
This one does
On 01/22/2015 09:07 AM, Jean-Francois Moine wrote:
On Wed, 21 Jan 2015 21:14:07 +0100
Lars-Peter Clausen l...@metafoo.de wrote:
[...]
+ card-dai_link-dai_fmt =
+ snd_soc_of_parse_daifmt(of_cpu, dt-audio-card,,
+ NULL, NULL)
+
On Thu, Jan 22, 2015 at 09:07:23AM +0100, Jean-Francois Moine wrote:
I was also wondering about some of these properties, as widgets and
routing. They seem to be software information and Linux specific.
Must these properties appear in the DTs?
What's Linux specific about them? The widgets
[...]
+ card->dai_link->dai_fmt =
+ snd_soc_of_parse_daifmt(of_cpu, "dt-audio-card,",
+ NULL, NULL) &
+ ~SND_SOC_DAIFMT_MASTER_MASK;
This one does not seem to be in the bindings documentation.
--
To unsubscribe
This patch adds a generic way to create audio cards from a graph of ports
defined in a DT.
The dt-card devices are created by audio controllers with themselves
as the root of the graph and the sound cards are created according to
the parameters found in the tree.
Signed-off-by: Jean-Francois
This patch adds a generic way to create audio cards from a graph of ports
defined in a DT.
The dt-card devices are created by audio controllers with themselves
as the root of the graph and the sound cards are created according to
the parameters found in the tree.
Signed-off-by: Jean-Francois
[...]
+ card-dai_link-dai_fmt =
+ snd_soc_of_parse_daifmt(of_cpu, dt-audio-card,,
+ NULL, NULL)
+ ~SND_SOC_DAIFMT_MASTER_MASK;
This one does not seem to be in the bindings documentation.
--
To unsubscribe from
36 matches
Mail list logo
