public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Franklin Meng <fmeng2002@yahoo.com>
To: Devin Heitmueller <dheitmueller@kernellabs.com>
Cc: linux-media@vger.kernel.org
Subject: Re: Kworld 315U and SAA7113?
Date: Sun, 17 Jan 2010 11:02:44 -0800 (PST)	[thread overview]
Message-ID: <87348.88308.qm@web32702.mail.mud.yahoo.com> (raw)
In-Reply-To: <829197381001170828t33b63c0ayf9b26472f702dd90@mail.gmail.com>

OK.. I guess that was a misunderstanding on my part.  I will split up the patch and re submit.  

Thanks,
Franklin

--- On Sun, 1/17/10, Devin Heitmueller <dheitmueller@kernellabs.com> wrote:

> From: Devin Heitmueller <dheitmueller@kernellabs.com>
> Subject: Re: Kworld 315U and SAA7113?
> To: "Franklin Meng" <fmeng2002@yahoo.com>
> Cc: linux-media@vger.kernel.org
> Date: Sunday, January 17, 2010, 8:28 AM
> On Sun, Jan 17, 2010 at 2:05 AM,
> Franklin Meng <fmeng2002@yahoo.com>
> wrote:
> > I retested my device and tried several different GPIO
> sequences but so far every time I change between the Analog
> and digital interface, the SAA7113 needs to be
> reinitialized.  I tried leaving both the digital and analog
> interfaces enabled by setting the GPIO to 7c but then the LG
> demod does not initialize.
> >
> > Either way it looks like I will have to reinitialize
> the device after switching between interfaces.
> >
> > Other than that do you want me to remove the suspend
> GPIO?  Since I don't have the equipment to measure the
> power, I don't know for a fact if the device really has been
> put in a suspend state or not.
> 
> Hello Franklin,
> 
> Just to be clear, I'm not proposing that you remove the
> suspend logic.
>  I was suggesting that you should be breaking the change
> into three
> separate patches, so that if a problem arises we can
> isolate whether
> it is a result of the power management changes. 
> Having a separate
> patch is especially valuable because you are touching other
> drivers
> which are shared by other products.
> 
> Cheers,
> 
> Devin
> 
> -- 
> Devin J. Heitmueller - Kernel Labs
> http://www.kernellabs.com
> 


      

  reply	other threads:[~2010-01-17 19:02 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-09 19:30 Kworld 315U and SAA7113? Franklin Meng
2010-01-13 21:10 ` Mauro Carvalho Chehab
2010-01-14 18:17   ` Franklin Meng
2010-01-13 22:04 ` Devin Heitmueller
2010-01-14 18:54   ` Franklin Meng
2010-01-14 19:13     ` Devin Heitmueller
2010-01-14 22:00     ` CityK
2010-01-14 22:09       ` Devin Heitmueller
2010-01-15  3:03         ` Franklin Meng
2010-01-17  7:05           ` Franklin Meng
2010-01-17 12:28             ` Mauro Carvalho Chehab
2010-01-17 16:28             ` Devin Heitmueller
2010-01-17 19:02               ` Franklin Meng [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-01-09  8:30 Franklin Meng
2010-01-08  3:48 Franklin Meng

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=87348.88308.qm@web32702.mail.mud.yahoo.com \
    --to=fmeng2002@yahoo.com \
    --cc=dheitmueller@kernellabs.com \
    --cc=linux-media@vger.kernel.org \
    /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