Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754794AbYCOWqr (ORCPT ); Sat, 15 Mar 2008 18:46:47 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752884AbYCOWqi (ORCPT ); Sat, 15 Mar 2008 18:46:38 -0400 Received: from dell.benran.ru ([83.149.196.126]:53382 "EHLO ari.home" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752367AbYCOWqh (ORCPT ); Sat, 15 Mar 2008 18:46:37 -0400 Date: Sun, 16 Mar 2008 01:46:36 +0300 (MSK) From: "Lev A. Melnikovsky" To: David Brownell cc: Alessandro Suardi , Rene Herman , linux-kernel@vger.kernel.org Subject: Re: ehci-hcd affects hda speed In-Reply-To: Message-ID: References: <47CEC816.6000808@keyaccess.nl> <5a4c581d0803051203s1a0048c2u5f10b3eb442cfafb@mail.gmail.com> <200803051303.46275.david-b@pacbell.net> User-Agent: Alpine 1.00 (LFD 882 2007-12-20) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1491 Lines: 34 LAM> Also, does anyone have a VT6212L datasheet? Unfortunately, Google I have eventually found it. An enlightening reading, really. If I understood all words, I mean :-). Particularly, what does "MAC turn around time" stand for with respect to EHCI? I would appreciate some reference, thanks. On Wed, 5 Mar 2008 at 5:19pm, Rene Herman wrote: RH> It was diagnosed to the VT6212L doing decidedly weird things with RH> toggling the Async bit and tying up the bus. Yes, it really looks like the chip owns the bus when it shouldn't. Suppose VT6212L has damaged its brains somehow. Can we fix this by ignoring its requests unless they are legitimate? I mean make the driver enable bus mastering only for short periods when the controller is expected to do something useful. It is easy (I have already done myself) to implement for asynchronous schedule, but there's still periodic schedule. Is it possible? How? Please advise. Being positive, I didn't have much time to play with it yet, but changing the bit 5 (EHCI sleep time select: 0=1us 1=10us) of register 0x4B seems to resolve my own problem. I wonder if this is going to help others (Alessandro?): setpci -s 00:09.2 4b.b=29 [don't forget to adjust the device address]. -L -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/