From: Roger Quadros <ext-roger.quadros@nokia.com>
To: ext matthias schwarz <matthias.schw@googlemail.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: Reading from ISP registers fails
Date: Tue, 21 Jul 2009 13:14:57 +0300 [thread overview]
Message-ID: <4A659521.6000606@nokia.com> (raw)
In-Reply-To: <a187869d0907210137x4995178au73c34182e6c3d47e@mail.gmail.com>
ext matthias schwarz wrote:
> Hello there,
>
> i just wrote a little kernel-module, which only executes the following
> lines of code:
>
> u32 syn_mode;
> void* iomem;
> struct resource* resource_ptr;
>
> resource_ptr = request_mem_region(0x480BC000, 0xFFF, "isp_ccdc");
>
> iomem = ioremap(OMAP3ISP_REG(ISP_SYSCONFIG), 8);
> if(iomem == NULL) {
> printk("ioremap returned zero\n");
> return 0;
> }
> syn_mode = ioread32(iomem);
>
>
>
> The resulting behaviour does not depend on which ISP register i am
> trying to read, it also happens for "OMAP3ISP_CCDC_REG_BASE +
> ISPCCDC_SYN_MODE" for example. And also when using
> "omap_readl(address)" to read those registers.
>
> So when this code is executed i get:
>
> Unhandled fault: external abort on non-linefetch (0x1028) at 0xd80bc004
> Internal error: : 1028 [#1] PREEMPT
> Internal error: : 1028 [#1] PREEMPT
> Modules linked in:Modules linked in: camera(+) camera(+) ipv6 ipv6
>
> CPU: 0 Not tainted (2.6.28-omap1 #15)
> [...]
>
>
> Hope someone can help me with what might be wrong.
> Thank you,
> Matthias
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
You need to enable interface clocks before accessing any peripheral registers.
regards,
-roger
next prev parent reply other threads:[~2009-07-21 10:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-21 8:37 Reading from ISP registers fails matthias schwarz
2009-07-21 10:14 ` Roger Quadros [this message]
2009-07-21 11:01 ` matthias schwarz
2009-07-21 15:45 ` Hiremath, Vaibhav
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=4A659521.6000606@nokia.com \
--to=ext-roger.quadros@nokia.com \
--cc=linux-omap@vger.kernel.org \
--cc=matthias.schw@googlemail.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