From: Tim Blechmann Subject: Re: [bisected] lx6464es fails to open a second time Date: Tue, 22 Nov 2011 11:17:45 +0100 Message-ID: <12713926.WkIoyVagpM@moka> References: <2428359.JOQWRg64O4@moka> <4ECB5257.4040600@ladisch.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from klingt.org (mail.klingt.org [86.59.21.178]) by alsa0.perex.cz (Postfix) with ESMTP id 4B4D8245D9 for ; Tue, 22 Nov 2011 11:17:46 +0100 (CET) In-Reply-To: <4ECB5257.4040600@ladisch.de> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: alsa-devel-bounces@alsa-project.org Errors-To: alsa-devel-bounces@alsa-project.org To: Clemens Ladisch Cc: Takashi Iwai , Brian Gerst , alsa-devel@alsa-project.org, LKML List-Id: alsa-devel@alsa-project.org > > today, i was able to bisect the issue and the first bad commit is: > > > > commit 6175ddf06b6172046a329e3abfd9c901a43efd2e > > Author: Brian Gerst > > Date: Fri Feb 5 09:37:07 2010 -0500 > > > > x86: Clean up mem*io functions. > > > > the communication with the device is done by passing simple commands via > > memcpy_fromio and memcpy_toio (compare sound/pci/lx6464es/lx_core.c, > > lines 75 to 99). any idea, what is going wrong there? > > The old and new implementations of memcpy_*io do not have any differences > in the documented API, but the new ones are much more optimized, so they > might not use 8- or 32-bit accesses or a different access pattern. > > Does the card's mapped I/O region behave exactly like memory, or has it > any restrictions on how it can be used? In the latter case, you should > implement your readbuf/writebuf functions by hand to use plain 32-bit > accesses in order (or whatever is required). indeed, emulating memcpy_*io with ioread32/iowrite32 fixes the issue. thanks, tim