On Thu, Jan 02, 2014 at 06:50:55PM +0100, Jean-Francois Moine wrote:
> No, the 'endpoint' <=> 'remote-endpoint' is a point to point relation.
> Even if the sources and sinks are not explicitly defined, the way
> the stream flows is easy to find: the main source is always in the
> 'audio-controller
On Thu, 2 Jan 2014 13:10:45 +
Mark Brown wrote:
> On Thu, Jan 02, 2014 at 01:44:37PM +0100, Jean-Francois Moine wrote:
>
> > I still don't understand. There is already such cases in the Cubox:
> > the S/PDIF output from the kirkwood audio controller is connected to
> > both the HDMI transmit
On Thu, Jan 02, 2014 at 01:44:37PM +0100, Jean-Francois Moine wrote:
> I still don't understand. There is already such cases in the Cubox:
> the S/PDIF output from the kirkwood audio controller is connected to
> both the HDMI transmitter and the S/PDIF TOSLINK. So, in the audio
> controller, the p
On Thu, 2 Jan 2014 11:56:18 +
Mark Brown wrote:
> On Thu, Jan 02, 2014 at 12:43:31PM +0100, Jean-Francois Moine wrote:
> > Mark Brown wrote:
>
> > > I think we want an explicit object in the card representing the DAIs.
> > > This will both be useful for making it easy to find the configurat
On Thu, Jan 02, 2014 at 12:43:31PM +0100, Jean-Francois Moine wrote:
> Mark Brown wrote:
> > I think we want an explicit object in the card representing the DAIs.
> > This will both be useful for making it easy to find the configuration
> > for the link and will be more extensible for the cases w
On Thu, 2 Jan 2014 11:10:56 +
Mark Brown wrote:
> On Thu, Jan 02, 2014 at 10:26:47AM +0100, Jean-Francois Moine wrote:
>
> > /* audio */
> > port@1 {
> > hdmi_i2s_audio: endpoint@0 {
> > reg = <0x03>;
> >
On Thu, Jan 02, 2014 at 10:26:47AM +0100, Jean-Francois Moine wrote:
> /* audio */
> port@1 {
> hdmi_i2s_audio: endpoint@0 {
> reg = <0x03>;
> remote-endpoint = <&audio_hdmi_i2s>;
>
On Wed, 01 Jan 2014 21:11:23 +0100
Lars-Peter Clausen wrote:
> On 01/01/2014 09:08 PM, Jean-Francois Moine wrote:
> > On Wed, 01 Jan 2014 20:05:05 +0100
> > Lars-Peter Clausen wrote:
> >
> >> As Mark also said, this binding definitely leaks way too much internals of
> >> the current ASoC implem
On 01/01/2014 09:08 PM, Jean-Francois Moine wrote:
> On Wed, 01 Jan 2014 20:05:05 +0100
> Lars-Peter Clausen wrote:
>
>> As Mark also said, this binding definitely leaks way too much internals of
>> the current ASoC implementation. In my opinion the way forward for ASoC is
>> to stop to distingui
On Wed, 01 Jan 2014 20:05:05 +0100
Lars-Peter Clausen wrote:
> As Mark also said, this binding definitely leaks way too much internals of
> the current ASoC implementation. In my opinion the way forward for ASoC is
> to stop to distinguish between different types of components. This is on one
> h
On 12/31/2013 11:31 AM, Jean-Francois Moine wrote:
> Some audio cards are built from different hardware components.
> When such compound cards don't need specific code, this driver creates
> them with the required DAI links and routes from a DT.
>
> Signed-off-by: Jean-Francois Moine
> ---
> This
11 matches
Mail list logo
