From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Thierry Reding <thierry.reding@avionic-design.de>
Cc: linuxtv@stefanringel.de, linux-media@vger.kernel.org,
d.belimov@gmail.com
Subject: Re: [PATCH 3/5] tm6000: bugfix interrupt reset
Date: Mon, 05 Dec 2011 16:21:51 -0200 [thread overview]
Message-ID: <4EDD0BBF.3020804@redhat.com> (raw)
In-Reply-To: <20111205153800.GA32512@avionic-0098.mockup.avionic-design.de>
On 05-12-2011 13:38, Thierry Reding wrote:
> * Mauro Carvalho Chehab wrote:
>> On 05-12-2011 05:21, Thierry Reding wrote:
>>> * linuxtv@stefanringel.de wrote:
>>>> From: Stefan Ringel<linuxtv@stefanringel.de>
>>>>
>>>> Signed-off-by: Stefan Ringel<linuxtv@stefanringel.de>
>>>
>>> Your commit message needs more details. Why do you think this is a bugfix?
>>> Also this commit seems to effectively revert (and then partially reimplement)
>>> a patch that I posted some months ago.
>>
>> Thierry,
>>
>> I noticed this. I tested tm6000 with those changes with both the first gen
>> tm5600 devices I have and HVR900H and I didn't notice any bad thing with this
>> approach, and changing from one standard to another is now faster.
>>
>> So, I decided to apply it (with the remaining patches I've made to
>> fix audio for PAL/M and NTSC/M).
>>
>> I also noticed that TM6000_QUIRK_NO_USB_DELAY is not needed anymore
>> (still, Stefan's patches didn't remove it completely).
>>
>> Could you please test if the problems you've solved with your approach
>> are still occurring?
>
> Unfortunately I don't have any hardware available anymore. I will see if I
> can get my hands on some of the devices, but that may take a while. I guess
> you'll just have to apply without me testing them first.
Ok.
> My comments should be addressed anyway, though.
Sure.
Stefan,
Could you better explain a little more about this change?
Also, if this is not required anymore, please send us a patch removing the
TM6000_QUIRK_NO_USB_DELAY quirk.
Regards,
Mauro.
>
> Thierry
next prev parent reply other threads:[~2011-12-05 18:22 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1322509580-14460-1-git-send-email-linuxtv@stefanringel.de>
2011-11-28 19:46 ` [PATCH 2/5] tm6000: bugfix register setting linuxtv
2011-11-28 19:46 ` [PATCH 3/5] tm6000: bugfix interrupt reset linuxtv
2011-12-05 7:21 ` Thierry Reding
2011-12-05 12:04 ` Mauro Carvalho Chehab
2011-12-05 15:38 ` Thierry Reding
2011-12-05 18:21 ` Mauro Carvalho Chehab [this message]
2011-12-05 20:02 ` Stefan Ringel
2011-12-05 20:16 ` Mauro Carvalho Chehab
2011-12-06 6:51 ` Thierry Reding
2011-12-06 8:12 ` Thierry Reding
2011-12-06 12:25 ` Mauro Carvalho Chehab
2011-12-06 13:05 ` [PATCH] [media] tm6000: Fix fast USB access quirk Thierry Reding
2011-12-06 12:22 ` [PATCH 3/5] tm6000: bugfix interrupt reset Mauro Carvalho Chehab
2011-11-28 19:46 ` [PATCH 4/5] tm6000: bugfix bulk transfer linuxtv
2011-11-28 19:46 ` [PATCH 5/5] tm6000: bugfix data check linuxtv
2011-11-30 17:21 ` Mauro Carvalho Chehab
2011-12-06 13:39 ` [PATCH 1/2] [media] tm6000: Fix check for interrupt endpoint Thierry Reding
2011-12-06 13:39 ` [PATCH 2/2] [media] tm6000: Fix bad indentation Thierry Reding
2011-12-06 13:58 ` Antti Palosaari
2011-12-06 14:13 ` Thierry Reding
2011-12-06 20:58 ` Mauro Carvalho Chehab
2011-12-06 21:03 ` Antti Palosaari
2011-12-07 13:24 ` Mauro Carvalho Chehab
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=4EDD0BBF.3020804@redhat.com \
--to=mchehab@redhat.com \
--cc=d.belimov@gmail.com \
--cc=linux-media@vger.kernel.org \
--cc=linuxtv@stefanringel.de \
--cc=thierry.reding@avionic-design.de \
/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;
as well as URLs for NNTP newsgroup(s).