From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754817AbbILLIv (ORCPT ); Sat, 12 Sep 2015 07:08:51 -0400 Received: from smtp12.smtpout.orange.fr ([80.12.242.134]:22978 "EHLO smtp.smtpout.orange.fr" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754492AbbILLIt (ORCPT ); Sat, 12 Sep 2015 07:08:49 -0400 X-ME-Helo: belgarion X-ME-Auth: amFyem1pay5yb2JlcnRAb3JhbmdlLmZy X-ME-Date: Sat, 12 Sep 2015 13:08:48 +0200 X-ME-IP: 109.220.179.182 From: Robert Jarzmik To: Petr Cvek Cc: zonque@gmail.com, ulf.hansson@linaro.org, Samuel Ortiz , Dmitry Eremin-Solenikov , netdev@vger.kernel.org, linux-kernel@vger.kernel.org, Arnd Bergmann Subject: Re: [PATCH 2/3] net: irda: pxaficp_ir: convert to readl and writel References: <1441261251-19548-1-git-send-email-robert.jarzmik@free.fr> <1441261251-19548-3-git-send-email-robert.jarzmik@free.fr> <55EF43E9.2040000@tul.cz> <55EF8A0F.7070106@tul.cz> <87twr4un1h.fsf@belgarion.home> <55F11FDE.6050304@tul.cz> <87io7iv845.fsf@belgarion.home> <55F233D2.3020708@tul.cz> <87y4gdtr6e.fsf@belgarion.home> <55F3A798.5090904@tul.cz> X-URL: http://belgarath.falguerolles.org/ Date: Sat, 12 Sep 2015 13:03:45 +0200 In-Reply-To: <55F3A798.5090904@tul.cz> (Petr Cvek's message of "Sat, 12 Sep 2015 06:18:32 +0200") Message-ID: <87d1xnucfi.fsf@belgarion.home> User-Agent: Gnus/5.130008 (Ma Gnus v0.8) Emacs/24.4 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Petr Cvek writes: >>>> And it is true I have not tested the rootfs special case, where drivers are not >>>> yet initialized (and more specifically gpio and interrupt chip). Your backtrace >>>> should tell me if you fall into this category of issues ... but I digress, this >>>> has no link with pxaficp. >>> >>> Should I start new thread? (same bug can be present in the FICP too) >> Yes, this pxamci bothers me, it deserves a thread. > > Will start soon. And I think I see your problem now : (a) there is a regression from the commit 8c8fe97b2b8a, for which the fix is here: https://lkml.org/lkml/2015/9/6/112 (b) for gpio expanders, another fix is here : https://lkml.org/lkml/2015/9/12/62 The regression is on dmaengine, that's where the thread belongs I think, at least if that fixes your issue. >>> but STIER is not just an offset, but full register address: >>> >>> __REG(0x40700004) >>> >>> So the definition should be changed, unless there is another patch I did not >>> received (in that case, send me full patchset again please) :-). >> Agreed, this is a bug in this patch. With this fix, is the pxaficp working or do >> you need a bit more time to experiment ? > > I have tried with a nasty hack (use only lower part of address, it should equal with reg offset): > #undef __REG > -#define __REG(x) (x) > +#define __REG(x) (x & 0xffff) > > and it seems to work. The module inits and I am able to see IrDA traffic and > ping other machine. FIR mode (mostly impacted by DMA) is still untested as > magician unfortunately supports only SIR mode. Okay, I'll add a fix in the next iteration, thanks for finding this. Cheers. -- Robert