On Wed, Mar 16, 2016 at 08:27:04PM +0530, Vinod Koul wrote:
> So I don't think FW name would help, if required we should add dev_info
> to print the firmware which is getting loaded.
We can't really be relying on userspace trawling through the logs -
quite apart from anything else the message
On Tue, Mar 15, 2016 at 09:48:51AM +, Liam Girdwood wrote:
> On Tue, 2016-03-15 at 09:55 +0100, Takashi Iwai wrote:
> > > Shouldn't we use whatever we use to figure out which firmware to load
> > > rather than the firmware name? Someone might do something like try to
> > > replace one
On Tue, Mar 15, 2016 at 06:01:28AM +, Liam Girdwood wrote:
> 1) Shortname is board/machine name. This can come from DMI or device
> tree. e.g. "Asus T100"
That seems more useful for users.
> 2) Long name is 1 + driver name + optional firmware name. (I've just
> added the FW name here too as
On Mon, Mar 14, 2016 at 08:19:27AM +, Liam Girdwood wrote:
Could people please fix their mail clients to word wrap within
paragraphs at something substantially less than 80 columns. Doing this
makes your messages much easier to read and reply to.
> On Mon, 2016-03-14 at 08:17 +, Lu, Han
On Fri, Jul 27, 2012 at 01:38:30PM -0500, Pierre-Louis Bossart wrote:
On 7/25/2012 4:19 PM, Mark Brown wrote:
If this is for fake streams held open by userspace we have a better in
kernel solution now - just hide the PCM from userspace entirely and
start it like anything else in the device
On Mon, Jul 23, 2012 at 02:27:26PM +0530, Arun Raghavan wrote:
While discussion on how we should deal with hardware with different
requirements from standard desktop cases continues, I'd like to solve the
problem of having modem PCMs that we don't want to auto-suspend in the near
future. For
On Mon, Jul 23, 2012 at 03:05:25PM -0500, Pierre-Louis Bossart wrote:
somehow the information should be available at the ALSA level that
such devices do not provide/expect any data and should not be
suspended. This information is available at the kernel level (no_pcm
flag or something), it
On Mon, Jul 23, 2012 at 09:08:40AM +0530, Arun Raghavan wrote:
Guys, please delete unneeded context from messages - makes it much
easier to find the new content.
3. Devices that have a loopback path in hardware/DSP (this is a request
I've seen, but I'm not aware of hardware that does this)
On Fri, Jun 15, 2012 at 06:28:51PM +0100, Liam Girdwood wrote:
On Fri, 2012-06-15 at 15:11 +0300, Tanu Kaskinen wrote:
This sort of hardware causes trouble for the planned routing system, at
least as I have envisioned it to behave. My vision has been that the
routing logic in pulseaudio
On Tue, Apr 17, 2012 at 04:29:01PM +0200, David Henningsson wrote:
On 04/17/2012 10:08 AM, Tanu Kaskinen wrote:
In my mind a port is an atomic routing unit, and a port
that can be used for both input and output is not atomic (it
defines two routes). An example of practical problems having
On Fri, Feb 24, 2012 at 03:39:44PM +0800, Feng Wei wrote:
2012/2/24 David Henningsson david.hennings...@canonical.com:
* The competing implementation problem: We've had multiple implementations
posted to the PulseAudio mailinglist, one by Janos and Jaska, one by
Alejandro and Margarita
On Tue, Nov 08, 2011 at 09:54:01AM +0100, David Henningsson wrote:
On 11/08/2011 09:31 AM, Maarten Bosmans wrote:
That's exactly why you should compile without asserts enable for
production builds.
I'm afraid that approach won't work for Ubuntu - there are way too
many cases where we
On Fri, Oct 14, 2011 at 03:27:58PM +0300, Janos Kovacs wrote:
So the idea is to use a modified device manager, David's jack
detection (with the port support for cards) and a stripped version of
Margarita's UCM patches.
I think this sounds like an excellent approach and it's fantastic that
On Mon, Oct 17, 2011 at 02:31:42PM +0300, Janos Kovacs wrote:
The first attempt is to map UCM verbs directly to alsa card profiles with the
combination with combination of certain UCM modifiers. We would have
profiles like HiFi: Play Music, HiFi Low Power: Play Music + Capture
Music,
Voice
On Fri, Oct 14, 2011 at 12:00:54PM +0200, David Henningsson wrote:
On 10/14/2011 11:39 AM, Mark Brown wrote:
On Fri, Oct 14, 2011 at 10:57:08AM +0200, David Henningsson wrote:
As for ports, this again depends on what is mutually exclusive and
what could be used in parallel, I vaguely remember
On Mon, Oct 10, 2011 at 01:01:00PM +0300, Matti J. Aaltonen wrote:
On 10/07/2011 03:49 PM, ext Mark Brown wrote:
What I said was that the entire audio system should be one card.
I didn't read it that way,but OK... Just one more comment/question:
I would have thought that to achieve as fine
On Fri, Oct 07, 2011 at 07:21:44PM +0200, Paul Menzel wrote:
I am not sure. 4 W power consumption of a sound chip sounds quite a lot
to me. Additionally as written above please try a newer version.
That's many orders of magnitude more than is sane unless there's very
loud sound coming out of
On Fri, Oct 07, 2011 at 10:24:40AM +0300, Matti J. Aaltonen wrote:
But then I don't get why the radio should be able to say when the
[analog] stream starts and stops (and what do you actually mean by
that?). Isn't it possible in the above scenario to simply turn on
the cross wired amp if the
On Fri, Oct 07, 2011 at 03:21:33PM +0300, Matti J. Aaltonen wrote:
by the DAC codec. Now to have on output for the analog radio the amplifier
should be handled as a separate audio card, right? And then the
No. When I said this should all be a single card that's what I meant.
Yes, but what I
On Fri, Oct 07, 2011 at 03:39:02PM +0300, Matti J. Aaltonen wrote:
On 10/07/2011 03:33 PM, ext Mark Brown wrote:
by the DAC codec. Now to have on output for the analog radio the amplifier
should be handled as a separate audio card, right? And then the
No. When I said this should all
On Thu, Oct 06, 2011 at 01:49:38PM +0300, Tanu Kaskinen wrote:
Yeah the driver is unable to detect directly if someone wants to use
the analog signal. But that's not a big problem, there still could
exist the facility for explicitly turning the radio on and off. It's
also possible to
On Thu, Oct 06, 2011 at 04:22:33PM +0300, Matti J. Aaltonen wrote:
But the handling of the analog audio isn't that straightforward, or
maybe it is... I'm not familiar with pulse audio.
It's trivial and can be done entirely in kernel as with all the other
audio power management.
Earlier
On Tue, Oct 04, 2011 at 02:33:47PM +0300, Tanu Kaskinen wrote:
On Mon, 2011-10-03 at 22:21 +0300, Mark Brown wrote:
On Mon, Oct 03, 2011 at 09:13:29PM +0200, David Henningsson wrote:
On 10/03/2011 06:12 PM, Tanu Kaskinen wrote:
I have some hardware that needs some mixer configuration
On Tue, Oct 04, 2011 at 02:30:17PM +0300, Tanu Kaskinen wrote:
I'm not sure that would work in this case. The mixer element is an
enumeration with states Off, Rx and Tx. I've been told that it
controls whether the FM radio is powered on (and whether it's in the
reception or transmission
On Wed, Sep 28, 2011 at 10:29:03AM -0700, Taylor Hutt wrote:
In this case, I am part of a team working to make a shipping product, and
there are time constraints which
do not afford the time necessary to do that, _and_ to make forward progress
to get the sound system working
across a
On Thu, Sep 22, 2011 at 09:33:15PM +0200, Maarten Bosmans wrote:
2011/9/22 Mark Brown broo...@sirena.org.uk:
On Wed, 2011-09-21 at 17:08 +0300, David Henningsson wrote:
Does not sound like anything I would like to enable by default - e g,
what if hw mute introduces a click, and changing
On Wed, Sep 21, 2011 at 05:16:52PM +0300, Tanu Kaskinen wrote:
On Wed, 2011-09-21 at 17:08 +0300, David Henningsson wrote:
Does not sound like anything I would like to enable by default - e g,
what if hw mute introduces a click, and changing the volume does not?
If you think that such
On Wed, Aug 03, 2011 at 06:35:22PM +0530, Himanshu Chug wrote:
one colleague of mine from ALSA /kernel team have wrote the Jack detection
app using udev API from libudev,
so the Jack plug in/plug Out state can be read at sys/devices/virtual/switch
/h2w/state
This is a completely non-standard
On Fri, Jul 08, 2011 at 02:38:00PM +0200, David Henningsson wrote:
On 2011-05-10 22:29, Jorge Eduardo Candelaria wrote:
+#includepulsecore/core-error.h
+#includepulsecore/once.h
Your MUA appears to have mangled spaces.
SectionVerb {
EnableSequence [
cdev hw:SDP4430
On Tue, Jun 28, 2011 at 11:46:18PM +0100, Colin Guthrie wrote:
The UCM stuff isn't merged yet as I'm kinda waiting on getting the jack
detection stuff sorted out first (it's kinda a pre-requisite but we
could ultimately shuffle things round in the short term).
It'd be really helpful to get
On Tue, Jul 05, 2011 at 08:26:42PM +0300, Tanu Kaskinen wrote:
I would much prefer if patches would be sent with git send-email unless
they are perfect, because commenting is much easier with inline
patches...
Even if they're perfect tools like git am are *much* happier with this.
31 matches
Mail list logo
