All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
To: Mark Brown <broonie@kernel.org>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
	Mark Brown <broonie@kernel.og>,
	ksummit-discuss@lists.linuxfoundation.org,
	Liam Girdwood <liam.r.girdwood@linux.intel.com>,
	Sakari Ailus <sakari.ailus@iki.fi>
Subject: Re: [Ksummit-discuss] Draft agenda for the kernel summit
Date: Tue, 20 Oct 2015 13:34:43 -0200	[thread overview]
Message-ID: <20151020133443.4140d53f@recife.lan> (raw)
In-Reply-To: <20151020132209.GZ32054@sirena.org.uk>

[-- Attachment #1: Type: text/plain, Size: 1601 bytes --]

Em Tue, 20 Oct 2015 14:22:09 +0100
Mark Brown <broonie@kernel.org> escreveu:

> On Tue, Oct 20, 2015 at 12:55:37PM +0100, Liam Girdwood wrote:
> > On Mon, 2015-10-19 at 14:46 -0600, Shuah Khan wrote:
> 
> > > You can find the media graph that includes ALSA Mixer Function and
> > > Control Interface (Device: /dev/snd/controlC2), PCM Audio Capture
> > > Function and PCM Audio Capture interface (Device: /dev/snd/pcmC2D0c)
> > > at:
> 
> > > https://drive.google.com/open?id=0B0NIL0BQg-AlbjZkcElJb2RtVk0
> 
> > Looks nice. Fwiw, the graph will probably get a lot bigger when we show
> > the audio DSP and codec paths (as DSPs and codecs have multiple muxes
> > and mixers). It may be good to have a cmd line option to stop at certain
> > nodes on the graph to avoid over populated/complex graphs ?
> 
> Having the ability to describe which physical device things are part of
> would probably help a lot with the rendering here - I'm guessing that a
> lot of filtering is likely to be things like collapsing down devices not
> being looked at right now into a single block in the graph and it'd
> probably help with user comprehesibilty provide a mapping back to things
> they can see in the physical world.
> 
> This doesn't entirely correspond with struct device due to MFD and
> multi-function USB stuff but it'd be a good start I expect.

Yeah, collapsing devices make sense.

Sakari is working on a properties API to be added to Media
Controller entities/interfaces/links. Perhaps he could add this
requirement to the API he's working with.

Regards,
Mauro



[-- Attachment #2: Assinatura digital OpenPGP --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-10-20 15:35 UTC|newest]

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-12 19:01 [Ksummit-discuss] Draft agenda for the kernel summit Theodore Ts'o
2015-10-13  4:00 ` Josh Triplett
2015-10-13 13:31 ` Linus Walleij
2015-10-16  0:41 ` Rob Herring
2015-10-16  6:52   ` Johannes Berg
2015-10-16  7:55     ` Arnd Bergmann
2015-10-16  8:00       ` Marcel Holtmann
2015-10-16  8:37         ` Arnd Bergmann
2015-10-16  9:21         ` Linus Walleij
2015-10-16  8:00       ` Johannes Berg
2015-10-16  7:57   ` Samuel Ortiz
2015-10-16  8:45     ` Geert Uytterhoeven
2015-10-16 13:09     ` Rob Herring
2015-10-16  9:03   ` Mark Brown
2015-10-16  8:04 ` Christian Borntraeger
2015-10-19 12:33 ` Mauro Carvalho Chehab
2015-10-19 13:53   ` Mark Brown
2015-10-19 16:27     ` Liam Girdwood
2015-10-19 19:34       ` Mauro Carvalho Chehab
2015-10-19 20:46         ` Shuah Khan
2015-10-20 11:55           ` Liam Girdwood
2015-10-20 13:22             ` Mark Brown
2015-10-20 15:34               ` Mauro Carvalho Chehab [this message]
2015-10-22  8:34                 ` Sakari Ailus
2015-10-22  8:49                 ` Sakari Ailus
2015-10-20 15:18             ` Mauro Carvalho Chehab
2015-10-20 15:47               ` Takashi Iwai
2015-10-20 16:11                 ` Mauro Carvalho Chehab
2015-10-20 23:39               ` Shuah Khan
2015-10-20 13:13         ` Mark Brown
2015-10-20 15:29           ` Mauro Carvalho Chehab
2015-10-20 15:56             ` Mark Brown
2015-10-21  0:04       ` Laurent Pinchart
2015-10-21 10:24         ` Liam Girdwood
2015-10-21 10:24         ` Mark Brown
2015-10-21  8:59       ` Geert Uytterhoeven
2015-10-19 18:48   ` Jonathan Cameron
  -- strict thread matches above, loose matches on Subject: below --
2017-10-13  0:15 [Ksummit-discuss] Draft Agenda for the Kernel Summit Theodore Ts'o
2017-10-13 18:28 ` Konstantin Ryabitsev
2017-10-20  0:30   ` Theodore Ts'o
2017-10-16  6:35 ` James Morris
2017-10-19 11:35 ` Mauro Carvalho Chehab
2017-10-20  0:32   ` Theodore Ts'o
2017-10-20  0:53 ` Rafael J. Wysocki
2017-10-20 19:46   ` Theodore Ts'o
2017-10-21  1:02     ` Rafael J. Wysocki
2017-10-20  2:18 ` Theodore Ts'o
2017-10-20  3:32   ` Thorsten Leemhuis
2017-10-20 11:19     ` Rafael J. Wysocki
2017-10-20  2:19 ` Theodore Ts'o
2017-10-20 14:31   ` Shuah Khan
2017-10-20 15:27     ` James Bottomley
2017-10-20 19:16       ` Shuah Khan
2017-10-20  6:04 ` Steven Rostedt
2017-10-20 15:57   ` Joe Perches
2017-10-20 19:50     ` Theodore Ts'o
2017-10-31  5:10       ` Joe Perches
2017-10-31 18:16         ` Jonathan Corbet
     [not found] <1445272350.2481.40.camel@loki>
2015-10-19 18:52 ` [Ksummit-discuss] Draft agenda for the kernel summit Mark Brown
2014-08-11 22:45 Theodore Ts'o
     [not found] ` <alpine.DEB.2.10.1408152014100.2503@hadrien>
2014-08-15 22:35   ` Theodore Ts'o
2014-08-16  0:27 ` Darren Vincent Hart
2014-08-16  2:17   ` Theodore Ts'o

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20151020133443.4140d53f@recife.lan \
    --to=mchehab@osg.samsung.com \
    --cc=broonie@kernel.og \
    --cc=broonie@kernel.org \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=lars@metafoo.de \
    --cc=liam.r.girdwood@linux.intel.com \
    --cc=sakari.ailus@iki.fi \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.