From: Petr Cvek <petr.cvek@tul.cz>
To: Robert Jarzmik <robert.jarzmik@free.fr>
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 06:18:32 +0200 [thread overview]
Message-ID: <55F3A798.5090904@tul.cz> (raw)
In-Reply-To: <87y4gdtr6e.fsf@belgarion.home>
Dne 11.9.2015 v 08:18 Robert Jarzmik napsal(a):
> Petr Cvek <petr.cvek@tul.cz> writes:
>
>>> Should have been posted to linux arm kernel mailing list, unless my mailer
>>> failed ...
>>>
>> Searching for:
>>
>> "ARM: pxa: add resources to pxaficp_ir"
>>
>> did not found anything, same was for "ficp" in the linux-arm-kernel/netdev/linux-kernel
>> mailing list archive.
> Ah ok, I'll resend it then.
>
>>>> BTW This patch required update of my kernel repo. It seems that my:
>>>>
>>>> magician.c patches + ficp patch + new dma engine
>>>>
>>>> does not work for me at all. Kernel throws some panic about interrupts and then
>>>> it ends in an infinite stack dumping loop. Fault occurs before rootfs is
>>>> mounted, so probably around MMC init (with removed SD card it fails normally
>>>> with no rootfs found error).
>>> Could you send me (privately) the stack you're getting please. This is something
>>> I'd like to catch up early in the -rc releases.
>>
>> Well this will be problem as I cannot save anything to an SD card after and
>> during the failure. Only viable interfaces would be earlycon on an infraport
>> or high speed camera on LCD :-).
> Ah just as on my mioa701. I ended up soldering a JTAG cable :)
Rather not :-D.
>
>>> 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.
>>
>> Anyway after mmc dma revert I was still not able to start FICP. There is an error:
>>
>> Unable to handle kernel paging request at virtual address 32e00004
>>
>> from pxa_irda_startup() and it seems it is caused by register definitions. For example:
>>
>> writel_relaxed((val), (irda)->stuart_base + (off));
>>
>> is called by
>>
>> stuart_writel(si, 0, STIER);
>>
>> 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.
Petr
next prev parent reply other threads:[~2015-09-12 4:18 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 [this message]
2015-09-12 11:03 ` Robert Jarzmik
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=55F3A798.5090904@tul.cz \
--to=petr.cvek@tul.cz \
--cc=arnd@arndb.de \
--cc=dbaryshkov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=robert.jarzmik@free.fr \
--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).