From: "Bjørn Mork" <bjorn@mork.no>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: Oliver Endriss <o.endriss@gmx.de>,
linux-media@vger.kernel.org, stable@kernel.org
Subject: Re: [PATCH] V4L/DVB: budget-av: wait longer for frontend to power on
Date: Fri, 09 Apr 2010 20:37:16 +0200 [thread overview]
Message-ID: <87k4sgtqub.fsf@nemi.mork.no> (raw)
In-Reply-To: <4BBF37D9.2060206@redhat.com> (Mauro Carvalho Chehab's message of "Fri, 09 Apr 2010 11:21:13 -0300")
Mauro Carvalho Chehab <mchehab@redhat.com> writes:
> Oliver Endriss wrote:
>
>> Mauro, please do not apply this patch!
>
> Don't worry, I won't apply this patch.
>>
>> Afaik there is no tuner which takes 5 seconds to initialize. (And if
>> there was one, it would be a bad idea to add a 5s delay for all tuners!)
>
> Yes, that's my point: if is there such hardware, the fix should touch
> only on the hardware with that broken design.
>
> (btw, there is one tuner that takes almost 30 seconds to initialize:
> the firmware load for xc3028 on tm6000 rev A should go on slow speed,
> otherwise, it fails loading - the i2c implementation on tm6000 were
> really badly designed)
>
>> The saa7146_i2c_writeout errors are likely caused by broken hardware.
>
> I think so.
You are so right both of you. Please drop the patch.
I believe this problem was yet another symptom of my faulty SATA hard
drive. The driver is working fine with the default 100 ms timeout after
replacing that drive.
Sorry about all the unnecessary work I created for you, and thanks for
taking the time to review this even though you suspected user/hardware
error.
Bjørn
prev parent reply other threads:[~2010-04-09 18:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-21 19:46 [PATCH] V4L/DVB: budget-av: wait longer for frontend to power on Bjørn Mork
2010-04-08 21:15 ` Mauro Carvalho Chehab
2010-04-09 14:07 ` Oliver Endriss
2010-04-09 14:21 ` Mauro Carvalho Chehab
2010-04-09 18:37 ` Bjørn Mork [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=87k4sgtqub.fsf@nemi.mork.no \
--to=bjorn@mork.no \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=o.endriss@gmx.de \
--cc=stable@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