public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: lawrence rust <lawrence@softsystem.co.uk>
To: Andy Walls <awalls@md.metrocast.net>
Cc: Shane Harrison <shane.harrison@paragon.co.nz>,
	linux-media@vger.kernel.org
Subject: Re: Fwd: No audio in HW Compressed MPEG2 container on HVR-1300
Date: Sat, 07 Aug 2010 11:54:20 +0200	[thread overview]
Message-ID: <1281174860.1363.112.camel@gagarin> (raw)
In-Reply-To: <1281097339.2052.17.camel@morgan.silverblock.net>

On Fri, 2010-08-06 at 08:22 -0400, Andy Walls wrote:
> On Fri, 2010-08-06 at 11:40 +0200, lawrence rust wrote:
> > On Fri, 2010-08-06 at 11:49 +1200, Shane Harrison wrote:
> 
> > > Well still no luck this end.  Have done the following:
> 
> > > 2) Applied the patch - no change (we were detecting the WM8775 OK
> 
> BTW, I forgot to mention the ivtv driver uses the WM8775 module for the
> PVR-150 card.  Changes to that module that affect the default setting
> needs to be done in a way that doesn't break the PVR-150.
> 

I believe that the patch that I posted for wm8775.c preserves the
original functionality (for ivtv and other dependants) although it
clearly achieves this through a different sequence of register writes.
The only major change to function is from ALC to manual level control
using the ALSA mixer API - which generally gives a better audio
experience.

> Maybe a .s_config() method in the WM8775 v4l2_subdev_core_ops would be
> the way to do that, or by passing parameters in struct i2c_board_info
> (according to a recent post by Hans Verkuil).

Good idea. If my current method breaks any existing code then I'll do
that, but for the moment I believe that they can co-exist.

Comments, criticisms and errata much appreciated.

> 
> Regards,
> Andy

-- Lawrence



      reply	other threads:[~2010-08-07  9:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-02  2:15 No audio in HW Compressed MPEG2 container on HVR-1300 Shane Harrison
2010-08-02  9:32 ` lawrence rust
     [not found]   ` <AANLkTinHK8mVwrCnOZTUMsHVGTykj8bNdkKwcbMQ8LK_@mail.gmail.com>
2010-08-02 10:19     ` Fwd: " Shane Harrison
2010-08-02 11:59       ` lawrence rust
2010-08-02 21:02         ` Shane Harrison
2010-08-03 13:48           ` lawrence rust
2010-08-05 23:49             ` Shane Harrison
2010-08-06  9:40               ` lawrence rust
2010-08-06 12:15                 ` Andy Walls
2010-08-06 12:22                 ` Andy Walls
2010-08-07  9:54                   ` lawrence rust [this message]

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=1281174860.1363.112.camel@gagarin \
    --to=lawrence@softsystem.co.uk \
    --cc=awalls@md.metrocast.net \
    --cc=linux-media@vger.kernel.org \
    --cc=shane.harrison@paragon.co.nz \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox