From: Robert Jarzmik <robert.jarzmik@free.fr>
To: Petr Cvek <petr.cvek@tul.cz>
Cc: zonque@gmail.com, ulf.hansson@linaro.org,
Samuel Ortiz <samuel@sortiz.org>,
Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH 2/3] net: irda: pxaficp_ir: convert to readl and writel
Date: Sat, 12 Sep 2015 13:03:45 +0200 [thread overview]
Message-ID: <87d1xnucfi.fsf@belgarion.home> (raw)
In-Reply-To: <55F3A798.5090904@tul.cz> (Petr Cvek's message of "Sat, 12 Sep 2015 06:18:32 +0200")
Petr Cvek <petr.cvek@tul.cz> 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
next prev parent reply other threads:[~2015-09-12 11:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-03 6:20 [PATCH 0/3] net: irda: pxaficp_ir: dmaengine conversion Robert Jarzmik
2015-09-03 6:20 ` [PATCH 1/3] net: irda: pxaficp_ir: use sched_clock() for time management Robert Jarzmik
2015-09-03 6:20 ` [PATCH 2/3] net: irda: pxaficp_ir: convert to readl and writel Robert Jarzmik
2015-09-08 20:24 ` Petr Cvek
2015-09-09 1:23 ` Petr Cvek
2015-09-09 6:25 ` Robert Jarzmik
2015-09-10 6:14 ` Petr Cvek
2015-09-10 11:14 ` Robert Jarzmik
2015-09-11 1:52 ` Petr Cvek
2015-09-11 6:18 ` Robert Jarzmik
2015-09-12 4:18 ` Petr Cvek
2015-09-12 11:03 ` Robert Jarzmik [this message]
2015-09-13 2:47 ` Petr Cvek
2015-09-03 6:20 ` [PATCH 3/3] net: irda: pxaficp_ir: dmaengine conversion Robert Jarzmik
2015-09-07 4:16 ` [PATCH 0/3] " Petr Cvek
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=87d1xnucfi.fsf@belgarion.home \
--to=robert.jarzmik@free.fr \
--cc=arnd@arndb.de \
--cc=dbaryshkov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=petr.cvek@tul.cz \
--cc=samuel@sortiz.org \
--cc=ulf.hansson@linaro.org \
--cc=zonque@gmail.com \
/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).